AWS Security Hub now infers resource criticality from installed software and usage
News
AWS Security Hub now infers resource criticality from installed software and resource usage patterns, enabling better prioritization of security exposures.
- Criticality signals now include installed software and resource usage alongside existing tags and names
- Resources with inconsistent tagging receive meaningful criticality scores without manual configuration
- Example: EC2 instances running databases with steady traffic receive higher criticality than idle monitoring instances
- Included in Security Hub Essentials plan at no additional cost with no new enablement required
This enhancement helps central security teams prioritize exposures affecting their most critical resources more effectively.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Oct 14
2026
2026
AWS Security Hub now supports resource criticality for prioritization
Nov 17
2026
2026
AWS Security Hub now detects when vulnerable software is running on Amazon EC2 instances
Nov 6
2026
2026
AWS Security Hub now provides an SBOM inventory for your compute resources
Dec 2
2025
2025
AWS Security Hub now generally available with near real-time analytics and risk prioritization
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.