SBOMs Are Shifting From Best Practice to Legal Obligation, Says InfoQ

In a report from InfoQ covering Viktor Petersson’s talk at QCon London 2026, he warned that Software Bills of Materials (SBOMs) are no longer just a security best practice but are rapidly becoming mandatory due to emerging regulations like the EU Cyber Resilience Act, U.S. Executive Order 14028, FDA device rules, and PCI‑DSS requirements. Petersson explained practical details on generating high‑quality SBOMs, differences between dominant formats like SPDX and CycloneDX, the importance of signing and lifecycle‑managing SBOM artifacts in CI/CD pipelines, and common pitfalls such as merging disparate SBOMs or skipping signing. He stressed teams must treat SBOMs as managed engineering artifacts rather than ad‑hoc documents if they want to meet upcoming compliance windows and improve software supply‑chain transparency.

https://www.infoq.com/news/2026/03/sbom-viktor-petersson/

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

Secure Vibe Coding Guide: Best Practices for Writing Secure Code

Ken Huang's "Secure Vibe Coding Guide" emphasizes the importance of integrating security into the software development lifecycle. The guide provides best practices for writing secure code, including input validation, proper authentication mechanisms, and secure data storage techniques. It also highlights the necessity of regular code reviews and staying updated with the latest security vulnerabilities and patches. By following these guidelines, developers can create applications that are resilient against common security threats and contribute to a safer digital environment.  https://kenhuangus.substack.com/p/secure-vibe-coding-guide
Read more

KEVIntel: Real-Time Intelligence on Exploited Vulnerabilities

KEVIntel is a dynamic platform providing up-to-date information on known exploited vulnerabilities (KEVs). It aggregates data from over 50 public sources, including CISA, and enriches each entry with metadata such as EPSS scores, online mentions, scanner inclusion, and exploitation status. The platform aims to serve as an early warning system, offering insights even before official publications. KEVIntel supports various formats like JSON, CSV, and RSS, facilitating integration into security operations. These entries include CVSS scores, exploit status, and links to proof-of-concept code, aiding organizations in prioritizing remediation efforts.   https://kevintel.com/
Read more