ISO Standards

ISO 27001 Internal Audit Checklist for Your ISMS

ISO 27001 Internal Audit Checklist for Your ISMS
In short

An ISO 27001 internal audit checks that your ISMS meets the standard and your own rules, and that it works in practice. Plan an audit programme, use an independent and competent auditor, check each clause and the Annex A controls you apply, record findings with evidence, and track corrective actions. Report results to top management.

In this article
  1. How do you plan with an ISO 27001 internal audit checklist?
  2. What should the checklist cover?
  3. How do you check the Annex A controls?
  4. How do you record findings and follow up?
  5. Frequently asked questions

An ISO 27001 internal audit checklist helps you check your own system before the certification body does. ISO/IEC 27001:2022 requires internal audits at planned intervals. They show whether your information security management system (ISMS) meets the standard and your own requirements, and whether it is effectively kept up.

Many companies treat the internal audit as a formality and then meet the same findings at the external audit. A good internal audit does the opposite. It finds weak points while you still have time to fix them. This article gives you a practical checklist and a simple method.

How do you plan with an ISO 27001 internal audit checklist?#

Planning decides how useful the audit will be. Start with these points.

  1. Create an audit programme that covers the whole ISMS over a set period, with more focus on higher-risk areas and past problem areas.
  2. Choose auditors who are competent and impartial. Nobody should audit their own work.
  3. Define the scope, criteria and dates for each audit.
  4. Tell the people being audited what to expect and which records to prepare.
  5. Decide how you will record evidence and findings.

If you have no one suitable, consider internal auditor training or outside support. See our ISO 27001 consulting in India for how we can help.

A risk-based programme is more useful than a rotating calendar. If a department had many incidents last year, or if a process changed recently, audit it sooner and in more depth. Areas that have run well for years can be sampled lightly. Write the reasons for your choices in the programme, so the certification body can see the logic.

What should the checklist cover?#

Use the headings of the standard as your frame, then add the Annex A controls from your Statement of Applicability. Check the exact requirements in your copy of ISO/IEC 27001:2022.

AreaQuestions to ask
Context and scopeAre interested parties and their requirements identified? Is the scope clear and current?
LeadershipIs the policy approved and communicated? Are roles and responsibilities assigned?
Risk assessment and treatmentIs the method followed? Are risks owned and treated? Is the SoA consistent with the plan?
ObjectivesAre objectives set, measured and reviewed?
SupportIs competence shown? Do staff know the policy? Are documents controlled?
OperationAre planned controls working and are changes managed?
Performance evaluationIs monitoring done, the audit programme followed and management review held?
ImprovementAre nonconformities recorded, corrected and checked for cause?

Do not treat the checklist as a script. It is a prompt for good questions. If an answer raises a concern, follow it further, ask for another sample and look for the cause. Good auditors listen as much as they check, and they note what works well, not only what fails.

How do you check the Annex A controls?#

For each control marked as applicable in your Statement of Applicability, ask three things: is it defined, is it done and is there evidence. Sample the records rather than reading everything. For example:

  • Access control: check a sample of new joiners, leavers and access reviews.
  • Supplier security: check contracts, reviews and any incidents with suppliers.
  • Incident management: check the log and how recent incidents were handled.
  • Backup and recovery: check logs and evidence of a restore test.
  • Awareness: check training records and ask staff simple questions.
  • Physical security: walk through the premises and observe real practice.

Talk to the people who do the work, not only the managers. Their answers show whether the written procedure matches reality, which is what an external auditor will test.

Include a review of the previous audit's findings. Auditors often find that last year's corrective actions were closed on paper but the problem came back. Checking that the fix lasted shows maturity, and it is exactly what an external auditor will ask about at a surveillance audit.

How do you record findings and follow up?#

Write each finding clearly: what you saw, what the requirement was and what evidence you have. Classify findings by their seriousness, using the terms your organisation has defined. Each nonconformity needs a corrective action, an owner, a due date and a check that the action worked.

  1. Hold a closing meeting to agree the facts.
  2. Issue a short audit report to the owner and top management.
  3. Track corrective actions to closure.
  4. Feed the results into the management review.
  5. Keep the programme, reports and action records as evidence.

Templates make this easier. Our ISO 27001 toolkit includes editable audit templates and a gap assessment checklist, with one year of e-mail support and a free upgrade within 6 months. Adapt them to your own scope and controls. The internal audit does not guarantee a certification result, but it greatly improves your readiness.

One last tip: do not wait until the week before the external audit. Run the internal audit early enough to fix findings, retest them and then hold the management review. Certification bodies will ask for the audit records and the management review minutes.

Keep the tone constructive. The purpose of the audit is improvement, not blame. When people see that findings lead to practical help, they share problems early, and your system becomes stronger before the external audit arrives.

Finally, give the audit enough time. Rushing a one-day audit across many areas produces thin results. It is better to audit fewer areas properly than to touch everything lightly, as long as the programme covers the whole system over time.

Frequently asked questions#

Who can perform the internal audit?#

Anyone competent and independent of the area being audited. This can be an employee from another team or an outside auditor.

How often should we audit?#

At planned intervals, with the whole ISMS covered over the programme period. Many organisations audit at least once a year, and more often for high-risk areas.

Do we need to audit every control every time?#

No. Plan a programme that covers all of the system over time, and sample within each area.

For the wider picture, read our complete guide to ISO 27001 or contact AdWiser for help.

Found this useful?

Share it with your network, and follow AdWiser Enterprise Consulting on LinkedIn for more certification guides and compliance tips.

Share:

Leave a Comment

Comments are reviewed before they appear. Please keep them relevant and leave out web links.

Ready to put this into practice?

Start with the ISO 27001:2022 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp