القائمة
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill t1552-004-private-keysيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | T1552.004_private-keys |
| description | Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials. |
| category | authentication |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","enterprise","t1552.004","credential-access","linux","macos","network-devices","windows","sub-technique"] |
| technique_id | T1552.004 |
| tactic | credential-access |
| all_tactics | ["credential-access"] |
| platforms | ["Linux","macOS","Network Devices","Windows"] |
| mitre_url | https://attack.mitre.org/techniques/T1552/004 |
| tech_stack | ["linux","macos","network devices","windows"] |
| cwe_ids | ["CWE-522"] |
| chains_with | ["T1552","T1552.001","T1552.002","T1552.003","T1552.005","T1552.006","T1552.007","T1552.008"] |
| prerequisites | ["T1552"] |
| severity_boost | {"T1552":"Chain with T1552 for deeper attack path","T1552.001":"Chain with T1552.001 for deeper attack path","T1552.002":"Chain with T1552.002 for deeper attack path"} |
Sub-technique of: T1552
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. 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.
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. An adversary with access to the device may be able to export the keys in order to impersonate the device.
On network devices, private keys may be exported via Network Device CLI commands such as crypto pki export.
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.
Platforms: Linux, macOS, Network Devices, Windows
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
Find private keys on the Windows file system. File extensions include: .key, .pgp, .gpg, .ppk., .p12, .pem, pfx, .cer, .p7b, .asc
Supported Platforms: windows Elevation Required: Yes
dir c:\ /b /s .key | findstr /e .key
Discover private SSH keys on a FreeBSD, macOS or Linux system.
Supported Platforms: linux, macos
find #{search_path} -name id_rsa 2>/dev/null >> #{output_file}
exit 0
Copy private SSH keys on a Linux system to a staging folder using the cp command.
Supported Platforms: linux
mkdir #{output_folder}
find #{search_path} -name id_rsa 2>/dev/null -exec cp --parents {} #{output_folder} \;
exit 0
Copy private SSH keys on a FreeBSD system to a staging folder using the cp command.
Supported Platforms: linux
mkdir #{output_folder}
find #{search_path} -name id_rsa 2>/dev/null -exec gcp --parents {} #{output_folder} \;
Dependencies:
Copy private SSH keys on a Linux or macOS system to a staging folder using the rsync command.
Supported Platforms: macos, linux
mkdir #{output_folder}
find #{search_path} -name id_rsa 2>/dev/null -exec rsync -R {} #{output_folder} \;
exit 0
If Atomic Red Team tests are not applicable, manually verify the technique by:
Identify Attack Surface: Determine if the target environment is susceptible to Private Keys by examining the target platforms (Linux, macOS, Network Devices).
Assess Existing Defenses: Review whether mitigations for T1552.004 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Use strong passphrases for private keys to make cracking difficult.
Ensure permissions are properly set on folders containing sensitive private keys to prevent unintended access. Additionally, on Cisco devices, set the nonexportable flag during RSA key pair generation.
Ensure only authorized keys are allowed access to critical resources and audit access lists regularly.
When possible, store keys on separate cryptographic hardware instead of on the local system. For example, on Windows systems use a TPM to secure keys and other sensitive credential material.
| Finding | Severity | Impact |
|---|---|---|
| Private Keys technique applicable | High | Credential Access |
| CWE ID | Title |
|---|---|
| CWE-522 | Insufficiently Protected Credentials |