Run stage: Optimizing your cloud security operations

After you implement a baseline in the walk stage, your organization progresses to the run stage. This stage is focused on demonstrating the cybersecurity capabilities that are available in the cloud, many of which are not possible or are very difficult to implement with on-premises solutions. This stage brings together different security components and automates processes. Automations free up your resources so that they can focus on high-value work.
The following is the only phase in the run stage:
Optimize – How do I improve this process and add automation?
Optimize
In the optimize phase, you automate your security operations. Like the crawl and walk stages, you can use AWS Security Hub CSPM during the run stage to achieve automation and iteration. The following image shows how Security Hub CSPM can trigger a custom Amazon EventBridge rule that defines automatic actions to take against specific findings and insights. For more information, see Automations in the Security Hub CSPM documentation.

By using Security Hub CSPM as a central automation hub, you can also forward activities to Splunk
The following is an example of repeated automated actions, as shown in the previous image:
Use Splunk to detect questionable activity.
Use Step Functions to collect logs, revoke access, quarantine, and take forensic snapshots.
Use an EventBridge rule to start a Lambda function that quarantines, takes forensic snapshots, and replaces compromised servers with a golden image.
Start a Lambda function that uses Systems Manager to remediate and apply patches throughout the rest of the environment.
Start an Amazon SQS message that uses the Rapid7
scanner to scan and validate whether the AWS resource is secure.
For more information, see How to automate incident response in the AWS Cloud for EC2 instances