AWS Systems Manager - Stop Managed EC2 Instances IP Entity Trigger

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Content Index

This playbook can be used by SOC Analysts to stop malicious or compromised EC2 instances in AWS. The playbook can be triggered from an IP entity context in an incident. The playbook takes the private IP and stops the managed EC2 instances using the Instance ID. The playbook also adds a comment to the incident with instance that was stopped.

Attribute Value
Type Playbook
Solution AWS Systems Manager
Source View on GitHub

Additional Documentation

📄 Source: AWSSystemsManagerPlaybooks/AWS-SSM-StopManagedInstance-IPEntityTrigger/readme.md

AWS-SSM-StopManagedInstance-IPEntityTrigger

Summary

This playbook can be used by SOC Analysts to stop malicious or compromised EC2 instances in AWS. The playbook can be triggered from an IP entity context in an incident. The playbook takes the private IP address and stops the managed EC2 instances using the Instance ID. The playbook also adds a comment to the incident with instance that was stopped.

Playbook performs the following actions:

  1. Get the private IP address from the IP Entity.
  2. Get the Instance ID of Managed EC2 instance for given private IP.
  3. Stop the EC2 instance using the Instance ID.
  4. Add a comment to the incident with the instance that was stopped.



Prerequisites

  1. Prior to the deployment of this playbook, AWS Systems Manager API Function App Connector needs to be deployed under the same subscription.
  2. Refer to AWS Systems Manager API Function App Connector documentation to obtain AWS Access Key ID, Secret Access Key and Region.

Deployment instructions

  1. To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
  2. Fill in the required parameters:
    • Playbook Name
    • Functions App Name - Name of the Function App where the AWS Systems Manager API Function App Connector has been deployed.

Deploy to Azure Deploy to Azure

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

  1. Click the Microsoft Sentinel connection resource
  2. Click edit API connection
  3. Click Authorize
  4. Sign in
  5. Click Save
  6. Repeat steps for other connections

b. Assign Playbook Microsoft Sentinel Responder Role

  1. Select the Playbook (Logic App) resource
  2. Click on Identity Blade
  3. Choose System assigned tab
  4. Click on Azure role assignments
  5. Click on Add role assignments
  6. Select Scope - Resource group
  7. Select Subscription - where Playbook has been created
  8. Select Resource group - where Playbook has been created
  9. Select Role - Microsoft Sentinel Responder
  10. Click Save

c. Function App Settings Update Instructions

Refer to AWS Systems Manager API Function App Connector documentation for Function App Application Settings (Access Key ID, Secret Access Key and Region) update instruction.

References

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Playbooks · Back to AWS Systems Manager