The short answer
A cyber security audit (often written cybersecurity audit) is an evidence-based check of your security controls against a defined benchmark, such as Cyber Essentials, ISO 27001, PCI DSS or your own policies. The auditor interviews staff, reviews documents and configurations and runs scans, then reports risk-rated gaps and a prioritised roadmap. Plan one every 12 months and after major change.
On this page
- What is a cyber security audit?
- Is an IT security audit the same as a cyber security audit?
- What does a cyber security audit cover?
- Which standard should the audit measure you against?
- How does a cyber security audit work?
- What do you get from a cyber security audit?
- What is a cyber security maturity assessment?
- What is a security posture assessment?
- How often should a cyber security audit be done?
- How do you prepare for a cyber security audit? A checklist
- Is a cyber security audit the same as a penetration test?
- What should you look for in a cyber security audit provider?
- Why Sovereign Secure
- Next step: agree the benchmark and scope
A cyber security audit is a structured, evidence-based check of whether your security controls are in place and working, measured against a stated benchmark. That benchmark might be Cyber Essentials, ISO 27001, PCI DSS, a framework such as the NCSC Cyber Assessment Framework, or simply your own policies. The auditor interviews people, reviews documents and system configurations, samples records and often runs vulnerability scans. You come away with findings ranked by risk and a roadmap of what to fix first, and a general audit usually adds a maturity score for each control area.
The most important decision is the benchmark. Without one, an audit becomes a list of opinions; against a named standard, it tells you exactly where you stand with the buyers and regulators who use it.
What is a cyber security audit?
A cyber security audit tests your controls against stated criteria, within an agreed scope, and records the evidence behind every conclusion. It answers “are we doing what we said, and what the standard requires?” rather than “are we secure?”, which no audit can promise.
The same work is sold as an IT security audit, a security audit, a cyber audit or a cyber security assessment. The labels overlap, so compare quotes on the scope and criteria written into the engagement, not the name.
Is an IT security audit the same as a cyber security audit?
Usually, yes: the terms are often used interchangeably. Where they differ, an IT security audit sometimes means a narrower review of IT systems only, such as servers, networks, accounts and patching, while a cyber security audit usually also covers governance, people, suppliers and incident response. An information security audit is wider still, because it covers information in every form, including paper and conversations.
| Label | What it usually covers | What it can leave out |
|---|---|---|
| IT security audit | Servers, endpoints, networks, user accounts, patching, backups | Policies, training, suppliers, incident response |
| Cyber security audit | Technical controls plus governance, people, suppliers and incident response | Non-digital information, unless agreed |
| Information security audit | All information, digital and physical, often against ISO 27001 | Nothing in principle, if the scope is the whole organisation |
Whichever label a provider uses, check the scope and the benchmark written into the engagement rather than the name.
What does a cyber security audit cover?
A full audit looks at governance and people as well as technology.
| Control area | What the auditor checks |
|---|---|
| Governance and risk | Security roles, approved policies, risk register, board reporting |
| Asset management | Inventories of hardware, software, data and cloud services |
| Network security | Firewall rules, segmentation, remote access, wireless |
| Configuration and patching | Hardened builds, no unsupported software, updates applied on time |
| Identity and access | Multi-factor authentication (MFA), admin accounts, joiners, movers and leavers |
| Malware and vulnerability management | Anti-malware coverage, scanning cadence, how fast findings are fixed |
| Logging and incident response | What is logged and reviewed; a tested incident plan |
| Backup and recovery | Protected backups and evidence of a successful restore test |
| Suppliers and people | Supplier security checks, awareness training, phishing resilience |
Network and configuration checks often go deeper as a separate firewall configuration review, which examines every rule rather than a sample.
Which standard should the audit measure you against?
Pick the benchmark your customers, regulators or insurers already use. If nobody is asking yet, a recognised baseline such as the NCSC’s 10 Steps to Cyber Security gives a sensible structure.
| Benchmark | Best for | Audit outcome | Who carries it out |
|---|---|---|---|
| Cyber Essentials | UK organisations, public-sector and NHS supply chains | Certificate valid for 12 months | An IASME-licensed certification body |
| Cyber Essentials Plus | Buyers who want audited proof of the five controls | Certificate after hands-on technical tests | An IASME-licensed certification body |
| ISO 27001 internal audit | Organisations running or building an ISMS | Internal audit report against clauses 4 to 10 and Annex A | A competent, impartial internal auditor, in-house or outsourced |
| PCI DSS v4.0.1 | Anyone storing, processing or transmitting card data | Report on Compliance or Self-Assessment Questionnaire, plus an Attestation of Compliance | A QSA for a Report on Compliance (or an internal ISA where the card brands or acquirer allow); you complete an SAQ yourself |
| NCSC Cyber Assessment Framework | Essential services, NHS bodies, public sector | Assessment against CAF outcomes | Usually a self-assessment first; some schemes, such as GovAssure, add independent review |
| Your own policy or a general framework, such as the CIS Controls | Anyone without a mandated standard | Gap report and maturity score, no certificate | Any competent auditor |
For card data, the audit is a formal PCI DSS assessment by a QSA. ISO 27001 clause 9.2 requires internal audits at planned intervals, which our ISO 27001 internal audit service covers. Public-sector and critical-service organisations should read our NCSC Cyber Assessment Framework guide.
How does a cyber security audit work?
Most audits follow the same seven steps, whatever the benchmark.
- Scope and criteria. Agree the benchmark, the systems, sites and suppliers in scope, and the evidence period.
- Document request. Policies, network and data-flow diagrams, asset lists, previous reports and the risk register.
- Interviews. Short sessions with IT, HR, finance, operations and leadership to confirm how processes really run.
- Technical review. Configuration review of firewalls, cloud tenants and sample devices, plus vulnerability scanning to confirm patching and hardening.
- Sampling. Records are tested over time, for example checking that a sample of recent leavers lost access on the day they left.
- Findings and grading. Each gap is rated by risk, or by nonconformity grade where the standard uses one.
- Report and close-out. You receive the report, agree owners and dates, and the auditor checks the fixes at follow-up.
What do you get from a cyber security audit?
Expect a report you can act on and show to a customer:
- An executive summary in plain English for the board.
- Findings with evidence, each with a risk rating, the requirement it relates to and a suggested owner.
- A maturity score for every control area, so you can measure progress at the next audit.
- A prioritised roadmap, split into quick wins, the next three months and the next 12 months.
- A mapping to standards where you plan to certify later, so the work counts twice.
Audits for a certification scheme end in that scheme’s formal output: a certificate, an Attestation of Compliance or an internal audit report of nonconformities. A maturity score and roadmap are not part of those outputs, so ask for them in the scope if you want them.
What is a cyber security maturity assessment?
A cyber security maturity assessment scores how well established each control area is, not just whether a control exists. Two organisations can both “have a backup policy”, yet only one tests restores. Some providers call this a security posture assessment.
Scales vary between frameworks and providers. A simple scale from 0 to 5 works for most organisations:
| Score | Level | What it looks like |
|---|---|---|
| 0 | Not in place | No control, or nobody knows whether one exists |
| 1 | Ad hoc | Done by individuals when they remember; nothing written down |
| 2 | Repeatable | Done consistently by habit, but informal and person-dependent |
| 3 | Defined | Documented, approved, assigned to an owner and followed |
| 4 | Managed | Measured and reviewed, with evidence it operates over time |
| 5 | Optimised | Improved continuously from metrics, incidents and testing |
The useful output is the gap between your current score and a target agreed with the board. Few organisations need a 5 everywhere; they need the right level for the risks they carry. Someone also has to own that roadmap after the audit; our guide to the virtual CISO (vCISO) explains one way smaller organisations fill that role.
What is a security posture assessment?
A security posture assessment is a review of how well your organisation can prevent, detect and respond to attacks today: your controls, configurations, exposed systems, people and processes, measured against a benchmark. It combines audit-style evidence review with technical testing, and usually ends with a maturity score and a prioritised roadmap.
It sits between the other common reviews:
| Review | Question it answers | Read more |
|---|---|---|
| Cyber security audit | Do our controls meet the benchmark, and can we prove it? | This guide |
| Cyber security risk assessment | Which risks matter most, and what should we do about them? | Cyber security risk assessment |
| Vulnerability assessment | Which known weaknesses are in our systems? | Vulnerability assessment |
| Penetration test | Could a real attacker get in, and how far? | Penetration testing |
| Security posture assessment | Overall, how strong is our defence right now? | A blend of all four, scoped to your needs |
How often should a cyber security audit be done?
At least once every 12 months, and again after any significant change. The standards you hold usually set the minimum rhythm.
| Driver | Minimum rhythm |
|---|---|
| Cyber Essentials and Cyber Essentials Plus | Certificates last 12 months, so reassess every year |
| PCI DSS v4.0.1 | Validate every year; quarterly internal and external vulnerability scans (11.3.1 and 11.3.2); internal and external penetration tests at least every 12 months and after significant change (11.4.2 and 11.4.3) |
| ISO 27001 | Internal audits at planned intervals (clause 9.2); certification surveillance audits every year and recertification every three years |
| Any organisation | After a merger, a cloud migration, a new critical supplier or a serious incident |
How do you prepare for a cyber security audit? A checklist
Preparation is mostly about finding evidence, not hiding problems. Use this cyber security audit checklist:
- Current hardware, software and cloud service inventory
- Network diagram and data-flow diagram
- Security policies with owners and last review dates
- Risk register and any treatment plans
- List of admin accounts and MFA status for every cloud service
- Patch and vulnerability scan reports for the last three months
- Backup jobs and the most recent restore test
- Incident response plan and incident log
- Supplier list with the security evidence you hold for each
- Previous audit and penetration test reports, with remediation status
Name one coordinator, book interviews early and tell staff the auditor is testing processes, not people.
Is a cyber security audit the same as a penetration test?
No. An audit checks that controls meet a benchmark across your whole organisation, while a penetration test attacks specific systems to prove whether a real attacker could get in, so the two complement each other: see our penetration testing services for the testing side.
What should you look for in a cyber security audit provider?
- The right standing for the benchmark. PCI DSS assessments need a QSA company (check the PCI SSC list of Qualified Security Assessors); Cyber Essentials needs an IASME-licensed certification body; ISO 27001 certificates come from an independent certification body.
- Honesty about independence. A provider that designed or fixed the controls should say so and not call the audit independent.
- Evidence, not questionnaires. Sampling, configuration review and scanning catch what self-assessment misses.
- A usable report and a written scope. Risk-rated findings, owners and a roadmap, against a scope agreed before fieldwork.
Why Sovereign Secure
Sovereign Secure Ltd was incorporated in 2012 and is headquartered in Accrington, Lancashire, with offices in Los Angeles, Singapore, Dubai and Dhaka. Assessing organisations against defined standards is our core work:
- PCI SSC approvals. We are a Qualified Security Assessor (QSA) company, a Qualified PIN Assessor (QPA), a Card Production Security Assessor (CPSA), a P2PE Assessor (Europe and USA) and a 3DS Assessor, and a member of the PCI SSC Global Executive Assessor Roundtable (GEAR) for 2026 to 2028.
- IASME schemes. We are an IASME-licensed certification body and issue Cyber Essentials, Cyber Essentials Plus, IASME Cyber Assurance and Defence Cyber Certification Levels 0 and 1 certificates.
- ISO 27001. We are ISO 27001 certified and run outsourced ISO 27001 internal audits. Certification audits are carried out by our partner certification body, MQA International.
- Technical evidence. Penetration testing, firewall configuration reviews and vulnerability scanning. External ASV scans are delivered through a PCI SSC Approved Scanning Vendor partner.
Where we have advised on or remediated the environment we are reviewing, we say so in the report and do not describe that review as independent. Read more about our wider cyber security consultancy.
Next step: agree the benchmark and scope
Tell us who is asking for the audit, what they want to see and your deadline. We will tell you which benchmark fits and which of our services cover it. Contact our team or call +44 161 523 5276.
If the benchmark is already set, see where you stand first with a free self-check: the PCI compliance check, the Cyber Essentials readiness check or the ISO 27001 checklist.
Free tools and services
- PCI compliance checkAnswer 22 questions for a readiness score, your likely SAQ and a fix list.Start the free check
- Cyber Essentials readiness checkAnswer 20 questions for a readiness score and a fix list before you apply.Start the free check
- Talk to usTell us what you need. We aim to reply within one working day.Get a quote
Last reviewed October 2026 by the Sovereign Secure assessment team.




