An ISO 27001 internal audit should provide credible information about conformity and whether the information security management system (ISMS) is effectively implemented and maintained. Plan the work around important processes, relevant criteria and previous results. Use objective evidence and impartial judgement, then report findings clearly enough for management to act. A checklist can support the work, but it should not replace understanding of the service and control outcomes.
Clause 9.2 of the licensed ISO/IEC 27001:2022 standard establishes internal audit requirements. The planning, sampling and reporting practices below are recommendations for implementation. They do not imply that every audit must use one template, a fixed annual duration or a particular auditor qualification.
Define what the audit must establish
The audit should consider the organisation’s own ISMS requirements as well as the standard’s requirements, and whether the system is implemented and maintained effectively. This matters because an organisation can fail to follow an important internal commitment even where the standard does not prescribe that exact operating method. The audit criteria should make both sources clear.
Distinguish audit from consultancy and routine control operation. An adviser may help design a process; a control owner may check daily performance; an auditor evaluates evidence against criteria with appropriate objectivity. These activities can inform one another, but they serve different purposes and should not be presented as interchangeable.
Set a useful audit question. For example, does the supplier approval process identify material information security requirements and ensure they are addressed before use? That question leads to evidence about actual decisions. Asking only whether a supplier policy exists can leave the main operating risk unexamined.
Build the programme around importance and previous results
ISO 27001 requires internal audits at planned intervals and a maintained audit programme addressing frequency, methods, responsibilities, planning and reporting, with consideration of process importance and previous audit results. See ISO 27001, Clause 9.2. The programme should explain why particular areas receive attention and how the ISMS is covered over time.
Consider material changes and known weaknesses when selecting work. A new cloud service, acquisition, repeated access issue or changed customer commitment may justify focused audit attention. A stable process with strong evidence may require a different depth than one undergoing major redesign. The programme should be responsive without becoming a collection of unplanned investigations.
Identify resources and competence needed. Technical control audits may require specialist knowledge, while management process audits require understanding of governance and evidence. Plan access to systems and people early, especially across locations or suppliers. An audit schedule that ignores these dependencies may be impossible to execute properly.
Set scope and criteria for each audit
Define the service, process, locations, systems, period and boundaries being examined. State the criteria, including relevant standard requirements, internal procedures and other adopted obligations. A clear scope prevents disagreement later about whether the audit was intended to cover a particular team or control population.
Choose a process-based view where it helps reveal connections. An employee departure audit may follow the event from HR through identity systems, business applications and provider access. A release audit may connect risk consideration, approval, testing and deployment. This can expose handoff failures that separate document checks overlook.
Record limitations before and during the work. If a provider cannot supply evidence or a system is unavailable, explain the effect on conclusions. Do not silently reduce the scope while presenting the result as complete. Management should know what was examined and what remains uncertain.
Protect objectivity and impartiality
The standard requires auditor selection and audit conduct that ensure objectivity and impartiality. In practice, examine whether the auditor is evaluating their own work or has incentives that could distort the conclusion. A small organisation may need another competent function or external support for areas where independent challenge is difficult.
Define competence according to the audit. An auditor needs to understand the criteria, gather and evaluate evidence, communicate findings and recognise the limits of their expertise. A course certificate may contribute to the evidence, but it does not automatically demonstrate capability to assess a complex technical environment.
Allow respectful challenge. Audited teams should be able to explain evidence and correct factual misunderstandings, while the auditor remains responsible for the conclusion. Disagreement should be resolved through criteria and evidence rather than hierarchy or pressure to preserve a favourable result before a customer deadline.
Design samples that answer the audit question
Identify the relevant population before selecting a sample. For access reviews, determine the systems and account types included. For changes, identify normal, emergency and unsuccessful releases. A sample of convenient recent records may miss the cases most likely to reveal a process weakness.
Use a reasoned mix of routine and challenging cases. Include different locations, owners, periods or risk levels where those differences matter. Explain the sampling method and limits. A small sample can provide useful evidence, but it should not be represented as exhaustive proof that every transaction complies.
Follow exceptions to resolution. If a record shows rejected access, a failed test or an overdue supplier action, examine what happened next. Effective controls often reveal and manage problems. The presence of an exception is not automatically a failure; the response and applicable criteria determine the audit conclusion.
Triangulate interviews, records and observation
Interviews explain how people understand the process, records show activity and observation can reveal how the work is performed. Use these sources together where appropriate. A confident description may conflict with actual records, while a poorly written procedure may coexist with a sound but undocumented practice that still needs evaluation against the criteria.
Ask people to demonstrate a recent case. This often produces clearer evidence than asking whether they “comply with the policy”. Follow the approval, action and result, and compare them with the required process. Avoid coaching the auditee into the answer the auditor expects.
Protect evidence gathered during the audit. It may include personal data, client information and sensitive weaknesses. Retain only what is needed to support the finding and use controlled references where possible. The audit should not create an uncontrolled collection of information more widely accessible than the source systems.
Write findings that separate criteria, evidence and conclusion
A clear finding identifies the applicable criterion, the observed evidence and the nature of the gap. It should be understandable to a manager who did not attend the audit. Avoid vague statements such as “access control is weak” without explaining the population, evidence and requirement.
Distinguish nonconformities from improvement suggestions according to the organisation’s audit method and the evidence. An auditor’s preferred tool or workflow is not automatically a requirement. Where the criterion is met but a better method may be possible, describe the suggestion appropriately rather than presenting personal preference as a mandatory correction.
Evaluate significance using the adopted method and consequence. Several similar failures may indicate a systemic issue rather than isolated errors. Conversely, one unusual record should not support a sweeping conclusion without further evidence. The report should explain the basis and limits of the assessment.
Report what management needs to decide
The report should state scope, criteria, method, key evidence, findings, limitations and conclusions. Highlight issues that require leadership attention, such as unresolved authority, insufficient resources or repeated ineffective actions. Keep detailed working notes separate where they would obscure the main decision points.
Report results to relevant management as required by Clause 9.2. A finding left only with an operator may never reach the person able to resolve its cause. Agree factual accuracy with the auditee where appropriate, but do not allow that process to remove a supported finding because it is commercially inconvenient.
Connect findings to the corrective action process. The audited function should determine causes and actions, with suitable oversight and verification. The auditor may clarify the requirement and evidence, while avoiding a situation where they design the solution and then independently assess their own design without safeguards.
Hypothetical example: a cloud consultancy audits privileged access
A hypothetical cloud consultancy reports that all administrator access is approved. An internal audit defines the population across customer support environments, internal platforms and emergency accounts. The auditor samples both routine approvals and access retained after a consultant changes assignment.
The evidence shows that normal provisioning is controlled, but removal depends on project managers sending informal messages. Several accounts remain active after work ends. The finding identifies the relevant internal lifecycle requirement, the sample evidence and the missing reliable trigger, rather than simply recommending a particular access product.
Management assigns the service delivery owner to improve the project closure interface and verifies removal across the affected population. Follow-up samples include completed projects and an urgent reassignment. The audit provides useful assurance by tracing the whole lifecycle and directing attention to a specific operating cause.
The report identifies the systems and project dates sampled, including the emergency accounts examined. It does not assume that the same result applies to every customer environment. The audit owner uses the common removal trigger to decide where further sampling is warranted, while service management checks the wider population for immediate exposure.
Hypothetical example: a food manufacturer audits information recovery
A hypothetical food manufacturer maintains production planning and traceability information in several connected systems. Its internal audit initially plans to review backup job logs. The auditor reframes the question around whether the required information can be restored and used in the selected production process.
The audit examines recovery requirements, test records and a recent restoration exercise. Backups complete successfully, but the exercise does not verify a supporting reference database. Operators explain that the database is necessary to interpret restored records. The evidence therefore challenges the claimed recovery coverage.
The finding remains specific to the relevant requirement and tested scope. Management expands the recovery validation and assigns ownership of the dependency. Follow-up checks the revised exercise result rather than accepting an updated plan as proof that recoverability has improved. The example shows how process understanding changes the value of the audit.
Verify that corrective action addresses the cause
Follow-up should distinguish immediate correction from action that prevents recurrence or occurrence elsewhere. Removing one inappropriate account corrects a record; fixing the unreliable departure trigger addresses a potential cause. Both may be needed, and the verification method should reflect the intended result.
Use evidence from operation after the change. A new procedure may be necessary, but it does not show that the revised process works. Sample subsequent transactions or test the relevant scenario. Where insufficient time has passed, record that limitation and plan appropriate later verification.
Review repeat findings across audits. They may reveal weak cause analysis, incomplete coverage, ineffective verification or an unresolved resource decision. Escalate the pattern rather than closing each occurrence as an isolated administrative error.
Commission an audit with a clear assurance purpose
When selecting external support, describe the ISMS scope, important services, previous findings and technical environment. Ask how the auditor will preserve impartiality, select evidence and report limitations. Agree deliverables and internal participation so that the work can produce an informed conclusion rather than a document-only review.
Clarify whether the engagement is an internal audit, readiness review or certification audit. These are different activities with different roles. ISO itself does not certify organisations, as explained in ISO’s certification guidance. Avoid commercial wording that implies a consultant’s internal audit guarantees a certification body’s decision.
CyberVantage360’s ISO 27001 service is a starting point for discussing assurance needs. Share your audit scope and unresolved concerns so the proposed work can address the processes and evidence that matter.
Frequently asked questions
Must internal audit occur once a year?
The standard requires audits at planned intervals and an audit programme that considers process importance and previous results. It does not impose one universal annual format for every organisation. Design coverage and timing that support the ISMS and respond to significant changes and findings.
Can an employee audit their own process?
The organisation must ensure objectivity and impartiality. Reviewing one’s own design or operation can create a conflict that needs to be addressed. Use suitable alternative personnel or external support where necessary, and document how the arrangement provides credible independent challenge.
Is a checklist enough for an internal audit?
A checklist can help organise criteria, but the auditor still needs to evaluate evidence and actual operation. Interviews, records, observation and process walkthroughs can reveal gaps that a document checklist misses. The conclusion should follow the evidence, not the number of completed checklist items.
Does an internal audit guarantee certification?
No. It provides information to the organisation about its ISMS and can support readiness. The certification body conducts its own assessment and decision process. Internal findings should be addressed honestly rather than treating the audit report as a promise of an external outcome.