Sekit CSF · Supply Chain Security · Technical
RCF-0330Software supply chain (SBOM)
Technical tools generate and analyse software bills of materials and alert when components with known vulnerabilities are detected
Mapping at a glance
RCF-0330Software supply chain (SBOM)Supply Chain Security · Technical
RCF-0330 maps to 6 controls across the published frameworks. +1 more in the table below. Open in the full graph →
Maps to ISO/IEC 27001:2022
Curated mapping with the reasoning, not just the codes.
A.5.21Managing information security in the ICT supply chainsupportsAutomated dependency scanning in the pipeline flags components with known vulnerabilities before release, the technical control that catches risk introduced deep in the ICT supply chain.A.8.8Management of technical vulnerabilitiessupportsAutomated dependency scanning in the pipeline flags components with known vulnerabilities before they ship, a supply-chain instance of A.8.8's technical vulnerability identification.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
GV.SC-06Due diligence before engagementID.AM-08Assets managed through lifecyclePR.PS-01Configuration management applied
Maps to Cyber Essentials
Curated mapping with the reasoning, not just the codes.
Evidence that proves this control
What an auditor, or Sekit's evidence engine, asks for.
Application security testing evidence
The proof that code and applications are automatically scanned for flaws (SAST/DAST), including dependencies and APIs.
From the Sekit evidence catalog
This topic through the other lenses
All Supply Chain Security controls
Ask Sekura: “What evidence proves RCF-0330?”
Also via MCP, free with account