MITRE ATT&CK CoA - T1003 - OS Credential Dumping

This playbook Remediates the OS Credential Dumping technique 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 technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs). Techniques Handled: - T1003: OS Credential Dumping Kill Chain phases: - Defense Evasion MITRE ATT&CK Description: Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. Credentials can then be used to perform Lateral Movement and to access restricted information. Possible playbook uses: - The playbook can be used independently to handle and remediate the specific technique. - The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase. - The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.

MITRE ATT&CK - Courses of Action · 8 tasks · 0 inputs · 1 output

Details

ID	`MITRE ATT&CK CoA - T1003 - OS Credential Dumping`
From Version	6.5.0
Tasks	8

README

This playbook Remediates the OS Credential Dumping technique 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 technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).
Techniques Handled:

T1003: OS Credential Dumping

Kill Chain phases:

Defense Evasion

MITRE ATT&CK Description:
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. Credentials can then be used to perform Lateral Movement and to access restricted information.

Possible playbook uses:

The playbook can be used independently to handle and remediate the specific technique.
The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.

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

Set
IsIntegrationAvailable
SetGridField

Commands

This playbook does not use any commands.

Playbook Inputs

There are no inputs for this playbook.

Playbook Outputs

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

Playbook Image

MITRE ATT&CK CoA - T1003 - OS Credential Dumping

Outputs

Handled.Techniques — The techniques handled in this playbook

Flowchart

Source

playbook-CoA_-_T1003_-_OS_Credential_Dumping.yml

Download History Raw

description: "This playbook Remediates the OS Credential Dumping technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.\n \n***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs).\nTechniques Handled:\n- T1003: OS Credential Dumping\n\nKill Chain phases:\n- Defense Evasion\n\nMITRE ATT&CK Description:\nAdversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. Credentials can then be used to perform Lateral Movement and to access restricted information.\n\nPossible playbook uses:\n- The playbook can be used independently to handle and remediate the specific technique.\n- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.\n- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.\n"
id: MITRE ATT&CK CoA - T1003 - OS Credential Dumping
inputs: []
name: MITRE ATT&CK CoA - T1003 - OS Credential Dumping
outputs:
- contextPath: Handled.Techniques
  description: The techniques handled in this playbook
  type: unknown
starttaskid: "0"
tasks:
  "0":
    id: "0"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "17"
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      id: e1467f88-d838-49c8-81cc-5268ed1511fe
      iscommand: false
      name: ""
      version: -1
      description: ''
    taskid: e1467f88-d838-49c8-81cc-5268ed1511fe
    timertriggers: []
    type: start
    view: |-
      {
        "position": {
          "x": 990,
          "y": 1040
        }
      }
  "17":
    id: "17"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "28"
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      id: c5161232-bb3f-4c21-898c-a4be936a037e
      iscommand: false
      name: Cortex XDR monitors for behavioral events indicative of command and control activity
      type: title
      version: -1
      description: ''
    taskid: c5161232-bb3f-4c21-898c-a4be936a037e
    timertriggers: []
    type: title
    view: |-
      {
        "position": {
          "x": 990,
          "y": 1200
        }
      }
  "18":
    id: "18"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "26"
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: Cortex XDR monitors for behavioral events indicative of command and control activity.
      id: 9f42b7b0-7a8e-4151-8876-aa8ff52fdb7b
      iscommand: false
      name: Cortex XDR monitors for behavioral events indicative of command and control activity
      type: regular
      version: -1
    taskid: 9f42b7b0-7a8e-4151-8876-aa8ff52fdb7b
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 990,
          "y": 1690
        }
      }
  "19":
    id: "19"
    ignoreworker: false
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      id: 5fc441b8-efc5-458c-80f6-7e507d938f5d
      iscommand: false
      name: Done
      type: title
      version: -1
      description: ''
    taskid: 5fc441b8-efc5-458c-80f6-7e507d938f5d
    timertriggers: []
    type: title
    view: |-
      {
        "position": {
          "x": 990,
          "y": 2230
        }
      }
  "26":
    fieldMapping:
    - incidentfield: Handled Techniques
      output:
        simple: T1003
    id: "26"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "30"
    note: false
    quietmode: 0
    scriptarguments:
      append:
        simple: "true"
      key:
        simple: Handled.Techniques
      stringify: {}
      value:
        simple: T1003
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: Set a value in context under the key you entered.
      id: a57d372f-217d-4780-8004-11b36359b963
      iscommand: false
      name: Set technique handled
      script: Set
      type: regular
      version: -1
    taskid: a57d372f-217d-4780-8004-11b36359b963
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 990,
          "y": 1870
        }
      }
  "28":
    id: "28"
    ignoreworker: false
    nexttasks:
      '#default#':
      - "29"
      "yes":
      - "18"
    note: false
    quietmode: 0
    scriptarguments:
      brandname:
        simple: Cortex XDR - IR
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: Returns 'yes' if integration brand is available. Otherwise returns 'no'.
      id: 874b4f1f-7aa7-4fd8-877c-14c1e3bed3f3
      iscommand: false
      name: Is Cortex XDR integration Enabled?
      script: IsIntegrationAvailable
      type: condition
      version: -1
    taskid: 874b4f1f-7aa7-4fd8-877c-14c1e3bed3f3
    timertriggers: []
    type: condition
    view: |-
      {
        "position": {
          "x": 990,
          "y": 1350
        }
      }
  "29":
    id: "29"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "18"
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: |-
        Enable the Cortex XDR integration to follow this CoA.

        If needed - please contact your Palo Alto Networks account manager for future guidance and assistance.
      id: 5615c7f3-af3a-4f7c-8ae0-24e153894d86
      iscommand: false
      name: Manual - Enable Cortex XDR integration
      type: regular
      version: -1
    taskid: 5615c7f3-af3a-4f7c-8ae0-24e153894d86
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 1310,
          "y": 1520
        }
      }
  "30":
    continueonerror: true
    id: "30"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "19"
    note: false
    quietmode: 0
    scriptarguments:
      columns:
        simple: technique
      context_path:
        simple: Handled.Techniques
      grid_id:
        simple: handledtechniques
      keys: {}
      overwrite:
        simple: "true"
      sort_by: {}
      unpack_nested_elements: {}
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: Creates a Grid table from items or key-value pairs.
      id: 282ea06f-539b-4149-8e13-5a686f54a377
      iscommand: false
      name: Set grid field
      script: SetGridField
      type: regular
      version: -1
    taskid: 282ea06f-539b-4149-8e13-5a686f54a377
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 990,
          "y": 2050
        }
      }
version: -1
view: |-
  {
    "linkLabelsPosition": {
      "28_18_yes": 0.56
    },
    "paper": {
      "dimensions": {
        "height": 1255,
        "width": 700,
        "x": 990,
        "y": 1040
      }
    }
  }
tests:
- No tests (auto formatted)
fromversion: 6.5.0