Published: 10 March 2020
Summary
Security operations can always benefit from more efficiency, and organizations are exploring SOAR as a potential solution. This research helps security and risk management technical professionals determine if a SOAR platform is the right choice when adding automation to their security operations.
Included in Full Research
- Defining SOAR
- The Four Core Engines of SOAR
- Workflow and Collaboration Engine
- Ticket and Case Management Engine
- Orchestration and Automation Engine
- Threat Intelligence Management Engine
- Prerequisites and Dependencies for SOAR
- Operational Metrics
- Defined Processes
- Trained Operators
- Documented Workflow
- Supported Technology Integrations
- Architecting the Inception of Security Automation
- SOAR Use-Case Examples
- SIEM Alert Handling (Team: Alert and Triage)
- Phishing Email and Other Suspicious Email Response (Team: Incident Reponses)
- Intelligence Management (Team: Threat Intelligence)
- Compliance Tracking (Team: Corporate Governance and Compliance)
- Running Consistent and Collaborative Incident Response (Team: IR)
- Security Incident Case Enrichment (Team: IR)
- Putting It All Together: A SOAR Assessment Company Example
- SOAR Justification Example: XYZ Corp. Quick Facts
- SOAR for Phishing Use-Case Justification Example
- Strengths
- Weaknesses
- Demystify and Socialize the Limits and Real Possibilities of Security Automation
- Choose a Candidate Use Case
- Check Dependencies
- Use Ideal Operational Metrics as SOAR Design Requirements
- Evaluate SOAR Platforms Against Specific Metrics
- Create a Justification Report of Both Hard and Soft Values