Boards, regulators, customers and certification bodies all want independent evidence that security controls actually work, and the cybersecurity auditor is the person who plans the tests, gathers the evidence and gives that opinion. The career spans internal audit teams, external assurance firms, certification bodies and regulators, and each setting has its own standards and independence rules. This guide explains what the role does using the ENISA European Cybersecurity Skills Framework (ECSF) profile, the skills and tools it needs, routes in from IT, security operations, GRC and accounting, the certifications that help, and how auditors progress. It is written for practitioners considering audit and for managers building an audit function.
Key takeaways
- Independence is the job. The ECSF profile requires auditing with integrity, impartiality and independence; an auditor's opinion is only worth something if they did not design or run the controls they test.
- Evidence beats opinion. The profile stresses working systematically and deterministically from evidence: sampling, re-performance, inspection of configuration and logs, and protecting the integrity of audit records.
- Four very different employers. Internal audit, external assurance (for example SOC 2), management system certification (for example ISO/IEC 27001) and regulatory supervision each follow different standards and reporting lines.
- Technical depth is now expected. Cloud, identity and automation controls cannot be audited from screenshots; auditors who can query configuration, logs and identity data directly are in demand.
- CISA is the anchor certification. ISACA CISA is the most widely recognised IS audit credential, complemented by ISO 27001 Lead Auditor for certification audits and the IIA CIA for internal audit careers.
What the role does
ENISA's ECSF lists the Cybersecurity Auditor as profile 6 of 12. Its mission is to perform independent reviews of the effectiveness of processes and controls and of compliance with legal, regulatory and policy frameworks, and to test and verify cybersecurity products, functions and policies against guidelines, standards and regulations. Alternative titles in the profile include Information Security Auditor, GRC Auditor, Cybersecurity Audit Manager and Information Security Risk and Compliance Auditor. ENISA states that the framework is being revised, with a public consultation planned for the end of 2026. In the US NICE Framework (Components v2.2.0, April 2025), the closest work roles are Technology Program Auditing and Security Control Assessment; see the NICE Workforce Framework Guide.
| ECSF element | Cybersecurity Auditor profile (summarised) | What it looks like in practice |
|---|---|---|
| Deliverables | Cybersecurity audit plan; cybersecurity audit report | Annual audit plan agreed with the audit committee; engagement reports with rated findings |
| Main tasks | Develop audit policy and methods; define scope, objectives and criteria; plan the audit; review the target against its risk profile; audit legal and regulatory compliance; execute the plan and collect evidence; protect audit records; produce conformity and assurance reports; monitor remediation | Scoping meetings, walkthroughs, control testing, evidence requests, closing meetings, follow-up of agreed actions |
| Key skills | Evidence-based, systematic work; apply audit frameworks and techniques; analyse processes and technical and organisational controls; find weaknesses and ineffective controls; collect and protect audit information; independence | Designing test steps, sampling, writing findings that management accepts |
| e-CF competences | B.3 Testing (level 4), B.5 Documentation Production (3), E.3 Risk Management (4), E.6 ICT Quality Management (4), E.8 Information Security Management (4) | A mix of testing discipline and management system knowledge |
Where auditors work
| Setting | Who the auditor reports to | Typical standards | Output |
|---|---|---|---|
| Internal audit (third line) | Chief audit executive and the audit committee | IIA Global Internal Audit Standards; ISACA IT audit standards | Assurance reports and rated findings for management and the audit committee. See the Internal Audit for Cybersecurity Guide. |
| External assurance firm | Engagement partner | Attestation standards such as those used for SOC 2 reports | Independent reports for customers and auditors. See the SOC 2 Guide. |
| Certification body | Certification body management | ISO/IEC 27001 requirements, management system audit guidance | Certification decisions and surveillance audits. See the ISO 27001 Certification Guide. |
| Regulator or assessor scheme | Supervisory authority or scheme owner | Sector rules and assessment schemes such as CMMC or PCI DSS | Supervisory findings, assessment results |
A typical engagement
- Plan: agree scope, objectives and criteria (for example "privileged access to the payments platform against the access control standard and ISO/IEC 27001 Annex A"), based on risk.
- Understand: walk through the process and the systems with control owners, and document the controls as designed.
- Test design: check that each control, if it operated, would address the risk.
- Test operating effectiveness: sample over the period, re-perform where possible (for example re-run an access review query), and inspect configuration and logs rather than screenshots.
- Report: write findings as condition, criteria, cause, consequence and recommendation, agree management actions with owners and dates.
- Follow up: verify that actions were implemented and closed findings stay closed.
Core skills and tools
Skills
- Audit method: risk-based planning, control design and operating effectiveness testing, sampling, evidence standards, working papers and finding writing.
- Control frameworks: ISO/IEC 27001:2022 and its Annex A, NIST CSF 2.0, NIST SP 800-53 Rev. 5 control families, CIS Controls v8.1, and sector frameworks your clients use. See the NIST CSF to ISO 27001 Mapping Guide.
- Technical literacy: enough cloud, identity, network and endpoint knowledge to read configuration, query logs and spot when evidence does not prove what it claims. Identity and access controls (joiners, movers and leavers, privileged access, MFA coverage, access reviews) are tested in almost every audit.
- Data analysis: testing whole populations instead of samples with SQL, Python or audit analytics tools, for example comparing every active account against the HR leaver list.
- Communication: interviewing without leading, writing findings that are precise and fair, and holding a position under pressure from senior management.
- Ethics and independence: recognising and declaring conflicts, and refusing to audit work you designed.
Tools
| Tool category | Used for |
|---|---|
| Audit management software | Audit universe, plans, working papers, findings and follow-up tracking |
| Data analytics (SQL, Python, spreadsheets, audit analytics tools) | Full-population testing of accounts, changes, access and transactions |
| Cloud and identity consoles with read-only roles | Inspecting configuration and policy directly rather than relying on screenshots |
| Log platforms and SIEM (read-only) | Verifying that logging and alerting controls operate |
| Continuous controls monitoring | Automated evidence collection for recurring tests. See the Audit Evidence and Continuous Controls Monitoring Guide. |
Where identity fits
Machine and agent identities are a growing source of audit findings because they rarely appear in the HR-driven processes auditors test. A strong auditor asks for the full inventory of service accounts, API keys, OAuth applications and AI agents, tests whether each has an owner and whether its credentials are rotated, and checks that access reviews include them. See the Audit Readiness for AI Agents and NHIs.
Routes into the role
- From IT operations or system administration: you know how controls are actually run; learn audit method, evidence standards and report writing.
- From security operations or engineering: strong technical testing skills; the shift is to independence, structured criteria and documenting work so a reviewer could re-perform it.
- From GRC or compliance: you know frameworks and evidence collection from the other side; build testing depth and an independent mindset.
- From financial audit or accounting: strong on method and professional standards; build technical literacy, often through an IT audit rotation and CISA.
- Graduate schemes: assurance firms and large internal audit functions run IT audit graduate programmes, a common way in without prior security experience. See the Career Change into Cyber Security Guide.
Building evidence
- Write a test programme for one control area (for example privileged access) with criteria, test steps and evidence required.
- Run a full-population test on data you are allowed to use, such as comparing active accounts with leavers in a lab or an approved internal data set.
- Write three practice findings in condition, criteria, cause, consequence and recommendation form.
- Shadow or support an internal audit or ISO 27001 internal audit.
Certifications that help
| Certification | Body | Why it helps |
|---|---|---|
| CISA | ISACA | The core IS audit credential; its domains are Information Systems Auditing Process; Governance and Management of IT; Information Systems Acquisition, Development and Implementation; Information Systems Operations and Business Resilience; and Protection of Information Assets. See the CISA Certification Guide. |
| ISO/IEC 27001 Lead Auditor | Accredited training providers | Required in practice for certification body auditors and useful for internal ISMS audit. See the ISO 27001 Lead Auditor and Lead Implementer Guide. |
| CIA | The IIA | The general internal audit credential; valuable if you aim to lead an internal audit function. |
| CCAK | Cloud Security Alliance | Cloud auditing knowledge. CSA states it has not offered the CCAK since 3 October 2025; existing holders may still list it, so check CSA's site for the current position. |
| Scheme credentials (for example CMMC CCA, PCI QSA) | Scheme owners | Needed to perform assessments under those schemes. See the CMMC Certified Professional and Assessor Guide and the PCI ISA and QSA Certification Guide. |
Check experience requirements, exam format and fees on each body's own pages before booking; ISACA, for example, requires candidates to demonstrate experience when applying for CISA certification. For AI system audits, see the ISACA AAISM and AAIA AI Certifications Guide.
Progression
| Stage | Typical titles | Scope |
|---|---|---|
| Entry | IT audit associate, junior auditor | Performs test steps and documents working papers under supervision |
| Practitioner | IT or cybersecurity auditor, senior auditor | Runs engagements, designs tests, writes findings |
| Manager | IT audit manager, lead auditor | Owns the technology audit plan or a client portfolio; reviews others' work |
| Senior leader | Head of IT audit, audit director, partner, chief audit executive | Sets the audit strategy; reports to the audit committee or leads a practice |
Many auditors move across the lines of defence after a few years: into risk management (see the Cybersecurity Risk Manager Career Guide), GRC, security architecture or CISO roles, where knowing how controls fail under test is a strong advantage. Specialisms include cloud audit, data and analytics audit, third-party assurance and AI system audit.
Measuring your progress
- Finding quality: share of your findings accepted by management without material change.
- Population testing: share of your tests performed on full populations rather than samples.
- Remediation impact: agreed actions from your audits that were implemented and stayed effective at follow-up.
Common failure patterns
- Screenshot evidence: accepting a point-in-time image as proof that a control operated over a year.
- Auditing your own design: moving from implementation to audit and testing the same controls, which breaks independence.
- Human-only scope: testing joiner and leaver processes for staff while ignoring service accounts, keys and AI agents.
- Findings without cause: reporting the symptom (an orphaned account) without the process failure behind it, so the problem returns.
Practitioner checklist
- Read the ECSF Cybersecurity Auditor profile and score yourself against each task and skill.
- Decide which setting you want (internal, external assurance, certification body, regulator) and learn its standards.
- Learn to test design and operating effectiveness, and to document work so it can be re-performed.
- Build data skills to test full populations with SQL or Python.
- Get hands-on with read-only access in one cloud platform and one identity provider.
- Plan for CISA, and add ISO 27001 Lead Auditor or CIA depending on your target setting.
- Practise writing findings in condition, criteria, cause, consequence and recommendation form.
- Keep an independence log: never audit controls you designed or operated in the past [12 months].
Standards and references
- ENISA: European Cybersecurity Skills Framework Role Profiles
- ENISA: European Cybersecurity Skills Framework (ECSF)
- ISACA: CISA Certification
- The IIA: Global Internal Audit Standards
- ISO: ISO/IEC 27001:2022 Information security management systems, Requirements
- NIST: NICE Framework Current Versions
Related NHI Mgmt Group resources: Cybersecurity Careers Guide · Audit, Assurance and Compliance Guide · Internal Audit for Cybersecurity Guide · ENISA ECSF Skills Framework Guide