Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 3 · Lesson 2 of 5
Endpoint telemetry, file reputation and sandboxes
1 min read
Questions about what happened on a host need host data. Process ancestry and command lines exist only in endpoint detection and response telemetry, which records each process with its parent and arguments. No SIEM rule built on firewall, proxy and authentication logs can rebuild a parent-child chain, because those sources never knew which process made a connection.
- Hash reputation answers one question: has anyone seen this exact file before? Attackers rebuild payloads per target, so not found is normal for new malware and is never a clean verdict.
- Static inspection cannot see behavior a macro builds at runtime, so detonate the file in an isolated, instrumented sandbox.
- A quiet sandbox run is not proof of safety. Strings naming virtualization drivers, checks for user documents and long sleep calls mean the sample is evading, so run longer in a realistic environment.
- An encoded PowerShell argument is obfuscation, not encryption. Decode the base64 offline to read the script without running anything.
Example: a binary dropped 20 minutes ago by a process the agent flagged returns not found from a reputation service. The right sequence is to keep the host under investigation, review the lineage that wrote the file, then analyze it statically and in a sandbox.
Submitting the signed interpreter that ran a script to a reputation service tells you nothing, because the interpreter itself is legitimate.
Check yourself
1. An analyst submits the SHA-256 digest of a suspicious executable to a file-reputation service, which answers 'not found'. The binary was written to disk an hour earlier by a process the endpoint agent had flagged as unusual. How should the 'not found' result be read?
2. An endpoint agent records this command line on a workstation: powershell.exe -nop -w hidden -enc SQBFAFgAIAAoAE4AZQB3AC0ATwBiAGoA... , and the parent process is a mail client. Which step establishes the intent of this execution fastest?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, MITRE ATT&CK knowledge base of adversary tactics and techniques
CompTIA CySA+ cheat sheet: every key fact on one page →