Investigating Ransomware Attack Artifacts
Overview
Cybersecurity skill for investigating ransomware attack artifacts. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"investigating ransomware attack artifacts"
"Identify, collect, and analyze ransomware attack artifacts to determine the vari"
Immediately after discovering ransomware encryption on systems
When performing forensic analysis to understand the full scope of a ransomware incident
For identifying the ransomware variant and determining if decryption is possible
When tracing the attack chain from initial access to encryption
For documenting evidence to support law enforcement and insurance claims
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
- Forensic images of affected systems (preserve before remediation)
- Memory dumps captured before system shutdown (if available)
- Ransom notes and encrypted file samples
- Network traffic captures from the attack period
- Windows Event Logs, Prefetch files, and registry hives
- Access to ransomware identification tools (ID Ransomware, No More Ransom)
- Isolated sandbox environment for malware analysis
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 Objectives — Clarify the goals and scope for ransomware attack artifacts.
- Gather Resources — Collect tools, data, and access needed for ransomware attack artifacts.
- Execute Process — Carry out ransomware attack artifacts operations methodically.
- Verify Quality — Check results against acceptance criteria.
- Document Outcomes — Record findings, decisions, and next steps.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
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: investigating-ransomware-attack-artifacts3description: Use when identify, collect, and analyze ransomware attack artifacts to determine the variant, initial access vector, encryption scope, and recovery options. Use when working with investigating ransomware attack artifacts.4license: Apache-2.05---67# Investigating Ransomware Attack Artifacts89## Overview1011Cybersecurity skill for investigating ransomware attack artifacts. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "investigating ransomware attack artifacts"16- "Identify, collect, and analyze ransomware attack artifacts to determine the vari"1718- Immediately after discovering ransomware encryption on systems19- When performing forensic analysis to understand the full scope of a ransomware incident20- For identifying the ransomware variant and determining if decryption is possible21- When tracing the attack chain from initial access to encryption22- For documenting evidence to support law enforcement and insurance claims232425## When NOT to Use2627- When you lack proper authorization for testing28- For production systems without change management29- When the task requires legal or compliance expertise beyond technical scope303132## Prerequisites33- Forensic images of affected systems (preserve before remediation)34- Memory dumps captured before system shutdown (if available)35- Ransom notes and encrypted file samples36- Network traffic captures from the attack period37- Windows Event Logs, Prefetch files, and registry hives38- Access to ransomware identification tools (ID Ransomware, No More Ransom)39- Isolated sandbox environment for malware analysis4041## 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 Objectives** — Clarify the goals and scope for ransomware attack artifacts.592. **Gather Resources** — Collect tools, data, and access needed for ransomware attack artifacts.603. **Execute Process** — Carry out ransomware attack artifacts operations methodically.614. **Verify Quality** — Check results against acceptance criteria.625. **Document Outcomes** — Record findings, decisions, and next steps.6364## Tools6566- **Analysis Platform** — Data processing and visualization67- **Collaboration Tools** — Team coordination and knowledge sharing686970## Process71721. **Reconnaissance** — Gather target information, identify attack surface, enumerate services731. **Analysis/Exploitation** — Execute the technique, analyze results, document findings741. **Reporting** — Document IOCs, write findings, provide remediation recommendations7576## Verification7778- [ ] All ransomware attack artifacts procedures executed completely and documented79- [ ] Findings validated against multiple data sources80- [ ] False positives identified and filtered81- [ ] Results documented with evidence and timestamps82- [ ] Recommendations provided with risk-based prioritization8384## Anti-Rationalization Table8586| Rationalization | Reality |87|---|---|88| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |89| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |90| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |