Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/socfortress/Playbooks
Playbooks for SOC Analysts
https://github.com/socfortress/Playbooks
Last synced: about 3 hours ago
JSON representation
Playbooks for SOC Analysts
- Host: GitHub
- URL: https://github.com/socfortress/Playbooks
- Owner: socfortress
- Created: 2022-09-21T11:56:09.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2022-12-11T22:48:25.000Z (about 2 years ago)
- Last Synced: 2023-05-25T22:35:15.072Z (over 1 year ago)
- Size: 6.02 MB
- Stars: 26
- Watchers: 2
- Forks: 12
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-rainmana - socfortress/Playbooks - Playbooks for SOC Analysts (Others)
README
# Table of Content
[[_TOC_]]# IR Playbooks
This repository contains all the Incident Response Playbooks and Workflows of Company's SOC.Each folder contains a Playbook that is broken down into 6 section as per [NIST - 800.61 r2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf)
## 1- Preparation
This section should include the following informations
- List of _ALL_ Assets
- Servers
- Endpoints (+critical ones)
- Networks
- Applications
- Employees
- Security Products
- Baselines
- Communication Plan
- Which Security Events
- Thresholds
- How to access Security Tools
- How to provision access
- Create Playbooks
- Plan Exercises
- Table Top
- Hands On## 2- Detection and Analysis
This section should include the following informations
- Gathering of Information
- Analyzing the Data
- Building Detections
- Root Cause Analysis
- Depth and Breath of the Attack
- Admin Rights
- Affected Systems
- Techniques Used
- Indicators of Compromise / Indicators of Attack
- Tactics Techniques and Procdures (TTP)
- IP Address
- Email Address
- File Hash
- Command Line
- etc.
## 3- Containment, Eradication, and Recovery
This section should include the following informations
- Isolate Affected Systems
- Patch Threat Entry Point
- Predefine threshold
- For Customers
- For internal systems
- For escalations
- Preauthorized actions
- Per customers
- Per environment
- Prod
- QA
- Internet Facing
- How to Remove the Threat on All Affected Systems
- Get Systems Operational
- Rebuilt and Resume Service## 4- Post-Incident Activity
- Lessons Learn
- New Detection
- New Hardening
- New Patch Management
- etc.
# Directory Structures
## Customers
This folder includes all the informations related to our customers such as- Contacts
- Names
- Phone Number
- Escalation point
- Business hours
- Off Hours
- Account Manager
- Pre-approved Actions and Threshold
- Blackout / Brownout schedule## Products
This folder contains information about the various "commercial" products we use during an incident.
For example:
- JIRA
- Remedy
- Service-Now
- ArcSight
- Elastic Stack
- RSA NetWitness
- Splunk
- AMP
- CrowdStrike
- McAfee
- Microsoft ATP
- Symantec
- Firepower
- Fortigate
- Etc.## IRP-*
These are the individual folders containing the Playbooks themselves
Within each directory there should be a PDF folder where a PDF version is available (and auto generated) for auditors and customers who requiere to see them# Create a new Playbook
## Folder & Files
To create a new Playbook:
- Create a new folder ex: `IRP-DDoS`
- Create a file called `README.md` inside your new folder
- Paste the content of `IRP-TEMPLATE.md`
- Replace the string `-NAME-` for your playbook name ex: `DDoS` in all the document
- Edit the sections.## Workflows
To create the Workflows
- Inside your new folder create a folder called `Workflows`
- Open the file `WORKFLOW-TEMPLATE.drawio` in [Draw.io](https://app.diagrams.net)
- Save locally until you have completed all the tabs
- Once all the tabs/phases are completed, upload a copy to your new `Workflows` folder
- Use the `File -> Export as -> PNG` function of Draw.io to save each diagram phase separatly
- Make sure you Unchecked `Include a copy of the diagram`
- Click `Export`
- Save locally
- Upload each .PNG file to your new `Workflows` folder