MITRE ATT&CK T1552.004: Private Keys
When to use this skill
Use this skill when the task involves T1552.004, Private Keys, 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 sub-technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1552.004
- Technique name: Private Keys
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1552/004
- Tactics: credential-access
- Platforms: Linux, macOS, Network Devices, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials. Private cryptographic keys and certificates are used for authentication, encryption/decryption, and digital signatures.(Citation: Wikipedia Public Key Crypto) Common key and certificate file extensions include: .key, .pgp, .gpg, .ppk., .p12, .pem, .pfx, .cer, .p7b, .asc.
Adversaries may also look in common key directories, such as ~/.ssh for SSH keys on * nix-based systems or C:\Users\(username)\.ssh\ on Windows. Adversary tools may also search compromised systems for file extensions relating to cryptographic keys and certificates.(Citation: Kaspersky Careto)(Citation: Palo Alto Prince of Persia)
When a device is registered to Entra ID, a device key and a transport key are generated and used to verify the device’s identity.(Citation: Microsoft Primary Refresh Token) An adversary with access to the device may be able to export the keys in order to impersonate the device.(Citation: AADInternals Azure AD Device Identities)
On network devices, private keys may be exported via Network Device CLI commands such as crypto pki export.(Citation: cisco_deploy_rsa_keys)
Some private keys require a password or passphrase for operation, so an adversary may also use Input Capture for keylogging or attempt to Brute Force the passphrase off-line. These private keys can be used to authenticate to Remote Services like SSH or for use in decrypting other collected files such as email.
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
- Audit
- Encrypt Sensitive Information
- Password Policies
- Restrict File and Directory Permissions
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- AADInternals (tool)
- Ebury (malware)
- Empire (tool)
- FoggyWeb (malware)
- Hildegard (malware)
- Kimsuky (intrusion-set)
- Kinsing (malware)
- Machete (malware)
- Mafalda (malware)
- Mimikatz (tool)
- Operation Wocao (campaign)
- Rocke (intrusion-set)
- Scattered Spider (intrusion-set)
- SolarWinds Compromise (campaign)
- Storm-0501 (intrusion-set)
- TeamTNT (intrusion-set)
- Troll Stealer (malware)
- Volt Typhoon (intrusion-set)
- jRAT (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
- Itzik Kotler, SafeBreach
- Austin Clark, @c2defense
1---2name: attack-ent-t1552-004-private-keys3description: "Analyze MITRE ATT&CK T1552.004 Private Keys 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.004, Private Keys, or enterprise ATT&CK. Adversaries may search for private key certificate files on compromised systems for 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-004-private-keys7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1552.00410 attack_stix_id: attack-pattern--60b508a1-6a5e-46b1-821a-9f7b78752abf11 attack_version: "1.3"12 attack_modified: "2025-10-24T17:48:50.819Z"13---1415# MITRE ATT&CK T1552.004: Private Keys1617## When to use this skill1819Use this skill when the task involves T1552.004, Private Keys, 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 sub-technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T1552.00425- Technique name: Private Keys26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1552/00428- Tactics: credential-access29- Platforms: Linux, macOS, Network Devices, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials. Private cryptographic keys and certificates are used for authentication, encryption/decryption, and digital signatures.(Citation: Wikipedia Public Key Crypto) Common key and certificate file extensions include: .key, .pgp, .gpg, .ppk., .p12, .pem, .pfx, .cer, .p7b, .asc. 3738Adversaries may also look in common key directories, such as <code>~/.ssh</code> for SSH keys on * nix-based systems or <code>C:\Users\(username)\.ssh\</code> on Windows. Adversary tools may also search compromised systems for file extensions relating to cryptographic keys and certificates.(Citation: Kaspersky Careto)(Citation: Palo Alto Prince of Persia)3940When a device is registered to Entra ID, a device key and a transport key are generated and used to verify the device’s identity.(Citation: Microsoft Primary Refresh Token) An adversary with access to the device may be able to export the keys in order to impersonate the device.(Citation: AADInternals Azure AD Device Identities)4142On network devices, private keys may be exported via [Network Device CLI](https://attack.mitre.org/techniques/T1059/008) commands such as `crypto pki export`.(Citation: cisco_deploy_rsa_keys) 4344Some private keys require a password or passphrase for operation, so an adversary may also use [Input Capture](https://attack.mitre.org/techniques/T1056) for keylogging or attempt to [Brute Force](https://attack.mitre.org/techniques/T1110) the passphrase off-line. These private keys can be used to authenticate to [Remote Services](https://attack.mitre.org/techniques/T1021) like SSH or for use in decrypting other collected files such as email.4546## Agent workflow47481. 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.492. 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.503. 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.514. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.525. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.536. 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.5455## Bundled resources5657- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.58- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.59- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.60- `templates/detection-brief.md`: detection engineering brief template.61- `templates/hunt-plan.md`: threat hunt plan template.62- `templates/incident-response-note.md`: incident response note template.63- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.64- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.65- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6667To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6869## Detection guidance7071No ATT&CK detection guidance was present in the source STIX object.7273## Useful telemetry and data sources7475- Not specified in the STIX object.7677## Mitigations to consider7879- Audit80- Encrypt Sensitive Information81- Password Policies82- Restrict File and Directory Permissions8384## Known threat context8586Use these examples only as contextual leads, not as proof that an observed event is this technique:8788- AADInternals (tool)89- Ebury (malware)90- Empire (tool)91- FoggyWeb (malware)92- Hildegard (malware)93- Kimsuky (intrusion-set)94- Kinsing (malware)95- Machete (malware)96- Mafalda (malware)97- Mimikatz (tool)98- Operation Wocao (campaign)99- Rocke (intrusion-set)100- Scattered Spider (intrusion-set)101- SolarWinds Compromise (campaign)102- Storm-0501 (intrusion-set)103- TeamTNT (intrusion-set)104- Troll Stealer (malware)105- Volt Typhoon (intrusion-set)106- jRAT (malware)107108## Recommended output pattern109110When responding with this skill, structure the answer as:111112- Assessment: whether the evidence supports this ATT&CK mapping and why.113- Evidence: specific indicators, logs, behaviors, and assumptions.114- Detection: telemetry sources, analytic logic, and tuning considerations.115- Response: containment, eradication, recovery, and validation actions.116- Coverage gaps: missing logs, sensors, controls, or environmental details.117- References: include the ATT&CK URL and any user-provided evidence references.118119## ATT&CK contributors120121- Itzik Kotler, SafeBreach122- Austin Clark, @c2defense