An enterprise financial institution is preparing to integrate a third-party payment processing API into its core banking platform. During the vendor risk assessment, the security team notes that while the primary vendor adheres to strong internal security standards, the API relies on multiple embedded open-source components and downstream software dependencies. To continuously track, evaluate, and respond to vulnerabilities originating within these embedded components across the software deployment lifecycle, which of the following mechanisms should the security team require from the vendor?
- A Software Bill of Materials (SBOM) paired with continuous component vulnerability managementAnswer
- BA SOC 2 Type I attestation report evaluating system availability and security control design
- CA Service Level Agreement (SLA) mandating sub-hour incident notification for operational outages
- DAn Interconnection Security Agreement (ISA) defining encrypted transit channels for network data flow
Answer
A Software Bill of Materials (SBOM) paired with continuous component vulnerability management
A Software Bill of Materials (SBOM) is a formal, structured record containing the details and supply chain relationships of various components used in building software. When combined with automated vulnerability management, it allows organizations to maintain complete visibility into nested third-party libraries and instantly identify exposed software components when new vulnerabilities are discovered.
Step-by-Step Solution
Key Concept
Software Supply Chain Oversight and Software Bill of Materials (SBOM)