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.
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
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.
Export configurations
Save current configurations of gateways, switches and APs. Remove secrets such as passwords and pre-shared keys before sharing.
Show access reviews
List admin accounts in NavCloud and on devices, with the date someone confirmed each one is still needed.
Show patching
Export device firmware versions and compare them with the current releases on the Navijin firmware page.
Show monitoring and logging
Screenshots or exports showing logs are collected, kept for the agreed period and reviewed.
Show change control
Three to five sample change tickets with approval, test and rollback notes.
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.
FAQ
Frequently asked questions
What if a control is missing?
Say so, show the risk entry and the plan with a date. Honest gaps are treated better than surprises.
Keep learning
Related guides
Build a risk register
Read more →Patch management for network devices
Read more →AAA admin audit trail
Read more →GDPR for Network Teams: Practical Security Controls and Checklist
What the EU General Data Protection Regulation expects from your network: security of processing, access control, logging, encryption, guest Wi-Fi data, CCTV, retention and breach readiness, with a checklist you can apply.
Read more →PCI DSS v4.0 for Networks: Segmentation, Firewalls and Wi-Fi
How the Payment Card Industry Data Security Standard applies to your network: defining the cardholder data environment, segmentation to reduce scope, firewall and router rules, wireless, logging, testing and secure management.
Read more →HIPAA Security Rule for Networks: Protecting ePHI in Clinics and Hospitals
What the US HIPAA Security Rule means for healthcare networks: risk analysis, access control, audit controls, integrity, transmission security, medical device segmentation and contingency planning.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.