AWS Security Hub launches 15 new security controls
Share
Services
[AWS Security Hub](https://aws.amazon.com/security-hub/) has released 15 new security controls, increasing the number of controls offered to 307\. Security Hub now supports additional AWS services such as Amazon FSx and AWS Private Certificate Authority (AWS Private CA). Security Hub also released new controls against previously supported services like Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Kubernetes Service (Amazon EKS), and Amazon Simple Storage Service (Amazon S3). For the full list of recently released controls and the AWS Regions in which they are available, visit the [Security Hub user guide](https://docs.aws.amazon.com/securityhub/latest/userguide/doc-history.html).
To use the new controls, turn on the standard they belong to. Security Hub will then start evaluating your security posture and monitoring your resources for the relevant security controls. You can use [central configuration](https://docs.aws.amazon.com/securityhub/latest/userguide/central-configuration-intro.html) to do so across all your organization accounts and linked Regions with a single action. If you are already using the relevant standards and have Security Hub configured to automatically enable new controls, these new controls will run without taking any additional action.
To get started, consult the following list of resources:
* Learn more about Security Hub capabilities and features 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/) on the AWS Free Tier
What else is happening at Amazon Web Services?
Read update
Services
Share
Read update
Services
Share
Amazon Managed Service for Prometheus now supports configuring a minimum firing period for alerts
October 16th, 2024
Services
Share