Skip to content

Latest commit

 

History

History
48 lines (31 loc) · 2.47 KB

Use-Case-Structure.md

File metadata and controls

48 lines (31 loc) · 2.47 KB

(AKA Playbook)

Executive Summary

[Provide non-technical, high-level information, references, and background.]

Name

[Provide a succinct statement that describes what the Use Case addresses (e.g. Antivirus Detection Alert).]

Problem Statement

[Describe the problem, beginning with any necessary background information.]

Objectives

[Define the goals of the Use Case.]

Compliance

[List the Compliance Framework and individual checks/requirements the Use Case relates to in bulleted format.]

MITRE ATT&CK Framework

[List the MITRE ATT&CK Framework Tactics/Techniques the Use Case relates to in bulleted format.]

Assumptions and Limitations

[Describe any assumptions/limitations regarding law, licensing, policies, or technicalities.]

Analysis

[Provide insights on the actions of and tools for those who are expected to monitor and respond.]

Detection Validation

[Describe expected paths that would lead to this Use Case being identified as the proper course of action/response. Include steps to validate true or false positive and whether Containment, Remediation, and Recovery steps are necessary. List specific monitors, dashboards, reports, automated emails, alerts, etc. In cases where a user may provide the initial notification, provide language to look for. e.g.:

  • A call from a user referencing a Symantec Antivirus popup or window.
  • An email from a System Administrator citing an antivirus alert in Symantec Manager.]

Recommended Response Action(s)

Identification

[Provide recommended actions that determine investigation scope, collect, and preserve data, and perform technical analysis, when, where, and who to escalate to.]

Containment

[Provide recommended actions that limit the impact and spread of the situation.]

Eradication & Recovery

[Provide steps to determine whether a system can be restored after cleanup versus requiring reimaging, disk replacement, or entire system replacement. Provide recommend actions to eradicate all artifacts revert all changes to the system when viable, including how to validate those actions taken.]

References and Resources

[Provide any useful resources or references that can help understand the vulnerability, attack, detection, affected software, protocols, etc. Usually in the form of URLs with page names (in case the Website owner restructure their links, like Microsoft does often.]

https://www.cisa.gov/sites/default/files/2024-08/Federal_Government_Cybersecurity_Incident_and_Vulnerability_Response_Playbooks_508C.pdf