AWS Security Incident Response now allows you to choose membership coverage for specific AWS organizational units (OUs) within an AWS Organization. While memberships previously covered all accounts in the selected AWS Organization, you now have the flexibility to choose which OUs to cover making it easier to try out the service and support your existing IR processes.
AWS Security Incident Response combines the power of automated monitoring and investigation, accelerated communication and coordination, and direct 24/7 access to the AWS Customer Incident Response Team (CIRT) to quickly prepare for, respond to, and recover from security events. This new feature allows you to enable Security Incident Response for specific types of workloads, such as production workloads, or for specific business subsidiaries that are grouped as OUs in their AWS Organization. You can also start with a pilot OU to evaluate the service’s effectiveness and refine processes before expanding coverage to your entire AWS Organization. All accounts within the selected OUs, including accounts under child OUs, are covered by the membership. Accounts added or removed from selected OUs will automatically update the coverage, making it easy for you to manage your AWS Security Incident Response membership.
Get started today by visiting AWS Security Incident Response via the AWS Management Console, AWS Command Line Interface (CLI), or AWS Software Development Kit (SDK). To learn more, see the AWS Security Incident Response documentation. For additional information on managing OUs with AWS Organizations, visit the AWS Organizations page.
Categories:
Source: Amazon Web Services
Latest Posts
- Amazon RDS for PostgreSQL supports minor versions 17.6, 16.10, 15.14, 14.19, and 13.22
- Noise suppression for dial-in participants in Teams audio conferences [MC1135397]
- Microsoft Teams | Manage voice and face recognition for rooms (MTR-W/MTRA) via device settings [MC1135396]
- Reporting labels retirement in Teams admin center [MC1135399]