Application Security

What Is SBOM?

SBOM is detail inventory of components that make up a software, including third-party and open-sources libraries, and framework version.

What Is SBOM (Software Bill of Materials)?

A Software Bill of Materials (SBOM) is detail inventory of components that make up a software, including third-party and open-sources libraries, and framework version. It’s like list of ingredient inside the application.

By keeping track every component inside application, the dev team can quicky detect when new vulnerabilitiies discover.

Why SBOM Matters in Cybersecurity

Modern application built by combining hundred or thousands third-party dependencies and open-source libraries to accelerate development. If one of those have vulnerabilities, it will place whole application into risk.

an SBOM help developer team to :

  • Identify vulnerabilities earlier by mapping affected component
  • Improve compliances with standards like NIST, ISO, or Executive Order 14028 in the U.S.
  • Enhance supply chain security by ensuring transparency in software composition
  • Build trust with customers and partners by showing what components are included

Key Elements of an SBOM

A proper SBOM usually includes:

  • Component name (e.g., lodash)
  • Version (e.g., 4.17.21)
  • License information (open source or proprietary)
  • Supplier (project or vendor that maintains it)
  • Relationships (how components depend on each other)

Example in Practice: The Apache Struts Breach (Equifax, 2017)

In 2017 attacker exploit critical vulnerability in Apache Struts Apache Struts framework (CVE-2017-5638), which was used in Equifax’s (American multinational consumer credit reporting agency) web applications. The patch of this vulnerability was available, but Equifax failed to apply in time.

Because the lacked visibility into all dependencies and libraries inside their application, the falw in Struts library went unnoticed, it lead to one of the largest data breaches in history, more than 147 million personal data exposed.

If an SBOM had been in place, Equifax could have quickly:

  • Identified that their applications were using the vulnerable version of Apache Struts
  • Prioritized patching as soon as the vulnerability was disclosed
  • Reduced the time attackers had to exploit the weakness

This case make us know how an SBOM have critical role to keep software components safe, helping organization act faster to newly disclose vulnerabilities

Ready to validate what matters?

Ready to validate what matters?

Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.

Qualification

Check whether AI Swarm Pentest fits your environment.

Share the minimum context. We will review the scope and tell you the next commercial step.

Before submitting — verify you fit

Teams with fewer than 50 developers: start a 14-day Trial instead of booking a demo. Start a 14-day Trial →

0 / 280

No commitment. If you don't fit, we'll tell you.

SAMPLE HANDOVER · ILLUSTRATIVE

Sample evidence handover

A trimmed view of what your team receives at the end of an AI Swarm Pentest engagement. Real engagements include full technical evidence, executive narrative, and a remediation plan.

VALIDATED FINDING Evidence attached

Server-Side Request Forgery in webhooks/receiver

demo-project/sample-app · src/webhooks/receiver.py:42

SeverityHigh CVSS 3.18.6 Priority79 Confirmedvia replay

Untrusted caller-supplied URLs reach an internal egress without an allowlist. Replayed in a sandbox against a fresh authorised target — the same control was validated to fail twice.

REVIEWER-READY REMEDIATION Merge-ready PR

Validate the target URL against an allowlist of permitted hostnames. Reject private/internal IP ranges. Enforce HTTPS only.

plexicus/remediation/webhooks-ssrf 3 changed · 0 new files
42resp = requests.get(target_url)
42+if not is_allowed_host(target_url):
43+  raise WebhookRejected(target_url)
44+resp = requests.get(target_url, timeout=5)
Every engagement hands over:
  • Executive briefing
  • Validated findings list
  • Merge-ready PRs
  • Compliance mapping (NIS2 · DORA · CRA)