AWS Security Hub Adds SBOM Inventory
Security Hub now provides a Software Bill of Materials inventory for EC2, ECR, and Lambda via Amazon Inspector.
AWS Security Hub now provides an SBOM inventory for your compute resources
Editorial position: This addition helps central security teams map software dependencies across compute resources without new configuration.
The news, in plain English
AWS Security Hub now includes a Software Bill of Materials (SBOM) inventory. The inventory lists software packages and applications installed on EC2 instances, ECR container images, and Lambda functions. Security Hub builds this view from SBOMs generated by Amazon Inspector. The feature requires no new enablement and is included with Security Hub Essentials at no extra cost.
Technical context
Security Hub aggregates security findings and compliance results from multiple AWS services. With this update, it also collects SBOM data from Amazon Inspector. Inspector already generates SBOMs for EC2, ECR, and Lambda. Security Hub now consumes and presents these SBOMs in a central inventory. This inventory updates continuously as Inspector runs its assessments.
The SBOM inventory draws from Inspector’s existing capabilities, meaning no separate data collection pipelines or integrations are required. Security Hub presents the SBOM data alongside other security findings, providing a unified dashboard for security teams.
Where this fits in practice
For organizations with many compute resources, maintaining a complete SBOM can be challenging. Security Hub’s inventory offers a single source of truth that updates automatically when Inspector scans run. This can simplify vulnerability management, audit preparation, and policy enforcement.
In practice: Teams that already use Security Hub and Inspector will see the SBOM inventory populate automatically, provided Inspector is enabled on their resources. The inventory reflects the current state of each resource’s software stack as of the latest Inspector scan.
The feature is particularly useful for environments with frequent changes to software dependencies, such as development and testing workloads. It reduces the manual effort required to track and report on software components across distributed systems.
Adoption path
No new steps are required beyond existing Security Hub and Inspector configurations. If Inspector is already enabled on EC2 instances, ECR repositories, or Lambda functions, the SBOM inventory will appear in Security Hub. There is no additional setup or cost.
To begin using the SBOM inventory:
- Ensure Amazon Inspector is enabled on the target resources (EC2, ECR, Lambda).
- Access Security Hub via the AWS Management Console, AWS CLI, or SDKs.
- Navigate to the SBOM inventory section to view and manage the listed software components.
Watch out: The inventory only includes resources scanned by Inspector. Any resource not covered by Inspector will not be represented. Organizations must verify that Inspector covers all relevant compute resources to maintain a complete view.
Cost and operations
The SBOM inventory is included with Security Hub Essentials, which has its own pricing. There are no additional charges for this feature. Operational impact is minimal, as Security Hub only reads SBOM data generated by Inspector during its normal scans.
Since the SBOM inventory relies on Inspector’s existing scan schedule, there is no added performance overhead on the scanned resources. Security Hub’s processing of SBOM data is handled within its service infrastructure, so customers should not expect changes to their typical Security Hub performance characteristics.
Security and reliability
The announcement does not provide specific details on security controls or reliability metrics for the SBOM inventory. It relies on the existing security and reliability of Security Hub and Inspector. Security Hub applies its standard access controls and encryption to the SBOM inventory data, consistent with other Security Hub features.
As with other Security Hub data, customers should apply appropriate IAM policies to control access to the SBOM inventory. The service’s existing compliance certifications apply to this feature, but specific compliance attestations for the SBOM inventory are not detailed in the announcement.
Limits and trade-offs
The feature depends entirely on Amazon Inspector being enabled and running. If Inspector is not used or not covering certain resources, those resources will not appear in the SBOM inventory. The announcement does not specify any limits on the number of resources or SBOM size.
Customers should be aware that the SBOM inventory reflects the state of resources only as of the latest Inspector scan. Any changes to software components between scans will not be reflected until the next assessment. This introduces a potential lag in visibility, particularly for environments with very frequent changes.
Who should act
Security teams that use Security Hub and need a consolidated, up-to-date view of software dependencies across EC2, ECR, and Lambda should review this feature. It is particularly useful for organizations that manage many compute resources and want to simplify SBOM tracking.
The feature is most beneficial for teams responsible for vulnerability management, compliance reporting, or software license compliance. It can reduce the operational burden of maintaining separate SBOM tracking solutions and provide better integration with existing AWS security workflows.
Bottom line
AWS Security Hub’s new SBOM inventory offers a convenient, automatic way to track software packages on supported compute resources. It requires no new configuration and adds no cost beyond existing Security Hub usage. Teams already using Security Hub and Inspector can begin using it immediately.
The SBOM inventory improves visibility into software dependencies across EC2, ECR, and Lambda, helping security teams stay informed about the components running in their environment. Its automatic population and integration with Security Hub make it a low-effort addition for existing users.
Sources
AWS Security Hub now provides an SBOM inventory for your compute resources