MITRE ATT&CK T1552: Unsecured Credentials
When to use this skill
Use this skill when the task involves T1552, Unsecured Credentials, 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: T1552
- Technique name: Unsecured Credentials
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1552
- Tactics: credential-access
- Platforms: Windows, SaaS, IaaS, Linux, macOS, Containers, Network Devices, Office Suite, Identity Provider
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may search compromised systems to find and obtain insecurely stored credentials. These credentials can be stored and/or misplaced in many locations on a system, including plaintext files (e.g. Shell History), operating system or application-specific repositories (e.g. Credentials in Registry), or other specialized files/artifacts (e.g. Private Keys).(Citation: Brining MimiKatz to Unix)
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
- Active Directory Configuration
- Audit
- Encrypt Sensitive Information
- Filter Network Traffic
- Limit Access to Resource Over Network
- Operating System Configuration
- Password Policies
- Privileged Account Management
- Restrict File and Directory Permissions
- Update Software
- User Training
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Astaroth (malware)
- DarkGate (malware)
- Leviathan Australian Intrusions (campaign)
- NPPSPY (tool)
- Pacu (tool)
- Volt Typhoon (intrusion-set)
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
1---2name: attack-ent-t1552-unsecured-credentials3description: "Analyze MITRE ATT&CK T1552 Unsecured Credentials in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1552, Unsecured Credentials, or enterprise ATT&CK. Adversaries may search compromised systems to find and obtain insecurely stored credentials."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1552-unsecured-credentials7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T155210 attack_stix_id: attack-pattern--435dfb86-2697-4867-85b5-2fef496c051711 attack_version: "1.5"12 attack_modified: "2025-10-24T17:48:42.785Z"13---1415# MITRE ATT&CK T1552: Unsecured Credentials1617## When to use this skill1819Use this skill when the task involves T1552, Unsecured Credentials, 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.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T155225- Technique name: Unsecured Credentials26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T155228- Tactics: credential-access29- Platforms: Windows, SaaS, IaaS, Linux, macOS, Containers, Network Devices, Office Suite, Identity Provider30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may search compromised systems to find and obtain insecurely stored credentials. These credentials can be stored and/or misplaced in many locations on a system, including plaintext files (e.g. [Shell History](https://attack.mitre.org/techniques/T1552/003)), operating system or application-specific repositories (e.g. [Credentials in Registry](https://attack.mitre.org/techniques/T1552/002)), or other specialized files/artifacts (e.g. [Private Keys](https://attack.mitre.org/techniques/T1552/004)).(Citation: Brining MimiKatz to Unix)3738## Agent workflow39401. 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.412. 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.423. 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.434. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.445. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.456. 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.4647## Bundled resources4849- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.50- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.51- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.52- `templates/detection-brief.md`: detection engineering brief template.53- `templates/hunt-plan.md`: threat hunt plan template.54- `templates/incident-response-note.md`: incident response note template.55- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.56- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.57- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5859To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6061## Detection guidance6263No ATT&CK detection guidance was present in the source STIX object.6465## Useful telemetry and data sources6667- Not specified in the STIX object.6869## Mitigations to consider7071- Active Directory Configuration72- Audit73- Encrypt Sensitive Information74- Filter Network Traffic75- Limit Access to Resource Over Network76- Operating System Configuration77- Password Policies78- Privileged Account Management79- Restrict File and Directory Permissions80- Update Software81- User Training8283## Known threat context8485Use these examples only as contextual leads, not as proof that an observed event is this technique:8687- Astaroth (malware)88- DarkGate (malware)89- Leviathan Australian Intrusions (campaign)90- NPPSPY (tool)91- Pacu (tool)92- Volt Typhoon (intrusion-set)9394## Recommended output pattern9596When responding with this skill, structure the answer as:9798- Assessment: whether the evidence supports this ATT&CK mapping and why.99- Evidence: specific indicators, logs, behaviors, and assumptions.100- Detection: telemetry sources, analytic logic, and tuning considerations.101- Response: containment, eradication, recovery, and validation actions.102- Coverage gaps: missing logs, sensors, controls, or environmental details.103- References: include the ATT&CK URL and any user-provided evidence references.104105## ATT&CK contributors106107- Austin Clark, @c2defense