Covering tracks is the activity of attempting to hide evidence of compromise, such as deleting logs, disabling audit trails, or planting backdoors. In a pentest, this is used to assess whether defenders can detect stealthy adversary behaviour and whether monitoring, logging, and response controls are resilient.
What Covering Tracks Means in an Attack or Test
Covering tracks is the post-compromise behaviour that aims to reduce visibility after unauthorized access, commonly by removing logs, tampering with audit data, or planting persistence so defenders investigate the wrong trail. It matters because detection and response depend on trustworthy evidence, not just on blocking initial intrusion.
In practice, this behaviour is often associated with stealth, persistence, and anti-forensic intent. When an attacker can alter telemetry or disable recording, the organisation may lose the very signals needed to understand scope, timing, and blast radius.
How Covering Tracks Weakens Detection and Forensics
The security problem is not only that evidence disappears, but that the remaining evidence may become misleading. A changed audit trail can conceal which account acted, which host was touched, and whether the compromise spread laterally. That makes incident reconstruction slower and increases the chance of incomplete containment.
Covering tracks is especially dangerous where logging is fragmented across endpoints, cloud services, and identity platforms. If one control plane is weakened while another still records events, defenders may see inconsistent timelines that are harder to correlate and trust.
Strong logging, time synchronisation, central collection, and protected retention reduce the chance that a single compromised system can erase the full story. These controls are part of why detective telemetry is treated as a core security asset rather than a passive record.
Common Techniques Used to Hide Evidence
Typical techniques include deleting or truncating logs, disabling audit policies, altering timestamps, clearing command history, and abusing privileged access to suppress alerts. Attackers may also create new local accounts, scheduled tasks, or backdoors so access can continue after the first intrusion is discovered.
Some of the most effective concealment methods rely on trust in administrative tooling. If an intruder can use legitimate access to change configuration or silence monitoring, the activity may blend into normal operations and evade basic perimeter controls.
In mature environments, defenders look for inconsistency rather than a single obvious indicator: missing records, unexpected log gaps, audit policy changes, or security tools that stop sending events. Those anomalies often reveal tampering more reliably than a direct signature of the original compromise.
What Defenders Should Preserve and Review After Suspected Covering Tracks
When covering tracks is suspected, the priority is to preserve independent evidence before it is overwritten. That usually means collecting logs from central systems, endpoint telemetry, identity events, and backup or immutable stores while the original host is still being investigated.
Review should focus on what changed in the monitoring environment itself, not only on the suspect application or server. A compromised account, a disabled sensor, or a rewritten log source can all be part of the incident path, and each may need separate containment and recovery steps.
Good investigation practice also includes checking whether persistence was planted to outlast the initial cleanup attempt. A hidden backdoor can be more important than the original payload because it explains why the attacker may return even after the first access route is closed.
Risk and Threat Considerations
Covering tracks raises the risk that a compromise becomes both longer lived and harder to scope. Once evidence is altered or removed, defenders may underestimate what was accessed, which accounts were abused, or whether the attacker left a durable foothold behind.
Failure mechanism: The attacker uses elevated or stolen access to tamper with logs, disable audit settings, or plant persistence, which breaks the defender's ability to reconstruct the intrusion accurately.
Impact: Containment takes longer, forensic confidence drops, and the organisation may miss follow-on activity such as lateral movement, credential abuse, or repeated re-entry.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack surface, NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | TA0005 — Defense Evasion | Covers hiding activity by evading logs and alerts. |
| Recommendation — Map tampering with logs and alerts to defense evasion and hunt for altered telemetry. | ||
| NIST SP 800-53 Rev 5 | AU-2 — Event Logging | Defines the logging basis that covering tracks tries to undermine. |
| AU-6 — Audit Record Review, Analysis, and Reporting | Supports detecting and acting on missing or manipulated audit evidence. | |
| AU-9 — Protection of Audit Information | Directly addresses preventing attackers from altering or deleting logs. | |
| Recommendation — Define and retain the event types needed to preserve trustworthy audit evidence. Review audit records for gaps, anomalies, and signs of tampering. Protect audit information against deletion, modification, and unauthorized suppression. | ||
| CIS Controls v8 | CIS-8 — Audit Log Management | Focuses on centralized, protected logging that resists log wiping. |
| CIS-17 — Incident Response Management | Covers preserving evidence and responding when concealment is suspected. | |
| Recommendation — Centralize and protect logs so attackers cannot easily erase evidence. Use incident response procedures to preserve evidence and investigate log tampering. | ||
| ISO/IEC 27001:2022 | A.8.15 — Logging | Addresses logging controls that preserve evidential integrity. |
| Recommendation — Implement logging controls that preserve reliable evidence for detection and investigation. | ||
Practitioner Guidance
What to watch for: Treat unexpected logging gaps, audit-policy changes, and security tooling failures as potential compromise signals, not just operational noise. A single missing event stream can be enough to justify escalation when the affected system is security-relevant.
Governance implication: Teams should decide in advance which logs are protected, where they are centralised, and who can alter or disable them. Covering tracks is easier when log ownership and retention controls are vague.
Practitioner takeaway: The best defence is evidence that the attacker cannot easily rewrite, because detection and forensics fail when the record of the event is less trustworthy than the event itself.
Related resources from NHI Mgmt Group
- How do organisations know whether PAM is actually covering privileged access?
- How do organisations know whether DORA controls are actually covering AI risk?
- What should organisations do when cloud security tools start covering AI pipelines as well as infrastructure?
- What breaks when risk software tracks apps but not the identities behind them?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org