Insufficient Security Event Logging
The host's audit policy and log settings do not record key security events, or keep them only briefly and locally, so attacks may go unseen and uninvestigated.
| Severity | Medium |
| CVSS 3.1 | 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Open in the calculator |
| CVSS 4.0 | 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-778: Insufficient Logging |
| OWASP Top 10 | A09:2025 Security Logging and Alerting Failures |
| Category | Insufficient Logging |
Description
The host does not record enough security-relevant activity to detect or investigate an attack: attacker activity such as privilege escalation, creation of accounts and services, credential theft and lateral movement may not be recorded, or the record may be overwritten or deleted before anyone reviews it. Typical gaps on Windows are an audit policy that relies on the limited defaults, so that events such as process creation with command lines, changes to local group membership, and new services and scheduled tasks are not logged; a Security log small enough to overwrite itself within hours or days; and no forwarding of events to a central platform. On Linux the equivalents are auditd not installed, or running without rules for privileged commands and changes to authentication files, and system journals that are not persistent or not sent off the host.
The organisation is then less likely to detect an intrusion while it is in progress, and may be unable to establish its scope, which data was affected and whether the attacker remains, which also affects its ability to meet notification duties. The weakness gives an attacker no access in itself, but increases the impact of any intrusion.
The weakness is identified by reviewing the effective audit policy with auditpol /get /category:* together with log sizes and retention, checking auditctl -l and the logging configuration on Linux, and confirming whether the actions performed during testing appear in the host's logs and in the organisation's central log platform.
Remediation
- Configure an advanced audit policy through Group Policy (
Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration) based on a recognised baseline, such as Microsoft's audit policy recommendations or the CIS Benchmarks, and enable Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings. - Record at least logon and account lockout events, credential validation, account and group management, process creation with command lines (Include command line in process creation events), service and scheduled task creation, audit policy changes and log clearing.
- Increase the size of the Security log and other important logs so that they hold several days of activity locally.
- Forward events to a central log platform or SIEM, using Windows Event Forwarding or an agent, so that they survive deletion on the host, and keep them for a defined retention period.
- On Linux, install and enable
auditdwith rules for privileged commands, identity and authentication files and sudo use, and forward system and audit logs off the host. - Synchronise the clocks of all hosts so that events can be correlated.
Confirm the fix by performing a set of test actions and checking that each appears, with enough detail, in the central platform.
References
- learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/audit-policy-recommendations
- learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/advanced-audit-policy-configuration
- cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html
- attack.mitre.org/mitigations/M1029
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.