ISO 27001 Internal Audit and Management Review — Requirements, Records and Common Gaps
The internal audit report says a supplier-access process is effective. Management review records a concern that procurement cannot identify all subcontractors with access. Nobody has connected the two findings or assigned a decision owner.
Internal audit and management review help an organisation evaluate its ISMS and decide what needs to change. Their value depends on the questions examined, the evidence considered and what happens after findings are reported.
This article follows that evaluation and decision process. Use the existing ISO 27001 evidence guide for the wider inventory of audit records, and the standard overview for the full ISMS structure. The examples here are fictional and illustrate possible arrangements rather than mandatory templates.
Give internal audit and management review different jobs
Internal audit provides information about whether the ISMS conforms to the organisation's requirements and ISO/IEC 27001, and whether it is effectively implemented and maintained. Management review allows top management to evaluate continuing suitability, adequacy and effectiveness and make the relevant decisions.
A routine operational meeting can provide useful information, but it does not automatically fulfil either activity. Keep their purposes clear even where the organisation uses an integrated management system or existing governance meetings.
ISO/IEC 27007 provides ISMS auditing guidance. Its published 2020 edition is under revision at the time of writing; a draft revision should not be described as a new mandatory certification requirement. Use the applicable ISO/IEC 27001 requirements as the assessment basis.
Plan audit coverage around the operation
Build a programme that considers the importance of the processes and previous audit results. Identify the scope and criteria for each audit. Include the relevant ISMS activities and locations over the programme rather than repeatedly reviewing only the policy folder.
For a distributed company, central IT may control user identities while local managers approve access and procurement appoints support providers. An audit confined to one central procedure can miss whether those interfaces work.
|
Programme consideration |
Practical audit question |
Possible evidence route |
|
Changes in the operation |
Was the new support provider brought into the ISMS arrangements? |
Procurement decision through access approval and monitoring |
|
Earlier findings |
Has the repeated account-removal issue actually changed? |
Previous finding through action and later departures |
|
Important processes |
Can the team explain how critical customer information is handled? |
Process interview supported by selected operating records |
|
Distributed responsibilities |
Do central and local teams use the same approval boundary? |
Compare central settings with local requests and exceptions |
The table illustrates planning questions. It does not prescribe a sample size, audit frequency or identical programme for every organisation.
Use competent auditors and protect objectivity
Select auditors with competence appropriate to the work and arrange the audit so that objectivity and impartiality are maintained. Completing a course can contribute to competence, but a course certificate alone does not establish the ability to audit every technical process.
In a small organisation, consider cross-functional arrangements or a suitable external internal auditor. Evaluate familiarity with the business, conflicts of interest and the ability to interpret relevant evidence. Someone who designed a process should not simply mark their own implementation satisfactory without an arrangement that protects objectivity.
For course selection, the existing ISO 27001 auditor-training article addresses internal-auditor and lead-auditor learning routes. Certification assessment remains a separate activity.
Follow a transaction through the process
A fictional organisation operates in Abu Dhabi and Kuala Lumpur. A central identity team creates accounts, local managers approve business access, and a regional supplier provides out-of-hours support.
The internal auditor chooses a recent support-contractor departure. The supplier's email reports the termination on 4 November. The service desk closes its task that day, but the production application's separate account is disabled on 8 November. The auditor checks what the approved procedure requires, whether any activity occurred in the intervening period and whether other departures have the same interface problem.
The finding must follow the applicable criteria and evidence. The example dates alone do not establish a nonconformity or a universal four-day rule. The useful question is whether the organisation's required access-removal arrangements were met and whether the process works across its systems.
For deeper operating records, refer to the SaaS evidence article. An internal audit should evaluate those records in context rather than reproduce another technical checklist.
Write findings that someone else can understand
Record the criterion examined, the evidence and the resulting conclusion. If a requirement was not fulfilled, state the gap clearly. A note saying “access needs improvement” may not tell the owner what failed or what evidence led to the finding.
Retain enough information to explain the sample and limitations. A successful check of one account does not establish the condition of every account. Avoid turning a sample into an unsupported claim about the whole population.
Report results to relevant management and retain evidence of the audit programme and results. Connect findings to the organisation's correction and corrective-action process without treating the auditor's own preferred solution as the only acceptable response.
Prepare management review inputs that support decisions
Bring information that allows top management to evaluate the ISMS: previous actions, relevant changes in context and interested-party requirements, security-performance information, audit results, risk-assessment results, treatment progress and improvement opportunities. Check the complete applicable requirements rather than using this summary as a substitute for the standard.
Give trends and exceptions enough explanation. A dashboard showing 98 per cent completion may conceal the same high-risk access review being omitted each time. Explain the population, what was missed, the consequence and what decision is needed.
ISO/IEC 27004 provides supporting guidance on security-performance and ISMS-effectiveness evaluation. Use measures that help explain the organisation's situation; do not assume a dashboard or a particular commercial tool is compulsory.
Turn the review into recorded decisions
Management review results should include decisions about improvement opportunities and any needed ISMS changes. Preserve evidence of what was decided. Where an action is agreed, identify who will deliver it, the expected timing and how progress will be evaluated.
|
Information considered |
Illustrative management decision |
Follow-up that makes the decision usable |
|
Contractor exits miss a separate application |
Integrate that application into the supplier-exit workflow |
Assign the process owner and evaluate subsequent departures |
|
A growing support team exceeds review capacity |
Allocate additional review responsibility and resources |
Check whether the revised arrangement reaches the relevant population |
|
A provider changes its service arrangement |
Review the dependency and related risk treatment |
Retain the review outcome and update affected responsibilities |
|
A recovery exercise leaves an unresolved limitation |
Determine the necessary change and accountable owner |
Evaluate the later exercise against the unresolved issue |
These are possible decisions, not promised audit outcomes. Record a reasoned decision where no change is needed as well as where work is authorised.
Keep follow-up visible between review dates
Do not wait for the next formal meeting to discover that an important action has no owner. Maintain suitable progress information and escalate delays through the organisation's arrangements. Where a repeated finding appears, evaluate whether the earlier corrective action addressed the cause.
For a data-centre operator, include the relevant operator and tenant interfaces in evaluation. Use the existing data-centre scope guide to clarify those responsibilities and the data-centre certification service page for broader assessment enquiries.
Applying the evaluation process across countries
For UAE and Malaysian operations sharing one ISMS, establish how local evidence reaches the audit programme and top management. Different public holidays, working hours, suppliers or information systems may affect evidence availability and follow-up, even where the central process is shared.
The UAE and Malaysia guides provide local certification context. For other operating locations, use the existing Saudi Arabia, Oman, Qatar, Kuwait, Bahrain, India, Canada and Singapore articles. Review the actual local roles; do not infer site coverage from a shared company name.
Discuss your evaluation status when enquiring about certification
Give SCS a clear summary of the proposed scope, locations, internal-audit coverage, management-review position and significant outstanding actions. Describe what has been completed and what remains in progress.
Use the ISO 27001 certification page or contact SCS for an assessment enquiry. The applicant's internal evaluation, any implementation assistance and the independent certification decision have different responsibilities and should be kept clear.
Need ISO 27001 Certification for Your Business?
Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.