MITRE ATT&CK T0801: Monitor Process State
When to use this skill
Use this skill when the task involves T0801, Monitor Process State, ics ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: ics
- ATT&CK ID: T0801
- Technique name: Monitor Process State
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T0801
- Tactics: collection
- Platforms: None
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may gather information about the physical process state. This information may be used to gain more information about the process itself or used as a trigger for malicious actions. The sources of process state information may vary such as, OPC tags, historian data, specific PLC block information, or network traffic.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.references/known-threat-context.md: ATT&CK relationship context with attribution cautions.templates/detection-brief.md: detection engineering brief template.templates/hunt-plan.md: threat hunt plan template.templates/incident-response-note.md: incident response note template.templates/coverage-assessment.md: ATT&CK coverage assessment template.scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Mitigation Limited or Not Effective
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- FrostyGoop (malware)
- Industroyer (malware)
- Industroyer2 (malware)
- Stuxnet (malware)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
1---2name: attack-ics-t0801-monitor-process-state3description: Analyze MITRE ATT&CK T0801 Monitor Process State in the ics matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T0801, Monitor Process State, or ics ATT&CK. Adversaries may gather information about the physical process state.4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See h5---67# MITRE ATT&CK T0801: Monitor Process State89## When to use this skill1011Use this skill when the task involves T0801, Monitor Process State, ics ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.1213## Technique context1415- ATT&CK domain: ics16- ATT&CK ID: T080117- Technique name: Monitor Process State18- Type: technique19- ATT&CK URL: https://attack.mitre.org/techniques/T080120- Tactics: collection21- Platforms: None22- Required permissions: Not specified23- Effective permissions: Not specified24- Defenses bypassed: Not specified2526## ATT&CK description2728Adversaries may gather information about the physical process state. This information may be used to gain more information about the process itself or used as a trigger for malicious actions. The sources of process state information may vary such as, OPC tags, historian data, specific PLC block information, or network traffic.2930## Agent workflow31321. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.332. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.343. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.354. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.365. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.376. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.3839## Bundled resources4041- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.42- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.43- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.44- `templates/detection-brief.md`: detection engineering brief template.45- `templates/hunt-plan.md`: threat hunt plan template.46- `templates/incident-response-note.md`: incident response note template.47- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.48- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.49- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5051To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.5253## Detection guidance5455No ATT&CK detection guidance was present in the source STIX object.5657## Useful telemetry and data sources5859- Not specified in the STIX object.6061## Mitigations to consider6263- Mitigation Limited or Not Effective6465## Known threat context6667Use these examples only as contextual leads, not as proof that an observed event is this technique:6869- FrostyGoop (malware)70- Industroyer (malware)71- Industroyer2 (malware)72- Stuxnet (malware)7374## Recommended output pattern7576When responding with this skill, structure the answer as:7778- Assessment: whether the evidence supports this ATT&CK mapping and why.79- Evidence: specific indicators, logs, behaviors, and assumptions.80- Detection: telemetry sources, analytic logic, and tuning considerations.81- Response: containment, eradication, recovery, and validation actions.82- Coverage gaps: missing logs, sensors, controls, or environmental details.83- References: include the ATT&CK URL and any user-provided evidence references.
santosomar