Tutorials · Security

How to Build a Network Admin Audit Trail With AAA Accounting and Syslog

Know who changed what, when and from where: combine AAA accounting, syslog, synchronised time and protected log storage into an audit trail that stands up in an investigation.

Intermediate15 min6 steps

Quick answer

Accountability is the A that most networks skip. AAA accounting records each admin session and command. Syslog records device events. With accurate time and tamper-resistant storage, together they show exactly who changed what and when.

This trail is what auditors ask for under ISO 27001, PCI DSS and NIS2, and what incident responders need in the first hour.

Key terms

Accountability
Tracing every action to one identified person. It requires unique accounts, no shared logins.
Non-repudiation
The person cannot credibly deny the action, because the record is authenticated and protected.
Accounting record
A start, stop or command entry sent by the device to the AAA server.
Log retention
How long logs are kept. Many policies require at least 12 months, with 3 months instantly searchable.

Before you start

  • Central AAA (TACACS+ or RADIUS) with unique admin accounts
  • A syslog or SIEM server
  • NTP servers reachable from all devices

Step by step

  1. Synchronise time everywhere

    Point every device to the same internal NTP servers and set the same time zone or UTC. Logs from unsynchronised clocks cannot be correlated.

    ntp server 10.99.0.5 prefer
    ntp server 10.99.0.6
    clock timezone UTC 0
    
  2. Enable command accounting

    Record every privileged command with start-stop records.

    aaa accounting commands 15 default start-stop group tacacs+
    aaa accounting exec default start-stop group tacacs+
    
  3. Send syslog to a central server

    Include configuration-change and login events. Use TCP or TLS syslog where the device supports it.

    logging host 10.99.0.30 transport tcp port 6514
    logging trap informational
    archive
     log config
      logging enable
      notify syslog
    
  4. Protect the logs

    Store logs on a server admins cannot edit, ideally write-once (immutable) storage, and forward a copy off-site.

  5. Alert on what matters

    Create alerts for break-glass account use, logins outside working hours, firewall-policy changes and AAA server failures.

  6. Review and retain

    Review admin activity weekly. Keep logs for the period your regulations require.

Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.

Pro tips

  • Disable shared accounts such as 'admin'. One shared account destroys accountability for everyone who uses it.
  • Include the ticket number in a session banner or change comment, so log entries link to approved changes.
  • Test restoring last month's logs. An archive you cannot search is not evidence.

Last reviewed:

FAQ

Frequently asked questions

What is AAA accounting?

The part of AAA that records what an authenticated user did: when they logged in and out, which commands they ran and how much data they used.

How long should network logs be kept?

It depends on regulation and policy. A common baseline is 12 months, with the most recent 90 days searchable immediately.

Why does time synchronisation matter for security?

Without matching clocks you cannot line up events from switches, firewalls and servers, and an investigation's timeline falls apart.

Stuck on a step?

Ask Navijin technical support or an authorised partner for help with your configuration.