CyberKit

Firewall Logs

Records of network connections a firewall allowed or denied.

What it is

Firewall logs document connection attempts evaluated against a rule set, recording source and destination addresses and ports, protocol, the action taken (allow or deny), and timestamps. They are generated at network and host firewalls alike.

Why it matters

They reveal which hosts talked to which, expose scanning and lateral-movement attempts, and show blocked outbound attempts that hint at malware trying to reach C2. Denied-connection patterns are often an early, high-signal indicator that something on the inside is misbehaving.

In practice

A burst of denied outbound connections from a workstation to a sequence of foreign IPs, flagging an implant cycling through fallback C2 servers.

What to look for

  • Denied outbound connections from internal hosts.
  • Allowed connections to rare destinations on unusual ports.
  • Rule changes around an incident.

Common mistake

Logging only denies. Allowed traffic is where the attacker succeeded.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

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

  • Palo Alto Networks NGFW Commercial

    A next generation firewall that enforces policy by application and user and logs each session.

  • Cloudflare WAF Commercial

    Filters web traffic at the edge before it reaches the application.

  • Suricata Open source

    Can run inline as an IPS to block traffic that matches its rules. Our notes.

  • Snort Open source

    A long standing open source IDS and IPS with a large public rule set.

Read next

  • Flow Logs: Metadata records summarizing network conversations, without packet payloads.
  • Proxy Logs: Records of outbound web requests passing through a forward proxy.
  • DNS Logging: Recording the domain-name lookups that hosts request and resolve.

Sources