Windows Security ยท 2.6

๐Ÿ“‹ Audit Logs & Event Viewer

Reading the system's black boxโฑ ~3 min

โœˆ๏ธEvent logs are the plane's black box

Aircraft black boxes record every sensor reading so investigators can reconstruct what happened after a crash. Event Viewer records every login attempt, service start/stop, policy change, and system error โ€” so you (or a forensic investigator) can reconstruct what happened after a breach.

Opening Event Viewer: eventvwr.msc

Log Types to Know

LogWhat It RecordsCompetition Use
SecurityLogin attempts (success & failure), privilege use, account changesMost important โ€” check for unauthorized logins
SystemOS events, driver failures, service start/stopFind malicious services that started automatically
ApplicationEvents from installed programsCheck for crash logs or unauthorized software activity
SetupWindows Update and installation eventsConfirm updates were installed

Configuring Audit Policy

By default, Windows logs very little. You must enable Audit Policy to capture security events. Go to: secpol.msc โ†’ Local Policies โ†’ Audit Policy

Audit SettingRecommend
Audit account logon eventsSuccess, Failure
Audit account managementSuccess, Failure
Audit logon eventsSuccess, Failure
Audit object accessFailure
Audit policy changeSuccess
Audit privilege useFailure
Audit system eventsSuccess, Failure
๐Ÿ’ก TipEnabling audit logging in competition often earns points AND gives you visibility into what's happening on the system โ€” a double benefit.

Reading Security Logs

  • โ€ขEvent ID 4624 โ€” Successful login; note the account name and logon type
  • โ€ขEvent ID 4625 โ€” Failed login; repeated failures = brute-force attempt
  • โ€ขEvent ID 4720 โ€” User account created
  • โ€ขEvent ID 4732 โ€” User added to Administrators group
  • โ€ขEvent ID 4698 โ€” Scheduled task created (often used by malware for persistence)
๐Ÿง Quick Checkfirst try = +5 XP

Where do you find failed login attempts on Windows?

โญ 0 XP๐Ÿ”ฅ 0 days