An enterprise security platform detects an exposed cloud service API key in a public code repository. Arrange the steps of an automated Security Orchestration, Automation, and Response (SOAR) playbook into the correct operational sequence from initial alert detection to incident ticket resolution.
- 1Ingest and parse the alert payload received via webhook from the secret detection scanner.
- 2Query cloud IAM and SIEM logs to enrich the alert with identity context, key permissions, and active usage logs.
- 3Execute automated API calls to revoke the leaked API key and terminate associated active session tokens.
- 4Query cloud audit logs to extract all API actions initiated by the key prior to revocation and attach them to the case file.
- 5Generate a high-priority ticket in the ITSM platform and notify the Security Operations Center team with summary metrics.
Cevap
The correct operational sequence for the SOAR playbook is: (1) Ingest and parse the alert payload received via webhook from the secret detection scanner, (2) Query cloud IAM and SIEM logs to enrich the alert with identity context, key permissions, and active usage logs, (3) Execute automated API calls to revoke the leaked API key and terminate associated active session tokens, (4) Query cloud audit logs to extract all API actions initiated by the key prior to revocation and attach them to the case file, and (5) Generate a high-priority ticket in the ITSM platform and notify the Security Operations Center team with summary metrics.
A standard automated SOAR playbook follows a precise operational lifecycle: (1) Incident ingestion & parsing, (2) Contextual enrichment via integrations, (3) Rapid automated containment, (4) Forensic artifact collection, and (5) Incident documentation & analyst notification.
Adım Adım Çözüm
Anahtar Kavram
SOAR Incident Response Workflow Sequence