ATT&CK coverage › Technique
Unsecured Credentials: Credentials In Files T1552.001
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords.
Events covered
5 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 14 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (8 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (75 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.
Common exclusions (7 distinct)
Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 10 rules
- Automated Collection Command Prompt
- Extracting Information with PowerShell
- HackTool - Typical HiveNightmare SAM File Export
- HackTool - WinPwn Execution
- HackTool - WinPwn Execution - ScriptBlock
- Insensitive Subfolder Search Via Findstr.EXE
- Potential PowerShell Console History Access Attempt via History File
- Potentially Suspicious JWT Token Search Via CLI
- PUA - TruffleHog Execution
- Remote File Download Via Findstr.EXE
Splunk 3 rules
- Shai-Hulud 2 Exfiltration Artifact Files
- Windows Unusual FileZilla XML Config Access
- Windows Unusual Intelliform Storage Registry Access