Layots Logo
Cybersecurity

ISO 27001 Gap Assessment — What evidence to prepare before the first review

What evidence to prepare before the first review for enterprise IT and procurement teams evaluating iso 27001 gap assessment.

Layots Editor
Layots Technologies
Share
ISO 27001 Gap Assessment — What evidence to prepare before the first review

Short answer: An ISO 27001 gap assessment compares what your organisation actually does against what ISO/IEC 27001:2022 requires, and produces a prioritised list of what is missing. Before the first review, prepare three things: your scope and asset inventory, the mandatory documented information the standard requires, and operational evidence from the last three to six months — access reviews, incident records, backup and recovery tests, supplier assessments and training records. Policies alone will not pass; auditors look for records that the controls ran.

Key takeaways

  • A gap assessment is not an audit. It is the honest inventory you do before the audit, with no certificate at stake.

  • The standard has two halves: clauses 4 to 10 (the management system) and Annex A (93 controls in four themes).

  • Auditors test evidence, not intent. A policy without records is a finding.

  • Most gaps sit in the same places: asset inventory, access reviews, supplier security, logging and backup testing.

  • Six months of operating evidence is usually the practical minimum before a Stage 2 audit.
  • What is an ISO 27001 gap assessment?

    A gap assessment is a structured review of your current information security practices against every requirement of ISO/IEC 27001:2022. It produces a control-by-control status (in place, partial, missing, not applicable), the evidence seen, the risk of leaving each gap open, and an owner plus a target date for closing it. Done properly it becomes your certification project plan.

    It is deliberately different from a certification audit. There is no certificate at risk, so people can say "we do not do that" without consequence — which is the only way the exercise produces a useful plan.

    What the standard actually asks for

    ISO/IEC 27001:2022 has two parts, and both are audited:

  • Clauses 4 to 10 — the management system. Context and interested parties, leadership and policy, risk assessment and treatment, objectives, competence and awareness, operation, monitoring and measurement, internal audit, management review, and corrective action.

  • Annex A — 93 controls in four themes: Organizational (37), People (8), Physical (14) and Technological (34). You select the applicable controls through your risk treatment and justify every inclusion and exclusion in the Statement of Applicability.
  • Organisations usually prepare well for Annex A and underprepare for the clauses. In practice, missing internal audits, management reviews and corrective action records are among the most common reasons a Stage 2 audit goes badly.

    Mandatory documented information to have ready

  • ISMS scope statement — What auditors look for: Sites, services, systems and exclusions, written and justified

  • Information security policy — What auditors look for: Approved by top management, communicated, with a review date

  • Risk assessment process and results — What auditors look for: A repeatable method, a populated risk register with owners

  • Risk treatment plan — What auditors look for: Decisions, owners, target dates, and current status

  • Statement of Applicability — What auditors look for: Every Annex A control with applicability and justification

  • Security objectives — What auditors look for: Measurable, with how and when they are measured

  • Evidence of competence — What auditors look for: Role requirements, training records, awareness completion

  • Monitoring and measurement results — What auditors look for: What you measure, the data, and what was done about it

  • Internal audit programme and reports — What auditors look for: A full cycle completed, findings tracked to closure

  • Management review minutes — What auditors look for: Agenda items per the standard, decisions and actions

  • Nonconformity and corrective action records — What auditors look for: Root cause, correction, verification of effectiveness
  • Operational evidence to collect before the first review

    This is where most gap assessments spend their time. Pull the last three to six months of:

  • Asset inventory for hardware, software, cloud services and information assets, with owners and classification.

  • Access control records: joiner, mover and leaver tickets, periodic access reviews with sign-off, privileged account list, and MFA coverage.

  • Change management records showing approval, testing and rollback for significant changes.

  • Patch and vulnerability evidence, including the latest VAPT report and the remediation and retest trail.

  • Logging and monitoring evidence: which sources are collected, retention, who reviews alerts, and sample investigations. See EDR and Managed SOC for the response side of this.

  • Backup and recovery tests, with timed results. A disaster recovery drill log is strong evidence here.

  • Incident records, including minor ones, with classification, timeline, resolution and lessons learned.

  • Supplier security records: due diligence, security clauses in contracts, and a register of who processes what data.

  • Physical security records: access logs, visitor records, server room controls, CCTV retention.

  • Awareness training records and phishing simulation results.

  • Business continuity documentation with the last test result.
  • How the certification audit is structured

    Certification happens in two stages. Stage 1 is a documentation and readiness review: the auditor checks scope, policies, the Statement of Applicability, the risk work and whether the management system exists at all. Stage 2 tests whether the ISMS actually operates, by sampling records against the controls you declared applicable. Surveillance audits then follow annually, with recertification in the third year.

    This is why evidence duration matters. A control approved last week has nothing to sample. Plan for a period of genuine operation — commonly three to six months — between closing gaps and booking Stage 2.

    A workable preparation sequence

  • Define scope and confirm it with management. Narrow, defensible scope beats an ambitious one.

  • Run the gap assessment across clauses 4 to 10 and all 93 Annex A controls.

  • Complete the risk assessment and derive the Statement of Applicability from it, not the other way around.

  • Close the high-risk gaps with named owners and dates.

  • Operate and collect evidence for three to six months.

  • Run a full internal audit and a management review, and close the findings they raise.

  • Book Stage 1, fix what it raises, then Stage 2.
  • Common gaps found in first assessments

  • An asset inventory that does not include cloud services and SaaS accounts.

  • Access reviews that are discussed but never evidenced with a signed record.

  • A Statement of Applicability written independently of the risk register.

  • Supplier security handled by procurement with no security review and no register.

  • Logs collected but never reviewed, with no record of any investigation.

  • Backups running but never restore-tested.

  • Internal audit skipped, or performed by the person who owns the controls being audited.

  • Management review minutes missing the inputs the standard specifically requires.

  • Incident records kept only for major incidents, so there is nothing to sample.
  • ISO 27001 and India's DPDP Act

    The two are different obligations, but much of the evidence overlaps. The ISMS gives you asset ownership, access control, logging, incident response, supplier management and retention practices — all of which a DPDP accountability review will also ask for. Running the gap assessment with both in mind avoids doing the same work twice. If you also build or sell AI systems, ISO/IEC 42001 extends the same management-system pattern to AI governance.

    Frequently asked questions

    How long does an ISO 27001 gap assessment take?
    For a single-site organisation of moderate complexity, typically one to three weeks of assessment work including interviews, document review and evidence sampling, followed by a prioritised report.

    How long until we can be certified?
    Commonly three to nine months from gap assessment to Stage 2, depending on how many gaps exist and how quickly evidence can accumulate. The constraint is usually evidence duration, not effort.

    Do we need a consultant and a separate auditor?
    Yes, they are different roles. The certification body must be independent; a consultant who implements your ISMS cannot certify it. Plan for both in your budget.

    Can we limit the scope to one business unit?
    Yes, if the scope is coherent and defensible, with clear boundaries and interfaces. Customers may ask what is excluded, so make the scope statement something you are comfortable sharing.

    What is the difference between ISO 27001 and SOC 2?
    ISO 27001 certifies a management system against an international standard. SOC 2 is an attestation report against trust services criteria, more common with US customers. Many organisations end up doing both, reusing the same evidence.

    Does cloud hosting reduce our control burden?
    It shifts responsibility, it does not remove it. You still own configuration, access, monitoring, data classification and supplier assurance for the cloud provider itself.

    What is the single biggest cause of audit findings?
    Missing records. The control exists and people follow it, but nothing is written down, so the auditor cannot sample it.

    Prepare for ISO 27001 with Layots

    Layots Technologies runs ISO 27001 gap assessments and readiness programmes for businesses in Chennai, Bangalore and Hyderabad: scope definition, control-by-control assessment, risk register and Statement of Applicability support, evidence design, technical remediation across identity, endpoint, network and backup, and internal audit support before you book Stage 2.

    Tell us your intended scope and target certification date. A consultant reviews the requirement and comes back with an assessment plan and a costed recommendation, usually within one business day.

  • Book a 30-minute virtual meeting with a consultant — request your free IT assessment

  • Call +91 99623 95939

  • WhatsApp the team for a quick requirement discussion
  • Related reading: ISO/IEC 27001 explained · Cybersecurity Assessment in Chennai · VAPT Services in Chennai

    Ready to transform your IT?

    Speak with a Layots enterprise architect. Assessment, no obligation.

    Request IT Assessment →
    Free assessment

    Talk to Our Specialists

    Found this useful? Our architects can apply the same thinking to your environment.

    • A solution architect reviews your requirement
    • We respond, usually within one business day
    • You get a practical, costed recommendation

    Prefer to talk now?

    No obligation. By submitting, you agree to our Privacy Policy. We never sell your information.