Cybersecurity audits: evidence, boundaries and remediation
Cybersecurity audits examine agreed controls and evidence, such as access settings, device protection, patching, backups, policies and recovery records. The report should state its scope, exclusions and findings, with an owner for each fix. Auditing differs from attempting exploitation in a penetration test. An audit is not certification and does not guarantee that every weakness has been found. An audit is one part of what NZ businesses need from cyber security.
Tell us what you need covered and request a written proposal.
Define what the audit will examine
List the systems, locations, controls and requirements the audit will cover. Agree what evidence will be supplied and what cannot be tested. Ask for exclusions before approving work. The penetration testing guide explains a separate engagement that attempts to exploit weaknesses. If you need a test rather than an audit, see Christchurch penetration testing.
Examine evidence rather than assurances
Review access settings, protection records, patching, backup results and incident preparation within the agreed scope. Ask how evidence is sampled and what those samples cannot tell you. Read the business backup guide when defining recovery checks. A configured backup is not evidence of a successful restore.
Require a report you can act on
Ask for findings ranked by business impact, evidence supporting each finding and a recommended action. Name who will fix each issue and who approves the work. Confirm whether retesting is included. Read the managed IT cost guide before assuming changes are part of recurring support.
Keep assessment and external decisions separate
An audit can support evidence gathering for a cyber insurance application. It does not decide cover or award certification. Agree who checks that each issue is fixed. Decide when changes to systems or requirements call for another review. A report will not fix the controls. Someone needs to own the work.
Frequently asked questions
What does a cybersecurity audit examine?
A cybersecurity audit examines the controls and evidence inside its agreed scope. This can include access settings, device protection, patching, backups, recovery tests, policies and incident response records. Ask which systems and requirements are excluded. Read the business backup guide when defining recovery checks, and this audit scope guide before commissioning work. An audit is not a guarantee of security or certification.
What should an audit report include and who fixes the findings?
Ask for the scope, evidence examined, limitations and findings ranked by business impact. Each finding should have a recommended action, an owner and a way to verify completion. Remediation and retesting need an agreed scope and budget. Use the discovery call to establish responsibilities. Receiving a report does not mean the weaknesses have been fixed.
How does penetration testing differ from a cyber security audit?
Penetration testing attempts to exploit weaknesses within an authorised scope. An audit examines controls and evidence against agreed requirements, which can include policies, access settings and recovery records. They answer different questions and can complement each other. Read the penetration testing guide and agree the boundaries before commissioning either engagement.
What security evidence might a cyber insurer request?
An insurer may ask for evidence of multi-factor authentication, device protection, backups, access controls and incident response preparation. The exact questions depend on the insurer and policy. Match each answer to current records and disclose gaps. Use the audit evidence guide to organise records, then confirm what the insurer will accept.
Tell us what you need covered and request a written proposal.