Detecting T1003 Credential Dumping With Edr
Overview
Cybersecurity skill for detecting t1003 credential dumping with edr. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"detecting t1003 credential dumping with edr"
"Detect OS credential dumping techniques targeting LSASS memory, SAM database, NT"
When hunting for credential theft activity in the environment
After compromise indicators suggest attacker has elevated privileges
When EDR alerts fire for LSASS access or suspicious process memory reads
During incident response to determine scope of credential compromise
When auditing LSASS protection controls (Credential Guard, RunAsPPL)
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- EDR agent deployed with LSASS access monitoring (CrowdStrike, Defender for Endpoint, SentinelOne)
- Sysmon Event ID 10 (ProcessAccess) with LSASS-specific filters
- Windows Security Event ID 4656/4663 (Object Access Auditing)
- LSASS SACL auditing enabled (Windows 10+)
- Registry auditing for SAM hive access
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Define Detection Scope — Identify the specific t1003 credential dumping techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.
- Collect Baseline Data — Gather historical logs and establish normal behavior patterns for t1003 credential dumping.
- Build Detection Queries — Write edr queries targeting t1003 credential dumping indicators. Use platform-specific query language for optimal performance.
- Execute Hunts — Run queries against the collected data, starting with broad filters and narrowing down.
- Triage Results — Investigate alerts, filter false positives, and validate findings against known-good behavior.
- Document Findings — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.
Tools
- edr — Primary tool for this skill
- SIEM Platform — Central log aggregation and query execution
- Sigma Rules — Vendor-agnostic detection rule format
- MITRE ATT&CK Navigator — Technique mapping and coverage analysis
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: detecting-t1003-credential-dumping-with-edr3description: Use when detect OS credential dumping techniques targeting LSASS memory, SAM database, NTDS.dit, and cached credentials using EDR telemetry, Sysmon process access monitoring, and Windows security event correlation. Use when detecting os credential dumping techniques targeting lsass memory, sam database,.4license: Apache-2.05---67# Detecting T1003 Credential Dumping With Edr89## Overview1011Cybersecurity skill for detecting t1003 credential dumping with edr. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "detecting t1003 credential dumping with edr"16- "Detect OS credential dumping techniques targeting LSASS memory, SAM database, NT"171819- When hunting for credential theft activity in the environment20- After compromise indicators suggest attacker has elevated privileges21- When EDR alerts fire for LSASS access or suspicious process memory reads22- During incident response to determine scope of credential compromise23- When auditing LSASS protection controls (Credential Guard, RunAsPPL)242526## When NOT to Use2728- When you lack proper authorization for testing29- For production systems without change management30- When the task requires legal or compliance expertise beyond technical scope313233## Prerequisites3435- EDR agent deployed with LSASS access monitoring (CrowdStrike, Defender for Endpoint, SentinelOne)36- Sysmon Event ID 10 (ProcessAccess) with LSASS-specific filters37- Windows Security Event ID 4656/4663 (Object Access Auditing)38- LSASS SACL auditing enabled (Windows 10+)39- Registry auditing for SAM hive access4041## Workflow4243```python44# Example: IOC detection45import re4647IOC_PATTERNS = {48 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",49 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",50 "hash_md5": r"\b[a-f0-9]{32}\b",51 "hash_sha256": r"\b[a-f0-9]{64}\b",52}5354def extract_iocs(text: str) -> dict:55 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}56```57581. **Define Detection Scope** — Identify the specific t1003 credential dumping techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.592. **Collect Baseline Data** — Gather historical logs and establish normal behavior patterns for t1003 credential dumping.603. **Build Detection Queries** — Write edr queries targeting t1003 credential dumping indicators. Use platform-specific query language for optimal performance.614. **Execute Hunts** — Run queries against the collected data, starting with broad filters and narrowing down.625. **Triage Results** — Investigate alerts, filter false positives, and validate findings against known-good behavior.636. **Document Findings** — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.6465## Tools6667- **edr** — Primary tool for this skill68- **SIEM Platform** — Central log aggregation and query execution69- **Sigma Rules** — Vendor-agnostic detection rule format70- **MITRE ATT&CK Navigator** — Technique mapping and coverage analysis717273## Process74751. **Reconnaissance** — Gather target information, identify attack surface, enumerate services761. **Analysis/Exploitation** — Execute the technique, analyze results, document findings771. **Reporting** — Document IOCs, write findings, provide remediation recommendations7879## Verification8081- [ ] All t1003 credential dumping procedures executed completely and documented82- [ ] Findings validated against multiple data sources83- [ ] False positives identified and filtered84- [ ] Results documented with evidence and timestamps85- [ ] Recommendations provided with risk-based prioritization8687## Anti-Rationalization Table8889| Rationalization | Reality |90|---|---|91| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |92| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |93| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |