VAKA-2044 · 6 Oct 2026 · 1 alert
Audit log cleared on the ERP server
- Severity
- High
- Verdict
- False positive (approved maintenance)
- Confidence
- 88%
- Status
- Closed with SOC analyst approval
The security log on QD-SRV-ERP01 was cleared. This happened inside the approved maintenance window in the change calendar, with the registered implementer’s admin account, and after the logs had been archived. The alert was opened at high severity because at first sight it looks like covering tracks; the company context showed it to be a false positive.
Flow
- Continues on the same asset
- Moves to another asset
- Connection outside the company
An arrow means 'followed by', not 'caused'.
- Critical
- High
- Medium
- Low
- 22:47, B1: Security log cleared (Event ID 1102). High severity, Defense Impairment. Involved: Ece Demir, QD-SRV-ERP01.
B16 Oct 2026 22:47Windows Security
Security log cleared (Event ID 1102)
The account QD\ece.demir.adm cleared the security log on QD-SRV-ERP01.
Assets and people
- ServerQD-SRV-ERP01ERP server
- PersonEce DemirSenior Systems Administrator · IT
Evidence records
[E1]Windows Security · ERP01
22:47:12 · Event 1102 · the security audit log was cleared · Subject QD\ece.demir.adm
Why it matters: The triggering record.
[E2]Windows System · ERP01
22:31:05 · Event 1074 · planned restart · QD\ece.demir.adm
Why it matters: The same account performed the in-scope maintenance restart 16 minutes earlier.
[E3]QD-SRV-LOG02
22:46:58 · Security-ERP01-20261006.evtx archived · SHA-256 recorded
Why it matters: The logs were archived before they were cleared.
MITRE ATT&CK
- T1685.005Disable or Modify Tools: Clear Windows Event Logs
Findings and evidence
-
Finding 1
The log was cleared inside the DEG-2026-0412 maintenance window (22:00–23:30) and matches the “archiving and clearing of the security logs” step in its scope.
Evidence [E1]
-
Finding 3
The logs were archived to LOG02 14 seconds before they were cleared; no audit trail was lost.
Evidence [E3]
-
Finding 4
The alert was opened at high severity because attackers also clear logs to cover their tracks, and ERP01 has high criticality. The context warrants lowering that severity.
Evidence [E1]
Evidence records
| Evidence | Source | Record | Why it matters |
|---|---|---|---|
| E1B1 | Windows Security · ERP01 | 22:47:12 · Event 1102 · the security audit log was cleared · Subject QD\ece.demir.adm | The triggering record. |
| E2B1 | Windows System · ERP01 | 22:31:05 · Event 1074 · planned restart · QD\ece.demir.adm | The same account performed the in-scope maintenance restart 16 minutes earlier. |
| E3B1 | QD-SRV-LOG02 | 22:46:58 · Security-ERP01-20261006.evtx archived · SHA-256 recorded | The logs were archived before they were cleared. |
Context
People
-
Ece Demir
Senior Systems Administrator · IT · Admin account
Usual pattern Weekdays 09:00–18:00. Uses a separate admin account (QD\ece.demir.adm) for administrative work; also works outside office hours during planned maintenance.
Assets
-
QD-SRV-ERP01
Server · High criticality · 10.20.1.20
ERP server
Owner: Ece Demir
Document excerpts behind the verdict
q-node retrieved these excerpts from the company’s own documents; each one supports a finding.
-
Change recordChange Calendar, October 2026
Record DEG-2026-0412. Date and time: 6 Oct 2026, 22:00–23:30. Scope: QD-SRV-ERP01 update, and archiving and clearing of the security logs. Implemented by: Ece Demir. Approved by: Burak Şahin.
Supports: Findings 1 and 2: the window, scope and implementer match the event exactly
-
InventoryAsset Inventory
QD-SRV-ERP01: ERP server. Owner: Ece Demir. Criticality: high. IP: 10.20.1.20.
Supports: Finding 4: the initial severity
MITRE ATT&CK
- Reconnaissance not seen
- Resource Development not seen
- Initial Access not seen
- Execution not seen
- Persistence not seen
- Privilege Escalation not seen
- Stealth not seen
- Defense Impairment 1 alert
- Credential Access not seen
- Discovery not seen
- Lateral Movement not seen
- Collection not seen
- Command and Control not seen
- Exfiltration not seen
- Impact not seen
Techniques
| Technique | Name | Tactics | Related alerts |
|---|---|---|---|
| T1685.005 | Disable or Modify Tools: Clear Windows Event Logs formerly T1070.001 | Defense Impairment | B1 |
Actions
Approval gate: q-node recommends these actions; none is carried out without human approval. The controls are for illustration only.
-
Draft a detection-rule exception for approved maintenance windows
- Scope
- Detection rule · engineer review
- Privilege
- No privilege required
- Reversibility
- Reversible
Not deployed directly; the draft goes to detection engineering.
Human approval required
Ask the Analyst
Coming soon
The live AI analyst (LLM connection) is coming to this tab soon. It will answer questions like these from the case data:
- Why was this treated as a false positive?
- Which maintenance record did it match?
- Were the logs really archived?
- How can this alert be prevented next time?
Try it on your own data instead of this case: upload your alert or log, let q-node analyze it and answer your questions.