CyberKit

Authentication Logs

Also called Auth Logs, Logon Logs.

Records of login attempts, successes, and failures across systems.

What it is

Authentication logs record identity events (successful and failed logons, logoffs, account lockouts, and credential use) across operating systems, directory services, applications, and cloud identity providers. Examples range from Windows logon events to Linux auth.log entries and identity-provider sign-in records.

Why it matters

Detecting credential abuse starts with them: brute force, password spraying, suspicious logon times or locations, and lateral movement via reused credentials all surface here. Correlating authentication events across sources is often what reveals the spread of an intrusion.

In practice

A spray of failed logons across many accounts followed by one success from an unusual country, marking a compromised credential.

What to look for

  • Failures followed by success for one account.
  • Logins from new locations or at odd hours.
  • Many accounts failing from one source.

Common mistake

Looking at one system's logs alone. Correlate VPN, cloud identity and domain logs.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

Read next

  • Cloud Audit Logs: Records of management-plane API activity in a cloud environment.
  • Web Access Logs: Server-side records of every HTTP request a web server handles.
  • Log Enrichment: Adding external context to log events to make them more useful.

Sources