Many organizations are being asked to demonstrate that their software is developed using secure development practices. While there is a growing body of guidance for text-based software languages, there has been less discussion about what secure development looks like for LabVIEW teams.
To help address that gap, a group of LabVIEW experts collaborated on the first version of the LabVIEW Secure Development Framework Guide. The document adapts guidance from the NIST Secure Software Development Framework (SSDF) to the unique workflows and tools commonly used by LabVIEW development teams.
Our goal is simple: provide practical recommendations that help teams improve security, satisfy customer expectations, and prepare for evolving regulatory requirements. Now that this is written, we'll be taking this message to the LabVIEW community in upcoming conferences and presentations.
I'd like feedback from this community:
- What parts of the guide are most valuable?
- What recommendations seem difficult to apply in practice?
- What important topics are missing?
- What should we improve in the next revision?
The guide has been submitted for publication on the NI security website, but community members here get the first look.
