Hands-on tutorial

Tutorials · Compliance

How to Prepare a Network Security Audit Evidence Pack

Auditors ask for proof, not promises. Collect configuration exports, access reviews, logs, change records and firmware status into one organised pack before the audit starts.

Intermediate12 min7 steps

Before you start

  • The list of controls in scope (from the auditor or your policy)
  • Admin access to NavCloud, gateways and switches
  • A shared folder with restricted access

Step by step

  1. Map each control to evidence

    Make a table: control, what proves it, where it comes from, who owns it. Example: 'Admin access is logged' → AAA accounting log export.

  2. Export configurations

    Save current configurations of gateways, switches and APs. Remove secrets such as passwords and pre-shared keys before sharing.

  3. Show access reviews

    List admin accounts in NavCloud and on devices, with the date someone confirmed each one is still needed.

  4. Show patching

    Export device firmware versions and compare them with the current releases on the Navijin firmware page.

  5. Show monitoring and logging

    Screenshots or exports showing logs are collected, kept for the agreed period and reviewed.

  6. Show change control

    Three to five sample change tickets with approval, test and rollback notes.

  7. Index and date everything

    Name files by control number and date. Auditors move faster when they can find evidence themselves.

Pro tips

  • Collect evidence continuously each month instead of in the week before the audit.
  • Never send live passwords or private keys as evidence.