• ISA provides technical resources and standards to help industrial automation professionals advance their careers and the field. We enable automation professionals worldwide to solve problems and enhance their skills by bringing people together to create new technologies and share best practices with future automation professionals.
    • Industry Insights

  • We attract over 140,000 unique automation professionals monthly, making us the premier online content provider and the only dedicated electronic magazine in the automation industry.

    Monthly Magazine

    Back
    Back
  • M logo for Automation.com Monthly. Link to current issue.

ENISA Publishes SBOM Advisory: What Does It Mean for the OT Cybersecurity Community?

By: Michelle Ritterskamp
Source: International Society of Automation (ISA)
18 November, 2026
3 min read
SBOM acronym text surrounded by digital component icons representing software bill of materials compliance and data protection. AdobeStock_2204794193.
SBOMs must be validated. Accurate software component information is necessary to support continuous cybersecurity risk management throughout a product’s operational life.

The European Union Agency for Cybersecurity, also known as ENISA, published its ENISA Technical Advisory for Software Bill of Materials in October 2026. From an operational technology (OT) cybersecurity engineering perspective, the document provides a resource for strengthening software supply chain security. The advisory addresses not only the generation of software bills of materials (SBOMs), but also the practical challenges of ensuring their accuracy, integrity, security, and usefulness throughout the software lifecycle.

A central message of the advisory is that software transparency alone is insufficient. The value of an SBOM depends on the processes used to generate, validate, protect, maintain, and integrate its information into ongoing cybersecurity and vulnerability management activities.

Takeaways from the advisory

SBOMs provide an important foundation for software supply chain transparency and accountability. During a recent ISA Global Cybersecurity Alliance (ISAGCA) webinar, “Never trust, always verify: How SBOMs can make or break your reputation,” William O’Connor, CSSLP, DevSecOps technical program manager at Rockwell Automation, stated, “We don’t release software without testing it, so we shouldn’t release an SBOM without validating it. An SBOM is only as good as the tools and the quality gate behind it.” Manufacturers can benefit from reliable information about the software components and dependencies incorporated into their products, while their customers can use this information to better understand potential vulnerabilities and cybersecurity risks.

Incomplete, inaccurate, or outdated SBOMs can undermine vulnerability identification and lead to incorrect security assessments. ENISA emphasizes the importance of standardized component identification, validation, cryptographic integrity, secure storage, and continuous maintenance to ensure that SBOM information remains dependable and relevant throughout the software lifecycle.

We can surmise that there is a benefit to integrating SBOMs into broader cybersecurity and risk management processes rather than just using them as compliance documents. Identifying a potential vulnerability is only the beginning. Organizations should also evaluate exploitability, exposure, asset criticality, and available mitigation measures to determine appropriate risk-based responses. O’Connor’s co-presenter, Peter Thermos, founder and CEO of Palindrome Technologies, shared that, in his opinion, “The SBOM must maintain three vital attributes, the three Cs: verifiable correctness, completeness, and consumable by third-party tools.”

Advertisement

For the industrial automation community, these principles are relevant. Accurate software component information can support more informed vulnerability management and maintenance decisions while helping to manage cybersecurity risks without unnecessarily disrupting operations.

Note that the SBOM does not establish conformity with any specific ISA/IEC 62443 requirement. It could be considered complementary rather than equivalent. Creating the SBOM also does not provide evidence that a product or system meets a specific security level. 

The advisory brings together guidance from Germany’s Federal Office for Information Security (BSI), the US Cybersecurity and Infrastructure Security Agency (CISA), and widely adopted SBOM formats such as SPDX and CycloneDX. All can be referenced as helpful when understanding the creation of the SBOM. Interestingly, ENISA shares that its new advisory is not mandatory Cyber Resilience Act (CRA) guidance, nor does it establish its advisory as legal or regulatory obligations to follow.

The OT cybersecurity community and SBOMs

The ENISA advisory reinforces an important cybersecurity principle: effective software supply chain security requires visibility into the components that make up a product, confidence in the accuracy and integrity of that information, and processes for using it to support informed cybersecurity decisions throughout the software lifecycle.

Although ENISA does not specifically reference ISA/IEC 62443, its recommendations complement established OT cybersecurity practices, particularly those addressing secure product development, software component management, vulnerability handling, and lifecycle security. Integrating SBOM practices into an ISA/IEC 62443-based cybersecurity program can strengthen software supply chain visibility and support more informed risk management decisions.

Advertisement

An SBOM should be viewed not simply as a software inventory or compliance artifact, but as an important source of information supporting continuous cybersecurity risk management throughout a product’s operational life. In ISAGCA’s recent SBOM webinar, our speakers discussed that this visibility can be important in industrial environments because software is often embedded within physical equipment, including controllers, gateways, and other shared connected devices.

According to O’Connor: “You can’t secure what you can’t see. For industrial products, that means more than open-source libraries. It means firmware, RTOS, protocol stacks, and even the components inside of the hardware.” SBOM generation, component management, vulnerability handling, and maintenance can support relevant lifecycle processes.

Thermos added: “Reputation is decided on a supplier’s reaction time after a critical vulnerability is disclosed. This reaction time relies heavily on the effectiveness of the vulnerability disclosure process, and an independent certification provides that assurance.” When added as complementary documentation to established cybersecurity frameworks such as ISA/IEC 62443, SBOM practices can contribute to a more transparent, accountable, and resilient industrial automation supply chain.

Additional resources

Previous Column Article Next Column Article
Advertisement

Trending Articles

Advertisement

Related Articles

View all Articles and News
Advertisement
Advertisement