WikiFrameworksISO/IEC 27001:2022Internal audit programme

Internal audit programme

Updated: 2026-02-18

Plain English Translation

Clause 9.2.2 requires the organization to create a formal 'master schedule' for its audits. Instead of performing random checks, you must establish a structured programme that defines exactly when audits will happen, what specific areas will be checked (scope), how they will be checked (methods), and who will do the checking. Crucially, this schedule should not be arbitrary; it must prioritize areas that are higher risk or have had problems in the past.

Executive Takeaway

Management must authorize a forward-looking audit schedule that prioritizes high-risk areas and ensures all aspects of the ISMS are reviewed over a defined cycle.

ImpactHigh
ComplexityMedium

Why This Matters

  • Ensures that audit resources are focused on the most critical business risks
  • Guarantees that no part of the security system goes unchecked indefinitely
  • Provides a structured mechanism for reporting performance to the board

What “Good” Looks Like

  • An 'Annual Audit Plan' is published and approved by leadership, and tools like WatchDog Security's Compliance Center can help assign audit owners, track planned intervals, and retain the plan as documented information.
  • The schedule is risk-based, meaning critical systems are audited more frequently than low-risk ones
  • Audit results are formally reported to relevant management and the board

It is the requirement to plan, establish, and maintain a structured schedule (programme) for conducting audits, including defining the frequency, methods, responsibilities, planning requirements, and reporting.

Create a document (e.g., spreadsheet or GRC plan) listing all ISMS processes and controls. Assign audit dates based on risk (high risk = more frequent). Define who will audit each area and what criteria (e.g., ISO 27001, internal policy) will be used. WatchDog Security's Compliance Center can help maintain the control inventory, map audits to scope and criteria, and keep the supporting evidence and reports organized by cycle.

The standard requires 'planned intervals.' Most organizations operate on an annual cycle, auditing the entire ISMS once a year, or splitting it into smaller quarterly audits covering different scopes.

The programme must include the frequency of audits, the methods to be used (interviews, sampling), responsibilities (who audits), planning requirements (scope/criteria), and reporting mechanisms.

There is no fixed frequency (e.g., 'monthly'). Frequency should be determined by the importance of the processes concerned and the results of previous audits (e.g., areas with past failures should be audited sooner).

Auditors are responsible for conducting audits objectively and impartially. They must define the scope and criteria for their specific audit and report the results to relevant management.

Map out the calendar year. Ensure critical areas (like User Access or Risk Management) are scheduled. Ensure availability of auditors and auditees. Allow time for remediation before the external certification audit.

Common methods include inquiry (interviews), observation (watching processes), inspection (reviewing documents/logs), and re-performance (testing controls yourself).

Risk-based scheduling gets messy when scope, criteria, owners, and evidence live in different places and change over the year. WatchDog Security's Compliance Center can help by mapping the audit programme to control owners, storing scope and criteria per audit, and highlighting gaps when required inputs or evidence are missing ahead of the planned audit window.

Audit outputs are only useful if you can later prove what was tested, what evidence was examined, and what was reported to management. WatchDog Security's Secure File Sharing can help protect sensitive audit packages with encrypted sharing, access controls, and audit logs, while WatchDog Security's Compliance Center can link finalized reports and evidence to the relevant audit cycle for retrieval during management review.

ISO-27001 9.2.2

"The organization shall plan, establish, implement and maintain an audit programme(s), including the frequency, methods, responsibilities, planning requirements and reporting... The organization shall define the audit criteria and scope for each audit; select auditors and conduct audits that ensure objectivity and the impartiality of the audit process."

VersionDateAuthorDescription
1.0.02026-02-18WatchDog Security GRC TeamInitial publication