ISO 27001 Internal Audit Program: Planning, Frequency and Independence

The ISO 27001 internal audit program: clause 9.2, risk-based frequency, a sample three-year program, process-based auditing, auditor independence in a small company and outsourcing.
Technical summary
Technology
ISO/IEC 27001:2022, ISO 19011:2018, ISO/IEC 27007
Topic
Designing and managing a multi-year internal audit program
Level
Intermediate
Prerequisites
  • An approved SoA and risk assessment
  • The people who will act as internal auditors have been identified
In this article7 sections

A one-off round with a checklist three weeks before the certification audit isn’t an internal audit. The auditor can tell from the program’s date, the narrowness of the sample and the findings all being missing documents. Internal audit is the mechanism by which the ISMS tests itself, and it needs a multi-year program to work. Below we explain how to set up such a program under ISO 27001 clause 9.2, how to prioritize processes and controls, how to ensure auditor independence in small organizations and how to measure the program’s effectiveness.

The difference between an audit program and an audit plan

ISO/IEC 27001:2022 clause 9.2 covers internal audit in two sub-clauses. 9.2.1 requires audits at planned intervals of whether the ISMS conforms to the organization’s own requirements and the requirements of the standard, and whether it’s effectively implemented and maintained. 9.2.2 requires an internal audit program to be planned, established, implemented and maintained; the program covers frequency, methods, responsibilities, planning requirements and reporting.

The management systems auditing guideline ISO 19011:2018 distinguishes two concepts: an audit program is the arrangements for one or more audits planned for a specific time frame and directed towards a specific purpose; an audit plan describes the activities and arrangements for a single audit. The two are constantly confused.

Feature Audit program Audit plan
Time horizon One or several years A single audit (days/weeks)
Owner ISMS manager or program manager Lead auditor
Content Which process/control, how often, who, with what method Scope, criteria, agenda, people to interview, sample
Input Risk, previous findings, changes Program, previous audit report, document review
Evidence Approved program, revision history Plan, checklist, report

Clause 9.2.2 also requires the criteria and scope of each audit to be defined, the results to be reported to relevant management and documented information to be kept as evidence that the program has been implemented. So it’s not just the report; the program itself is evidence too. An unapproved program isn’t a program.

The inputs that shape the program: risk, previous findings, changes

The standard requires the importance of the processes concerned and the results of previous audits to be taken into account when establishing the program. In practice, you can score each process or control group on these four inputs and set the audit frequency accordingly:

  • Risk level: How much the process reduces high risks. Access management, backup and change management usually come at the top.
  • Previous findings: Open or recently closed nonconformities require a re-audit to confirm the corrective action really works.
  • Changes: A new system, a new supplier, an organizational change or a move to the cloud.
  • Incidents and external inputs: Security incidents, customer complaints, external audit observations.

Know one constraint from the start: prioritization allows some areas to be audited infrequently, not never. Although the standard doesn’t write it as a cycle, 9.2.1 requires the conformity of the ISMS as a whole to be audited; certification bodies also expect the program to cover all of clauses 4–10 and all Annex A controls marked applicable in the SoA over the certification cycle. Auditing the management system clauses (context, leadership, risk assessment, management review, corrective action) every year is common and recommended practice. It’s also expected that an internal audit and management review have been carried out at least once before the Stage 2 certification audit.

Sample multi-year program

The table below is a fictional example prepared for a three-year certification cycle. “A” stands for an annual audit, “D” for an in-depth audit (with an enlarged sample) and “F” for a focused follow-up audit.

Field Year 1 Year 2 Year 3
Clauses 4–10 (management system) Y Y Y
Access and identity management (5.15–5.18, 8.2, 8.5) D Y D
Backup and continuity (8.13, 5.29, 5.30) D Y Y
Change and patch management (8.8, 8.32) Y D Y
Suppliers and cloud (5.19–5.23) Y D T
Human resources (6.1–6.6) Y — D
Physical security (7.1–7.14) Y — Y
Incident management (5.24–5.28) Y Y D
Follow-up of previous year’s findings — T T

The program can also be carried out with several small audits spread over the year instead of one big audit. A process-based approach works better: tracing the “joiner–leaver” process from start to finish tests several Annex A controls in a single audit and produces more realistic findings than an audit that goes clause by clause. Example: pick five people from HR’s leavers list and check when their accounts were disabled in Active Directory, whether their VPN and cloud application accounts were closed, and the return record for their assigned laptop. A place you may get caught out is a user whose AD account was closed but whose SaaS account stayed open. How to choose the sample is explained in the guide sampling in internal audits.

Internal auditor competence and independence

Clause 9.2.2 requires auditors to be selected and audits to be conducted in a way that ensures objectivity and impartiality. Clause 7.2 also requires the competence of those doing work that affects ISMS performance to be determined and evidenced; internal auditors fall within this.

Competences expected of an internal auditor:

  • Being able to interpret ISO 27001 requirements and Annex A controls
  • Audit technique based on ISO 19011: interviewing, record review, sampling, observation
  • A technical grounding in the area audited (for example, being able to read Active Directory or backup software reports)
  • Being able to write a finding with criteria, evidence and impact

Don’t underestimate the technical grounding item. An auditor who looks only at the “last job successful” line in the backup console can’t see that no full backup has been taken for weeks, or that a server has dropped out of the job definition. A training certificate alone isn’t enough as evidence of competence; audits done under supervision and the quality of reports are also assessed.

Independence in small organizations

There’s one basic rule: an auditor doesn’t audit their own work. In a company where the IT team is two or three people, this rule is met in these ways:

  • Cross-auditing: A trained employee from quality or HR audits IT processes, and an IT employee audits HR and physical security processes.
  • Auditing the management system clauses separately: The ISMS manager doesn’t audit the risk methodology and management review records they wrote themselves; someone else or an external resource audits these clauses.
  • Group company support: Reciprocal auditing with an auditor from another company in the same group.
  • Outsourcing: For areas where independence can’t be ensured internally.

The method used to ensure independence must be written in the program. Assigning auditors without justification raises a question of objectivity.

Outsourced internal audit

Outsourcing all or part of internal audit isn’t contrary to the standard. Points to watch:

  1. Ownership of the program stays with the organization. The external auditor carries out the audit; the program’s scope, frequency and follow-up of results remain the organization’s responsibility.
  2. Consulting and auditing must be kept separate. A consultant who set up the ISMS or wrote its documents auditing those same documents is an objectivity problem.
  3. Confidentiality and access: The access to be given to the external auditor, the confidentiality agreement and how evidence will be shared must be defined. The auditor isn’t given domain admin rights; read-only reports and screen sharing are usually enough.
  4. Knowledge transfer: The report shouldn’t be just a list of findings; it should also include how each control was tested, so the same method can be repeated in the next audit.

For how to define outsourced deliverables, see the guide outsourced ISMS consulting.

Reviewing the program’s effectiveness

Audits may have been done and the program can still be ineffective. ISO 19011 recommends monitoring and reviewing the program; from an ISO 27001 perspective, the program’s results go into management review as the “audit results” input. Review the program once a year with these questions:

  • Were all planned audits done on time? Is the justification for postponed ones recorded?
  • Will the program cover all clauses and applicable controls by the end of the cycle?
  • Do the findings show real problems, or just missing documents? Did the external audit find anything the internal audit missed?
  • Were findings closed on time, and was the effectiveness of corrective actions verified?
  • Were the auditors’ competence and independence sufficient?

A nonconformity found in the external audit that the internal audit never saw is the clearest sign of weakness in the program. In that case, revisit the sample size, audit duration and choice of auditors. For how to write findings, see writing audit findings; for how to take them to the review meeting, the management review guide shows the way.

If you’d like internal audit carried out by an independent team, see our ISO 27001 internal audit and corrective action management service; to run the program throughout the year, our ongoing ISMS consulting service. The primary source for auditing principles is the ISO 19011:2018 guideline.

Frequently asked questions

How many times a year should an internal audit be done?

The standard doesn’t give a fixed frequency; frequency is set in the program according to the importance of processes and the results of previous audits. A common practice is to audit the management system clauses every year and to cover all applicable controls within the certification cycle.

Is it mandatory to audit all Annex A controls every year?

It isn’t mandatory. In a risk-based program, controls can be audited at different frequencies; however, certification bodies commonly expect all controls marked applicable in the SoA to be audited at least once within the certification cycle.

Can the ISMS manager do the internal audit themselves?

They can audit other processes, provided they don’t audit areas within their own responsibility. Clauses they run themselves, such as the risk methodology, management review and document control, must be audited by another employee or an external auditor.

What’s the difference between ISO 27007 and ISO 19011?

ISO 19011 is the general auditing guideline for all management systems. ISO/IEC 27007, building on ISO 19011, provides additional guidance specific to auditing information security management systems.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles