SBOM
General inventory ofall software
components, libraries, packages, and
dependencies
Covers entire software systems
Focus on code components only
Used in traditional software
supply chain risk
management
Typical fields:
APISBOM
SBOM specialized for
API Inventory only
Includes API metadata like
version, owner, endpoints
Used for API Security
and API Supply Chain
V/S
• API name and version
• API endpoint list
• Which components are used in which
endpoints
• API-specific build & release info
• API Methods Used
• API security posture and vulnerability mapping
Additional fields
(on
top
of SBO
M
):
• Component name, version, supplier
• License type
• Checksums (hashes)
• Known vulnerabilities (CVEs)
4.
API version
Detailed
inventory of
API-SBOM
Standsfor API Software Bill of Materials.
All APIs in the
application
API OEM (Custom /
Commercial / Open Source)
API Vulnerability
API license
API Checksum
Enabling organizations toeasily
deploy cyber security solutions and
enhance their cyber security posture”
VISION & MISSION
What Guides Us..
“Making Security Simple”
11.
We are productinnovators and have four (4) indigenously
created cyber security products to address areas of:
Application Security Cyber-Resilience Cyber Training Cyber Incident Management
Empowering Cyber Resilience
#6 Cyclone DX - SBOM Generation, Vulnerability Management, License Compliance, Software Supply Chain Risk Management:, API and Service Transparency by supporting API SBOMs describing dependencies and integrations of APIs and microservices).
SWID- Software Inventory Management: , License Compliance, Security & Vulnerability Management, Automation & Configuration Management:
SPDX- License Compliance, SBOM Representation, Vulnerability Management, Supply Chain Documentation
#9 Benefits
Central inventory of all APIs, versions, endpoints, and dependencies
Proactively identify vulnerable or outdated APIs
Quickly trace affected APIs during security incidents
Meet compliance audits with ownership/licensing data
Better decisions on API lifecycle and security
Challenges
Hard to gather accurate API details across teams/environments
No universally accepted API-specific SBOM format
Most SBOM tools are package-focused, not API-aware
Frequent updates needed as APIs change fast
Teams may resist due to perceived extra work