sample
A copy of a suspicious or malicious file kept for analysis.
In more detail
Store samples in password-protected archives (the password infected is a common convention) so nobody runs them by accident and mail scanners do not delete them. Search public scanning services by hash rather than uploading, since uploads are shared with others and may tip off the attacker.
Related terms
- malware triage — A quick first examination of a suspicious file, using hashes, strings, headers and imports, to judge what it is and what to do next.
- hash — A short fixed-length fingerprint calculated from data, which changes completely if even one byte of the data changes.
- sandbox — A locked-down environment in which a program runs with very few permissions, so that damage from a bug or attack stays contained.
Taught in
- SOC Operating Models, Tiers & Key Performance Metrics — Security Operations & Threat Hunting (SOC)
- Log Parsing, Schema Normalization (OCSF/ECS) & Extraction — Security Operations & Threat Hunting (SOC)
- Detection as Code: Authoring & Testing Sigma Rules — Security Operations & Threat Hunting (SOC)
- Windows Event Logs, Sysmon & Linux Auditd Telemetry — Security Operations & Threat Hunting (SOC)
- YARA Rule Authoring & File Signature Matching — Security Operations & Threat Hunting (SOC)
- Memory Forensics: Process Trees & Injection — Security Operations & Threat Hunting (SOC)
- Malware Triage: Hashes, Strings & Sandboxing — Security Operations & Threat Hunting (SOC)