Attack Ent T1003 Os Credential Dumping

MITRE ATT&CK T1003: OS Credential Dumping

When to use this skill

Use this skill when the task involves T1003, OS Credential Dumping, enterprise 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: enterprise
• ATT&CK ID: T1003
• Technique name: OS Credential Dumping
• Type: technique
• ATT&CK URL: https://attack.mitre.org/techniques/T1003
• Tactics: credential-access
• Platforms: Linux, macOS, Windows
• Required permissions: Not specified
• Effective permissions: Not specified
• Defenses bypassed: Not specified

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. Credentials can be obtained from OS caches, memory, or structures.(Citation: Brining MimiKatz to Unix) Credentials can then be used to perform Lateral Movement and access restricted information.

Several of the tools mentioned in associated sub-techniques may be used by both adversaries and professional security testers. Additional custom tools likely exist as well.

Agent workflow

1. 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.
2. 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.
3. 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.
4. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
5. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
6. 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

• Active Directory Configuration
• Behavior Prevention on Endpoint
• Credential Access Protection
• Encrypt Sensitive Information
• Operating System Configuration
• Password Policies
• Privileged Account Management
• Privileged Process Integrity
• User Training

Known threat context

Use these examples only as contextual leads, not as proof that an observed event is this technique:

• APT28 (intrusion-set)
• APT32 (intrusion-set)
• APT39 (intrusion-set)
• Axiom (intrusion-set)
• BlackByte (intrusion-set)
• Carbanak (malware)
• Ember Bear (intrusion-set)
• HOMEFRY (malware)
• Leviathan (intrusion-set)
• MgBot (malware)
• Mustang Panda (intrusion-set)
• OnionDuke (malware)
• PinchDuke (malware)
• Poseidon Group (intrusion-set)
• Revenge RAT (malware)
• Sowbug (intrusion-set)
• Storm-0501 (intrusion-set)
• Suckfly (intrusion-set)
• Tonto Team (intrusion-set)
• Trojan.Karagany (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.

ATT&CK contributors

• Vincent Le Toux
• Ed Williams, Trustwave, SpiderLabs
• Tim (Wadhwa-)Brown
• Yves Yonan