Guide IT Management

IT audit readiness: controls, evidence and a checklist

Preparing for an IT audit takes more than gathering policies and documents. You need to show that your controls meet the applicable requirements and operate consistently, which means operational records, clear ownership, periodic reviews and a way of handling nonconformities. This guide explains how to structure evidence, review controls and organise an internal audit programme without relying on last-minute preparation.

17 September 2026
Updated 18 November 2026
10 min read
Key takeaways
  • Audits find three different problems: a control that is missing or badly designed, a control that exists but does not operate effectively, and a control that operates but lacks sufficient evidence
  • Missing records can stop an auditor concluding that a control operated consistently, but auditors also observe, interview, inspect configurations and re-perform controls
  • There is no universal 6 or 12 month evidence period; it depends on the audit type, the applicable requirements and how often each control runs
  • ISO/IEC 27001 clause 9.2 requires an internal audit programme at planned intervals, not a quarterly audit of every control
  • Keep management-system evidence and operational-control evidence apart, and protect the repository that holds them

1. What audits actually find

Not every audit finding is the same kind of problem, and treating every finding as a paperwork issue leads to the wrong fix. Broadly, an audit can find three things.

  • The control is missing or badly designed. There is no access review at all, or the review covers one system out of five. Better documentation will not fix this; the control itself has to change.
  • The control exists but does not operate effectively. A restore test was run and failed, leavers keep their accounts for weeks, or patches are approved but never deployed. This is a control failure, not a documentation gap.
  • The control operates but the evidence is insufficient. Access reviews do happen, but there is no dated record of who reviewed what and what changed as a result.

All three occur in practice, and the mix varies from one organisation to the next. The aim of audit readiness is to know which of the three applies to each control before an auditor does, because each needs a different response: redesign the control, fix how it operates, or improve how evidence is captured.

2. How auditors reach a conclusion

Auditors assess controls against defined audit criteria: the requirements of a standard such as ISO/IEC 27001, a regulation, a contract or a customer questionnaire. Records are an important part of the evidence, but not the only part. Depending on the audit, an auditor may also observe a process, interview the people who run it, inspect system configurations, re-perform a control (for example, checking a sample of leavers against their account status) or ask for a test.

Missing records still matter. Where the criteria require a control to operate consistently over a period, an auditor without records may be unable to conclude that it did, especially for past activity that cannot be observed today. Whether that becomes a finding depends on the criteria and on whether the other available evidence is sufficient. "We do it but never wrote it down" is a weak position rather than an automatic failure, and not one to rely on.

Management-system evidence

For ISO/IEC 27001, clauses 4 to 10 produce their own evidence, separate from the security controls:

  • Scope of the management system and the context analysis behind it (clause 4)
  • Leadership commitment, roles and the information security policy (clause 5)
  • Risk assessment and risk treatment method and results, the Statement of Applicability and security objectives (clause 6)
  • Performance evaluation: monitoring results, internal audit reports and management review records (clause 9)
  • Nonconformities, corrective actions and improvement records (clause 10)

Operational-control evidence

  • Patching and vulnerability management: scan results, deployment reports, approved exceptions
  • Access reviews: dated review records, resulting changes, joiner and leaver records
  • Backup and recovery: job reports plus documented restore tests with results against recovery objectives
  • Incident response: incident log, actions taken, lessons learned
  • Training and awareness: completion records and course content
  • Supplier management: supplier inventory, security assessments, contract clauses

3. How much history you need

There is no general rule that auditors expect 6 or 12 months of evidence. The period depends on the type of audit, the applicable requirements and how often each control runs. A continuous control such as automated patch deployment produces records all the time; a monthly vulnerability scan produces twelve a year; a quarterly access review produces four; an annual restore test or management review may produce one. An auditor sampling a quarterly control needs to see the quarters in the period under review, not an arbitrary number of months.

Keep the records your framework and audit scope require, for as long as a deliberately defined retention policy says. If you are planning for a first audit, starting three to six months ahead is a sensible planning assumption, because it gives monthly and quarterly controls time to run and produce records. It is a planning suggestion, not a requirement of any standard.

Evidence capture works best as part of operational routines. Configure systems to keep the logs and reports you need, export them automatically where possible, and make the control owner responsible for recording the outcome when the control runs. The effort involved depends on the number of controls, systems and owners and on the requirements in scope; no fixed monthly figure applies everywhere. Records produced only during audit preparation, without a history of execution behind them, add little.

4. Build a controlled evidence repository

Evidence scattered across mailboxes and personal drives is slow to produce and hard to trust. A single repository structured by requirement and control, with a named owner for each area, solves that. The repository also needs protecting, because it often holds sensitive material: access lists, network diagrams, vulnerability reports, and personal data in HR or incident records.

  • Access control matched to the sensitivity of what is stored
  • Versioning and change logging, so you can show what changed and when
  • Protection against accidental or deliberate deletion
  • A defined retention period for each type of evidence

Where possible, keep controlled exports from the source system, or references to it (a ticket number, a report generated by the backup console, a link to the review in the identity platform), rather than copying raw data into yet another folder. Avoid unnecessary copies of personal and confidential data, and take particular care with what you share with external auditors and customers: provide what the criteria require, redacted where appropriate, through a controlled channel.

The businesses that pass audits with the least friction are not doing more security work than everyone else. They are simply not throwing away the proof of the work they were already doing.

5. A compact audit-readiness matrix

A simple matrix keeps the three types of finding apart. For each control, record the evidence you expect it to produce and how you will validate that it works, not just that it exists.

ControlExpected evidenceValidation
Access reviewsDated review record per system, reviewer, changes madeSample accounts and confirm that removals were carried out
Backup recoveryBackup job reports and documented restore tests with timingsRestore test against agreed recovery time and recovery point objectives
Vulnerability managementScan results, remediation records, approved exceptionsCompare a recent scan with remediation deadlines
Supplier securitySupplier inventory, assessments, security clauses in contractsCheck that critical suppliers have a current assessment
Management reviewMinutes covering the inputs in ISO/IEC 27001 clause 9.3, decisions and actionsConfirm that actions were assigned and followed up

Give each control a status on a consistent scale:

  • Not implemented. The control does not exist yet.
  • Implemented but unverified. The control is in place, but nobody has checked it.
  • Design verified. The control has been reviewed and is designed to meet the requirement.
  • Operating effectiveness verified. Evidence shows the control worked as intended over the assessment period.
  • Not applicable. Excluded, with the justification recorded (for ISO/IEC 27001, in the Statement of Applicability).

Note the assessment period and the criteria next to each status. "Verified" means little unless the reader knows against what, and over which period.

6. Internal audits, control reviews and certification audits

These terms are often used interchangeably, but they are different things. An external certification audit is carried out by a certification body to decide whether to certify your management system. Conformity assessment is the broader term for any evaluation of whether specified requirements are met, certification included. An internal audit is an audit your organisation conducts, or has conducted on its behalf, of its own management system. A control review is an operational check by a control owner or manager, such as a quarterly review of privileged access.

ISO/IEC 27001:2022 clause 9.2 does not require quarterly audits of every control. It requires internal audits at planned intervals, under an audit programme that sets frequency, methods, responsibilities, planning requirements and reporting, and that takes into account the importance of the processes concerned and the results of previous audits. For each audit the organisation defines the criteria and scope, selects auditors and conducts audits so that objectivity and impartiality are ensured, and reports the results to relevant management. Nonconformities then go through corrective action under clause 10, and audit results are an input to management review under clause 9.3. ISO 19011 provides guidance on managing an audit programme and conducting audits.

Quarterly reviews of critical controls are useful and can form part of the programme, but they are not a formal internal audit. A checklist supports an internal audit; it is not one by itself. The audit needs defined objectives, criteria, scope and methods, an auditor with adequate competence, objectivity and impartiality, and findings that are recorded and followed through to corrective action.

In a small organisation, impartiality is hard because the people who know the controls also run them. External support can help, but hiring a consultant does not automatically guarantee competence or independence: check their experience with the standard and make sure they did not design or operate the controls they are auditing. Our ISO 27001 certification guide shows where the internal audit fits in the wider certification route.

7. Gaps worth checking first

Some gaps come up often enough in SME readiness reviews to be worth checking early: access reviews carried out informally with no dated record, policy review dates that have lapsed, supplier assessments that were started and never finished, and risk assessments written for the first certification and not updated since the environment changed.

Do not overlook restore tests

A missing documented restore test is a serious gap. Successful backup jobs show that data was copied; they do not show that it can be recovered within your recovery objectives. If a restore test was run and failed, that is a control failure to fix, not a paperwork issue. If no test has been run, schedule one, record the result and the time it took, and act on what it shows.


Making audit readiness part of normal operations

Audit readiness holds up best as a standing responsibility rather than a project with a start and end date. It also belongs in the wider IT plan: our guide to building an IT strategy roadmap explains how to schedule control improvements and audit cycles alongside other IT work.

  • Classify each gap as a design gap, an operating failure or an evidence gap, and respond accordingly.
  • Keep management-system evidence and operational-control evidence apart, each with a named owner.
  • Set evidence retention by requirement and control frequency, not by a fixed number of months.
  • Run an internal audit programme at planned intervals with competent, impartial auditors, and follow findings through to corrective action.
  • Protect the evidence repository and share only what the audit criteria require.

Businesses without a dedicated compliance or IT governance function often find this discipline is the first thing to slip when day-to-day pressures take priority. Cyvra's virtual IT manager service maintains audit evidence as a standing responsibility, so readiness does not depend on someone remembering to do it between other priorities.

The ISO/IEC 27001 standard sets out the management system requirements, including internal audit (clause 9.2) and management review (clause 9.3). ISO 19011 gives guidelines for auditing management systems. The National Cyber Security Centre's Cyber Essentials guidance is a useful reference for UK assessments.

Frequently asked questions

What evidence is needed for an IT audit?

It depends on the audit criteria (the standard, regulation, contract or questionnaire you are assessed against) and on the scope. Typical evidence includes approved policies and procedures, records such as access reviews and change approvals, system logs and reports, test results such as restore tests and vulnerability scans, internal audit reports and management review minutes. Auditors may also interview staff, observe processes and inspect configurations.

Does ISO 27001 require quarterly internal audits?

No. Clause 9.2 of ISO/IEC 27001:2022 requires internal audits at planned intervals, under an audit programme that defines frequency, methods, responsibilities and reporting and considers the importance of the processes and the results of previous audits. Each audit needs defined criteria and scope, auditors selected to ensure objectivity and impartiality, and results reported to management. Quarterly control reviews can complement the programme but do not replace it.

How much history do you need to show?

There is no universal 6 or 12 month requirement. It depends on the audit type, the scope and criteria, and how often each control operates. A quarterly control needs records for the quarters in the period under review; an annual control may have a single record. Keep the records your framework requires, under a defined retention policy.

Do we need audit readiness even if we are not pursuing a formal certification?

Yes. Client due diligence questionnaires, cyber insurance renewals and vendor security assessments often ask for similar evidence to a certification audit. Businesses that keep their evidence organised can answer these requests much faster, whether or not they hold a certification.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Talk to Cyvra

Audit coming up and not sure your evidence will hold up?

We help businesses in the Netherlands and UK build and maintain audit-ready evidence year-round, not just before a deadline.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content. Readers should seek independent advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.