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 2 · Lesson 3 of 5
Persistence and anti-forensics on hosts
1 min read
Attackers want two things after they land: to survive a reboot and to erase the trail. A new service with automatic start is one of the most durable persistence methods, because the operating system relaunches it at every boot.
Windows records a service installation as System event 7045. The exam marks it as malicious through details, not the event itself: the binary sits in a writable data folder instead of a program folder, the friendly name matches no licensed product, the change happened out of hours under a privileged account, and no change request explains it.
Anti-forensics is read from the order of events. A typical sequence is auditpol switching off process creation auditing, then Security event 1102 showing the log was cleared, then the event log service stopping. Each step targets the record of the intrusion, not disk space.
Normal retention simply overwrites the oldest entries and does not generate a clear event. If a forwarding agent already shipped earlier events to a collector, the attempt fails, because those copies are out of the attacker's reach.
Check yourself
1. At 03:12 a file server records service installation event 7045 for a service named WinDefragSvc with image path C:\ProgramData\wdfg.exe and automatic start, created under a domain administrator account. No change request references the host, and no defragmentation product is licensed in the environment. What does this indicate?
2. A server logs, in this order: process creation for auditpol.exe /set /subcategory:"Process Creation" /success:disable at 02:39, event 1102 at 02:41, and a stop of the event log service at 02:42. The forwarding agent had already shipped the earlier events to the collector. What does this sequence indicate?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, AWS CloudTrail User Guide: Logging data events
CompTIA CySA+ cheat sheet: every key fact on one page →