MITRE ATT&CK CoA - T1547.001 - Registry Run Keys Startup Folder

This playbook Remediates the Registry Run Keys / Startup Folder 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: - T1547.001: Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder Kill Chain phases: - Persistence - Privilege Escalation MITRE ATT&CK Description: Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. [1] These programs will be executed under the context of the user and will have the account's associated permissions level. Placing a program within a startup folder will also cause that program to execute when a user logs in. There is a startup folder location for individual user accounts as well as a system-wide startup folder that will be checked regardless of which user account logs in. The startup folder path for the current user is C:\Users[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. The startup folder path for all users is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp. 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 · 7 tasks · 0 inputs · 1 output

Details

ID	`MITRE ATT&CK CoA - T1547.001 - Registry Run Keys Startup Folder`
From Version	6.5.0
Tasks	7

README

This playbook Remediates the Registry Run Keys / Startup Folder 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:

T1547.001: Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder

Kill Chain phases:

Persistence
Privilege Escalation

MITRE ATT&CK Description:
Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the “run keys” in the Registry or startup folder will cause the program referenced to be executed when a user logs in. [1] These programs will be executed under the context of the user and will have the account’s associated permissions level.

Placing a program within a startup folder will also cause that program to execute when a user logs in. There is a startup folder location for individual user accounts as well as a system-wide startup folder that will be checked regardless of which user account logs in. The startup folder path for the current user is C:\Users[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. The startup folder path for all users is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp.

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
SetGridField
IsIntegrationAvailable

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 - T1547.001 - Registry Run Keys Startup Folder

Outputs

Handled.Techniques — The techniques handled in this playbook

Flowchart

Source

playbook-CoA_-_T1547.001_-_Registry_Run_Keys_Startup_Folder.yml

Download History Raw

description: "This playbook Remediates the Registry Run Keys / Startup Folder 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- T1547.001: Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder\n\nKill Chain phases:\n- Persistence\n- Privilege Escalation\n\nMITRE ATT&CK Description:\nAdversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the \"run keys\" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. [1] These programs will be executed under the context of the user and will have the account's associated permissions level.\n\nPlacing a program within a startup folder will also cause that program to execute when a user logs in. There is a startup folder location for individual user accounts as well as a system-wide startup folder that will be checked regardless of which user account logs in. The startup folder path for the current user is C:\\Users[Username]\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\Startup. The startup folder path for all users is C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp.\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 - T1547.001 - Registry Run Keys Startup Folder
inputs: []
name: MITRE ATT&CK CoA - T1547.001 - Registry Run Keys Startup Folder
outputs:
- contextPath: Handled.Techniques
  description: The techniques handled in this playbook
  type: unknown
starttaskid: "0"
tasks:
  "0":
    id: "0"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "4"
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      id: d2a03a6a-ce1b-48af-88ea-ce412bd17ef0
      iscommand: false
      name: ""
      version: -1
      description: ''
    taskid: d2a03a6a-ce1b-48af-88ea-ce412bd17ef0
    timertriggers: []
    type: start
    view: |-
      {
        "position": {
          "x": 50,
          "y": -220
        }
      }
  "1":
    id: "1"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "3"
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: Manual - Configure XDR Behavioral Threat Protection under the Malware Security Profile.
      id: 95b39f35-a0d6-430b-8af5-78f3cb5ee4fe
      iscommand: false
      name: Manual - Configure XDR Behavioral Threat Protection under the Malware Security Profile
      type: regular
      version: -1
    taskid: 95b39f35-a0d6-430b-8af5-78f3cb5ee4fe
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 50,
          "y": 275
        }
      }
  "2":
    id: "2"
    ignoreworker: false
    note: false
    quietmode: 0
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      id: e13affdd-68db-4873-82e4-f9f78838b033
      iscommand: false
      name: Done
      type: title
      version: -1
      description: ''
    taskid: e13affdd-68db-4873-82e4-f9f78838b033
    timertriggers: []
    type: title
    view: |-
      {
        "position": {
          "x": 50,
          "y": 825
        }
      }
  "3":
    id: "3"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "6"
    note: false
    quietmode: 0
    scriptarguments:
      append:
        simple: "true"
      key:
        simple: Handled.Techniques
      stringify: {}
      value:
        simple: T1547.001
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: Set a value in context under the key you entered.
      id: d54bcabd-dcc2-466d-8615-8a034b0f3638
      iscommand: false
      name: Set technique handled
      script: Set
      type: regular
      version: -1
    taskid: d54bcabd-dcc2-466d-8615-8a034b0f3638
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 50,
          "y": 460
        }
      }
  "4":
    id: "4"
    ignoreworker: false
    nexttasks:
      '#default#':
      - "5"
      "yes":
      - "1"
    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: aaf9eaaa-a8be-497c-82c4-b1e1c63b963a
      iscommand: false
      name: Is Cortex XDR integration Enabled?
      script: IsIntegrationAvailable
      type: condition
      version: -1
    taskid: aaf9eaaa-a8be-497c-82c4-b1e1c63b963a
    timertriggers: []
    type: condition
    view: |-
      {
        "position": {
          "x": 50,
          "y": -70
        }
      }
  "5":
    id: "5"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "1"
    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: 29f4d063-883e-4a5f-8049-7ad34a973936
      iscommand: false
      name: Manual - Enable Cortex XDR integration
      type: regular
      version: -1
    taskid: 29f4d063-883e-4a5f-8049-7ad34a973936
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 480,
          "y": 100
        }
      }
  "6":
    id: "6"
    ignoreworker: false
    nexttasks:
      '#none#':
      - "2"
    note: false
    quietmode: 0
    scriptarguments:
      columns:
        simple: technique
      context_path:
        simple: Handled.Techniques
      grid_id:
        simple: handledtechniques
      keys: {}
      overwrite: {}
      sort_by: {}
      unpack_nested_elements: {}
    separatecontext: false
    skipunavailable: false
    task:
      brand: ""
      description: Creates a Grid table from items or key-value pairs.
      id: f4ee501c-677d-40dd-8056-d4da61ee1d3b
      iscommand: false
      name: Set grid field
      script: SetGridField
      type: regular
      version: -1
    taskid: f4ee501c-677d-40dd-8056-d4da61ee1d3b
    timertriggers: []
    type: regular
    view: |-
      {
        "position": {
          "x": 50,
          "y": 640
        }
      }
version: -1
view: |-
  {
    "linkLabelsPosition": {},
    "paper": {
      "dimensions": {
        "height": 1110,
        "width": 810,
        "x": 50,
        "y": -220
      }
    }
  }
tests:
- No tests (auto formatted)
fromversion: 6.5.0