Broot Security logo
BROOT SECURITY
Capabilities / SCA

Software Composition Analysis (SCA)

Third-party library audits, licensing checks, and dependency chain vulnerability scanning.

Last reviewed by Rhitik Kumar, Lead Offensive Security Engineer.

Scope of Assessment

Software composition analysis secures your supply chain. Open-source packages are checked for known vulnerabilities such as Log4j, licence compliance is audited, and your full dependency tree is mapped.

Third-party package vulnerability audits
Open-source licensing compliance
Dependency tree tracking
SBOM generation

Engagement Details

Audit Duration3-5 Business Days
Lead CredentialsOSCP / OSWE / CISSP Certified
Retests Included1 Free Retest (within 30 days)

How the engagement runs

  1. 01

    Dependency inventory

    Direct and transitive dependencies are enumerated from your manifests and lockfiles, including container base images where those are in scope.

  2. 02

    Vulnerability correlation

    Each component and version is matched against public vulnerability databases and advisories, then filtered by whether the vulnerable code path is actually reachable in your application.

  3. 03

    Licence and supply chain review

    Licences are checked for obligations and conflicts, and packages are reviewed for typosquatting, abandonment and unexpected maintainer changes.

  4. 04

    SBOM and remediation plan

    You get a standards-compliant SBOM plus an upgrade path ordered by real risk, so the work is a short list rather than a thousand-row scanner export.

What you receive

  • CycloneDX or SPDX Software Bill of Materials
  • Vulnerable dependency list filtered for reachability
  • Licence compliance report with obligations and conflicts
  • Prioritised upgrade path with breaking-change notes
  • CI integration guidance to keep the inventory current

Frequently Asked Questions

Do you generate Software Bill of Materials (SBOM)?

Yes. We generate standard cycloneDX or SPDX SBOM formats for compliance reviews.

Our scanner already reports hundreds of issues. How is this different?

Most of those are not reachable from your code. Findings are filtered for exploitability so remediation targets the handful that matter instead of the full export.

Do you cover container images?

Yes. Base image and OS package layers are inventoried alongside application dependencies where containers are in scope.

Can this run in our pipeline?

Yes. Part of the deliverable is getting the check into CI so the inventory stays current after the engagement ends.

Let's map out your testing strategy.

Have a custom compliance framework or specific targeting parameters? Schedule a scoping session with our senior offensive leads.