de lista de materiales de software (SBOM)

An SBOM (Software Bill of Materials) is a complete inventory of all software components, libraries, and open-source or third-party dependencies in your application. It matters because it gives you the visibility to identify outdated software and known vulnerabilities, verify license compliance, and manage risk across your software supply chain. Think of it as a detailed ingredient list for your software.

MAS TRM Guidelines require financial institutions to assess and continuously monitor the security posture of third-party vendors and software. An SBOM scanner provides the component-level visibility needed to identify vulnerable or outdated dependencies in your software supply chain, demonstrate ongoing risk management to auditors, and maintain evidence of software integrity across your technology stack.

While Singapore does not currently mandate SBOM production in the way the US Executive Order 14028 does, the regulatory direction is clear. The amended Cybersecurity Act extends oversight to third-party and cloud systems. MAS TRM emphasises continuous third-party risk management. The Cyber Trust mark increasingly expects demonstrable software supply chain hygiene. Adopting SBOM scanning ensures your organisation remains in-step with these tightening regulatory expectations.

The Cyber Trust mark assesses an organisation’s cybersecurity practices relative to its risk profile, including how it manages third-party and software supply chain risks. Maintaining a current, accurate software inventory with identified vulnerabilities demonstrates the kind of proactive risk management the certification framework expects. Blacklock SBOM scanning provides this inventory on demand, with audit-ready reports.

SBOM scanning identifies outdated libraries, components with known CVEs, and packages with license restrictions or compliance obligations, giving you visibility into risks across your software dependencies. This visibility is particularly valuable for SaaS companies, FinTechs, and organisations in regulated sectors where a single vulnerable dependency could compromise customer data or service availability.

Key frameworks include: US Executive Order 14028 (SBOM required for software sold to US federal agencies), US FDA Section 524B (SBOM for connected medical devices), PCI DSS v4.0 (inventory of custom and third-party components), EU Cyber Resilience Act (SBOM in technical documentation), and ACSC Guidelines for Software Development (recommends SBOM provision to customers). In Singapore, while there is no direct SBOM mandate, MAS TRM’s third-party risk requirements and the Cyber Trust mark’s risk-based assessment both align with SBOM as a supporting practice.

Development teams, product owners, security practitioners, DevOps engineers, procurement teams, and compliance officers. Anyone responsible for knowing what’s inside your software and whether those components are secure, licensed appropriately, and up to date.

Nuestra herramienta analiza las bibliotecas y las versiones de paquetes compatibles en su base de código comparándolas con bases de datos de vulnerabilidades públicas, como la base de datos nacional de vulnerabilidades (NVD). Identifica las vulnerabilidades en función de las versiones de los componentes compatibles y te proporciona recomendaciones prácticas para priorizar y mitigar los riesgos.

The scanner analyses your codebase’s libraries and package versions against public vulnerability databases, including the National Vulnerability Database (NVD). It surfaces CVE IDs, severity levels, and CVSS scores for each affected component, along with actionable context to help your team prioritise remediation.

For every component in your SBOM, Blacklock shows both the version you’re currently running and the latest available version. This makes it straightforward to identify upgrade priorities and ensure your production software uses the most current, secure versions of its dependencies.

We recommend scanning after every significant code change or dependency update, and scheduling regular scans even during low-activity development periods. Continuous scanning keeps you ahead of newly disclosed vulnerabilities and ensures your SBOM remains an accurate, current record of your software composition.

SBOM scanning analyses your software’s components, libraries, and third-party dependencies before deployment, identifying risks linked to specific packages. Vulnerability scanning examines deployed systems in a live environment, detecting misconfigurations, open ports, and exploitable weaknesses. The two are complementary: SBOM scanning secures your code supply chain, while vulnerability scanning secures your running infrastructure.

Most small to mid-sized projects are completed within a few minutes. Larger codebases with extensive dependency trees may take longer, but the process is designed to minimise disruption to your development workflow.

SBOM scanning is priced per repository on a monthly or annual subscription. You can purchase a plan directly from your Blacklock account and scale up by adding repositories as your needs grow.