AWS Security Hub announces the AWS Resource Tagging Standard
Share
Services
Today, AWS Security Hub announces the release of the [AWS Resource Tagging standard](https://docs.aws.amazon.com/securityhub/latest/userguide/standards-tagging.html). The standard contains 85 new controls which can be used to identify if any of your AWS Resources are missing tag keys required by your organization. With the release of this standard, Security Hub now offers 386 security controls that automatically check the compliance of your AWS resources against pre-defined security principles and best practices.
To quickly enable the new standard across your AWS environment, you should use central configuration. This will allow you to enable the standard in some or all of your organization accounts and across all of AWS Regions that are linked to Security Hub with a single action. Furthermore, you can use central configuration to centrally define the requiredTagKeys parameter that specifies the tag keys that the new controls check for. Alternatively, if you are not using central configuration, you may enable the standard and define the tags that the controls will check for on an account-by-account and Region-by-Region basis. To learn more about using central configuration, visit the [AWS security blog](https://aws.amazon.com/blogs/security/introducing-new-central-configuration-capabilities-in-aws-security-hub/).
To get started with Security Hub, consult the following list of resources:
* Learn more about Security Hub capabilities and features, and the Regions in which they are available, in the [AWS Security Hub user guide](https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html)
* Subscribe to the [Security Hub SNS topic](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-announcements.html) to receive notifications about new Security Hub features and controls
* Try [Security Hub at no cost for 30 days](https://aws.amazon.com/security-hub/pricing/)
What else is happening at Amazon Web Services?
Amazon AppStream 2.0 users can now save their user preferences between streaming sessions
December 13th, 2024
Services
Share
AWS Elemental MediaConnect Gateway now supports source-specific multicast
December 13th, 2024
Services
Share
Amazon EC2 instances support bandwidth configurations for VPC and EBS
December 13th, 2024
Services
Share
AWS announces new AWS Direct Connect location in Osaka, Japan
December 13th, 2024
Services
Share
Amazon DynamoDB announces support for FIPS 140-3 interface VPC and Streams endpoints
December 13th, 2024
Services
Share