MITRE ATT&CK - Courses of Action

This is the parent playbook, which contains all phases and remediates MITRE ATT&CK techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. The playbook utilizes several other MITRE ATT&CK remediation playbooks. The playbook follows the MITRE ATT&CK kill chain phases and takes action to protect the organization from the inputted techniques, displaying and implementing security policy recommendations for Palo Alto Networks products. ***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs). Possible playbook triggers: - The playbook can be triggered by a feed integration fetching indicators that contain MITRE ATT&CK techniques as “Feed Related Indicators”, using the "MITRE ATT&CK - Courses of Action - Job" playbook. - The playbook can be triggered manually for specific MITRE ATT&CK techniques using the ‘techniqueByIncident’ playbook input. - An incident that contains MITRE ATT&CK technique IDs using the ‘techniqueByIncident’ playbook input.

MITRE ATT&CK - Courses of Action · 26 tasks · 5 inputs · 1 output

Details

IDMITRE ATT&CK - Courses of Action
From Version6.5.0
Tasks26

README

This is the parent playbook, which contains all phases and remediates MITRE ATT&CK techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. The playbook utilizes several other MITRE ATT&CK remediation playbooks.

The playbook follows the MITRE ATT&CK kill chain phases and takes action to protect the organization from the inputted techniques, displaying and implementing security policy recommendations for Palo Alto Networks products.

***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Possible playbook triggers:

  • The playbook can be triggered by a feed integration fetching indicators that contain MITRE ATT&CK techniques as “Feed Related Indicators”, using the “MITRE ATT&CK - Courses of Action - Job” playbook.
  • The playbook can be triggered manually for specific MITRE ATT&CK techniques using the ‘techniqueByIncident’ playbook input.
  • An incident that contains MITRE ATT&CK technique IDs using the ‘techniqueByIncident’ playbook input.

Dependencies

This playbook uses the following sub-playbooks, integrations, and scripts.

Sub-playbooks

  • Courses of Action - Command and Control
  • Courses of Action - Initial Access
  • Courses of Action - Credential Access
  • Courses of Action - Defense Evasion
  • Courses of Action - Execution
  • Courses of Action - Exfiltration
  • Courses of Action - Persistence
  • Courses of Action - Lateral Movement
  • Courses of Action - Collection
  • Courses of Action - Privilege Escalation
  • Courses of Action - Discovery
  • Courses of Action - Impact

Integrations

This playbook does not use any integrations.

Scripts

  • Set

Commands

  • findIndicators
  • setIncident
  • appendIndicatorField
  • closeInvestigation

Playbook Inputs

Name Description Default Value Required
TechniquesList MITRE ATT&CK ID of a technique, or comma-separated list of techniques IDs. incident.techniqueslist Optional
template Template name to enforce WildFire best practices profile.   Optional
pre_post Rules location. Can be ‘pre-rulebase’ or ‘post-rulebase’. Mandatory for Panorama instances.   Optional
device-group The device group for which to return addresses (Panorama instances).   Optional
tag Tag for which to filter the rules.   Optional

Playbook Outputs

Path Description Type
Handled.Techniques The techniques handled in this playbook unknown

Playbook Image

MITRE ATT&CK - Courses of Action

Inputs

  • TechniquesList — MITRE ATT&CK ID of a technique, or comma-separated list of techniques IDs.
  • template — Template name to enforce WildFire best practices profile.
  • pre_post — Rules location. Can be 'pre-rulebase' or 'post-rulebase'. Mandatory for Panorama instances.
  • device-group — The device group for which to return addresses (Panorama instances).
  • tag — Tag for which to filter the rules.

Outputs

  • Handled.Techniques — The techniques handled in this playbook

Commands used

appendIndicatorField closeInvestigation findIndicators setIncident

Flowchart

no yes yes yes yes Start Start Courses of Action - Collection - Courses of Action - Collection Courses of Action - Colle... Courses of Action - Collection Courses of Action - Credential Access - Courses of Action - Credential Access Courses of Action - Crede... Courses of Action - Credentia... Courses of Action - Defense Evasion - Courses of Action - Defense Evasion Courses of Action - Defen... Courses of Action - Defense E... Courses of Action - Discovery - Courses of Action - Discovery Courses of Action - Disco... Courses of Action - Discovery Courses of Action - Execution - Courses of Action - Execution Courses of Action - Execu... Courses of Action - Execution Courses of Action - Exfiltration - Courses of Action - Exfiltration Courses of Action - Exfil... Courses of Action - Exfiltration Courses of Action - Impact - Courses of Action - Impact Courses of Action - Impact Courses of Action - Impact Courses of Action - Initial Access - Courses of Action - Initial Access Courses of Action - Initi... Courses of Action - Initial A... Courses of Action - Persistence - Courses of Action - Persistence Courses of Action - Persi... Courses of Action - Persistence Courses of Action - Privilege Escalation - Courses of Action - Privilege Escalation Courses of Action - Privi... Courses of Action - Privilege... Close Investigation? Close Investigation? Courses of Action - Lateral Movement - Courses of Action - Lateral Movement Courses of Action - Later... Courses of Action - Lateral M... Courses of Action - Command and Control - Courses of Action - Command and Control Courses of Action - Comma... Courses of Action - Command a... Close Investigation - closeInvestigation Close Investigation closeInvestigation Done Done Manual investigation and review Manual investigation and ... Are there techniques to handle? Are there techniques to h... Set techniques to context Set techniques to context Tag MITRE ATT&CK indicators as handled - appendIndicatorField Tag MITRE ATT&CK indicato... appendIndicatorField Find indicators from type Attack Pattern - findIndicators Find indicators from type... findIndicators Are there Attack Pattern indicators? Are there Attack Pattern ... Tag Attack Pattern indicators as handled - appendIndicatorField Tag Attack Pattern indica... appendIndicatorField Are there indicators to tag? Are there indicators to tag? Configure Layout Configure Layout Add descriptions to layout - setIncident Add descriptions to layout setIncident

Source

playbook-MITRE_-_Courses_of_Action.yml playbook-MITRE_-_Courses_of_Action_Trigger_Job.yml playbook-MITRE_-_Courses_of_Action_Trigger_Job_README.md
Download History Raw 
This is a wrapper playbook for the "MITRE ATT&CK - Courses of Action" use-case.

Possible playbook triggers:
- Through a job, by a feed integration fetching indicators that contain MITRE ATT&CK techniques as “Feed Related Indicators”, or with custom inputs.
- Through an incident, using custom playbook inputs.

Once triggered, the playbook will create a new incident from type "MITRE ATT&CK CoA". The incident will trigger the playbook "MITRE ATT&CK - Courses of Action", 
which contains all phases and remediates MITRE ATT&CK techniques using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team. 
 
***Disclaimer: This playbook does not simulate an attack using the specified techniques, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).


## Dependencies
This playbook uses the following sub-playbooks, integrations, and scripts.

### Sub-playbooks
This playbook does not use any sub-playbooks.

### Integrations
This playbook does not use any integrations.

### Scripts
* SearchIndicatorRelationships
* Set
* DeleteContext

### Commands
* closeInvestigation
* findIndicators
* createNewIncident

## Playbook Inputs
---

| **Name** | **Description** | **Default Value** | **Required** |
| --- | --- | --- | --- |
| techniqueByIncident | MITRE ATT&CK ID of a technique, or comma-separated list of techniques IDs. |  | Optional |
| Indicator Query | Define a query that will retrieve indicators that contain MITRE ATT&amp;amp;CK techniques under the "Feed Related Indicators" field.<br/>\(Possible query example: \`feedrelatedindicators.type:"MITRE ATT&amp;amp;CK"\`\) | type:"Attack Pattern" or type:Report and feedrelatedindicators.type:"MITRE ATT&amp;CK" | Optional |
| template | Template name to enforce WildFire best practices profile. |  | Optional |
| pre_post | Rules location. Can be 'pre-rulebase' or 'post-rulebase'. Mandatory for Panorama instances. |  | Optional |
| device-group | The device group for which to return addresses \(Panorama instances\). |  | Optional |
| tag | Tag for which to filter the rules. |  | Optional |
| query_type | The type of the indicator query this playbook is running. Possible values can be:<br/>Direct - The playbook query returns a list of "STIX ATT&amp;amp;CK Pattern" indicators.<br/>,relationship,unit42,other |  | Optional |

## Playbook Outputs
---

| **Path** | **Description** | **Type** |
| --- | --- | --- |
| Handled.Techniques | The techniques handled in this playbook | unknown |

## Playbook Image
---
![MITRE ATT&CK - Courses of Action Trigger Job](../doc_files/MITRE_ATTand
CK_-_Courses_of_Action_Trigger_Job.png)