Types of Security Logs: A Complete Guide for Cybersecurity Monitoring

Security logs are timestamped records of events that help you detect and investigate attacks. The main types are authentication logs, operating system and endpoint logs, firewall and network logs, DNS and web proxy logs, application and web server logs, cloud audit logs, database logs, email logs and endpoint detection (EDR) telemetry.

Jul 03, 2025 - 12:27
Updated: 
106.7k

SOC & Blue Team in Cybersecurity & Ethical Hacking · Explainer

SOC Analyst, lesson 3 of 16

Types of Security Logs: A Complete Guide for Cybersecurity Monitoring

Quick answer: Security logs are timestamped records of events that help you detect and investigate attacks. The main types are authentication logs, operating system and endpoint logs, firewall and network logs, DNS and web proxy logs, application and web server logs, cloud audit logs, database logs, email logs and endpoint detection (EDR) telemetry. Each answers a different question: who logged in, what ran, what talked to what, and what changed. Collect them centrally in a SIEM, synchronise clocks, protect them from tampering, and in India keep them for at least 180 days as CERT-In directions require.

Key takeaways

  • No single log type shows the whole attack; combine several.
  • Authentication, endpoint and network logs give the fastest wins.
  • Accurate time synchronisation makes logs usable as evidence.
  • CERT-In requires 180 days of logs kept within India.
  • NIST SP 800-92 and CISA guidance describe good log management.

Table of Contents

What Are Security Logs?

A log entry records what happened, when, where and who or what caused it. NIST SP 800-92 describes log management as generating, transmitting, storing, analysing and disposing of these records. Logs support alerting, incident investigation, compliance audits and troubleshooting. During an incident, NIST SP 800-61 Rev. 3 treats them as core evidence.

What Are the Main Types of Security Logs?

Log typeExamplesWhat it reveals
AuthenticationActive Directory, Entra ID, VPN, SSOLogins, failures, MFA prompts, lockouts
Operating systemWindows Security log, Linux auth.log or journaldProcess starts, privilege use, service changes
Endpoint (EDR)EDR or Sysmon telemetryMalicious processes, persistence, file changes
Firewall and networkFirewall, NetFlow, IDSAllowed and blocked connections, scans
DNS and proxyResolver logs, web proxyMalware callbacks, phishing domains
Application and web serverApache, Nginx, IIS, app audit trailsInjection attempts, abuse of business logic
Cloud auditAWS CloudTrail, Azure Activity Log, Google Cloud Audit LogsAPI calls, permission changes, new keys
DatabaseDatabase audit logsBulk reads, privilege grants, schema changes
EmailMail gateway and mailbox auditPhishing delivery, forwarding rules

The OWASP Logging Cheat Sheet explains what application developers should record and what to leave out, such as passwords and session tokens.

Which Events Should You Watch First?

SourceEventWhy it matters
Windows4624 and 4625Successful and failed logons
Windows4688New process created (enable command line capture)
Windows4720 and 4732Account created, user added to a security group
Windows1102Security log cleared
Linuxsshd entries in auth.log or journaldSSH logins and failures
CloudNew access keys, disabled loggingCommon attacker actions after access

Windows events depend on advanced audit policy being enabled. On Linux you can review recent SSH activity with:

sudo journalctl -u ssh --since "24 hours ago"

On some distributions the unit is named sshd instead of ssh.

How Should You Collect and Protect Logs?

  • Centralise logs in a SIEM; see our guide on how SIEM works.
  • Synchronise time with NTP on every system.
  • Use standard formats such as syslog per RFC 5424 and forward over TLS.
  • Protect integrity with restricted access and write-once or immutable storage.
  • Alert on gaps, since a silent source can mean an attacker disabled logging.
  • Prioritise sources, as recommended in the joint CISA event logging best practices.

What Do Indian Rules Require?

The CERT-In directions of 28 April 2022 require service providers, intermediaries, data centres and government bodies to enable logs of all their ICT systems, keep them securely for a rolling 180 days within India, and report listed incidents within 6 hours of noticing them. Logs that contain personal data must also be handled under the DPDP Act 2023. WebAsha offers practical SOC and log analysis training.

References

Frequently Asked Questions

Authentication, operating system, endpoint, firewall and network, DNS and proxy, application, cloud audit, database and email logs are the main types used in monitoring.

Start with authentication logs, endpoint or EDR alerts, firewall logs and email logs, because they cover most common attack paths with the least effort.

CERT-In directions of April 2022 require covered entities to keep ICT system logs securely for a rolling 180 days within Indian jurisdiction.

It records a failed logon attempt. Many 4625 events across accounts from one source can indicate password guessing or a password spraying attempt.

Without consistent time across systems, investigators cannot build an accurate timeline of an incident, and the logs become weaker as evidence.

Passwords, session tokens, full card numbers and other secrets. The OWASP Logging Cheat Sheet lists data to exclude or mask before storage.

Logs are the raw records. A SIEM collects, normalises and correlates logs from many sources to raise alerts and support investigations.

Commonly in /var/log/auth.log or /var/log/secure, and in the systemd journal, which you can query with the journalctl command.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Wow Wow 0
Sad Sad 0
Angry Angry 0
Vaishnavi

Vaishnavi is a skilled tech professional at the Ethical Hacking Training Institute in Pune, responsible for managing and optimizing the technical infrastructure that supports advanced cybersecurity education. With deep expertise in network security, backend operations, and system performance, she ensures that practical labs, online modules, and assessments run smoothly and securely. Her behind-the-scenes contributions play a vital role in delivering a seamless and secure learning experience for aspiring ethical hackers.