ISO/IEC 27001:2022 · IMPLEMENTATION & CERTIFICATION READINESS

Certify once. Then reuse the evidence for everything you get asked for next.

Infosecurix runs first-time ISO/IEC 27001:2022 implementations on an AI-augmented method and a 139-artifact management system library, already proven through a live certification. We build the ISMS so it holds SOC 2, DORA, NIS2, PCI DSS, the CRA and the ISO extensions on the same controls and the same evidence repository — instead of three parallel compliance programmes.

Fixed 10-phase plan · 204 activities · Stage 2 audit target from week 12

Control Reuse — Indicative

Choose a framework to discover what your ISO 27001 implementation already encompasses.

ISO/IEC 27001:2022SOC 2 Type 2PCI DSS V4.0.1NIS2

Clause 6.1

Risk assessment & treatment

Clause 9.2–9.3

Internal audit & management review

A. 5. 15

Access control

A.5.19–A.5.22

Supplier & ICT third-party risk

A.5.24–A.5.26

Incident management & reporting

A.5.29–A.5.30

Continuity & ICT readiness

A. 8. 8

Vulnerability & patch management

A.8.15–A.8.16

Logging & monitoring

++

139

ISMS artifacts in the library — policies, procedures, registers, records

93

Annex A controls assessed, justified and mapped in your Statement of Applicability

9

Phases from engagement initiation to certificate issuance and handover

2+1

Implementation consultants, plus an independent internal auditor for Clause 9.2

++

ISO/IEC 27001:2022 · IMPLEMENTATION & CERTIFICATION READINESS

Most failed ISO 27001 projects don't fail the audit. They fail before it.

We've seen the same three patterns in organisations attempting their first certification. Each one is a scoping and sequencing problem, not a security problem.

PATTERN 01

A template pack, not a management system

Downloaded policies get adopted without a risk assessment behind them, so the Statement of Applicability can't be justified and Stage 1 stops at documentation review.

PATTERN 02

No evidence window planned

The audit date is booked before controls have produced evidence of real operation. Access reviews, recovery tests, internal audits and management reviews are left too late, so readiness depends on last-minute activity rather than a planned evidence cycle.

PATTERN 03

Built for one certificate only

Six months later a customer asks for SOC 2, or NIS2 lands in scope, and the work restarts from zero because nothing was mapped or structured for reuse.

++

THE METHOD

Ten phases, 204 activities, a named owner on every one.

The plan is not written from scratch for your engagement. It is a proven delivery template, tailored to your scope in Phase 0 and handed to you as a working project plan with a full work breakdown structure, RACI and artifact register.

  1. P0

    Engagement initiation

    Scope boundaries, stakeholders, plan tailoring, tooling and evidence repository stood up.

  2. P1

    Gap analysis & scope definition

    Clause 4–10 and Annex A gap assessment, ISMS scope statement, and your multi-framework mapping baseline.

  3. P2

    Risk & applicability foundation

    Risk methodology, asset and risk register, risk treatment plan, Statement of Applicability with justifications.

  4. P3

    Management system build

    Clause 4–10 documentation: policy, roles, objectives, competence, communication, documented information, performance evaluation.

  5. P4

    Annex A controls implementation

    Organisational, people, physical and technological controls. Runs in parallel with P3 via plan predecessors, not after it.

  6. P5

    Internal audit & management review

    Full-scope internal audit by an auditor independent of the implementation team, then a minuted management review with decisions and actions.

  7. P6 - MILESTONE

    Stage 1 audit — from week 6

    Documentation readiness review by your certification body, inside the operational evidence window.

  8. P7 - MILESTONE

    Stage 2 audit — from week 12

    Effectiveness audit. The window exists so records have real operating history behind them by this date.

  9. P8

    Certificate issuance & closeout

    Nonconformity response, corrective action closure, lessons learned, handover of the complete ISMS to your owners.

  10. P9

    Transition to fractional ISO maintenance

    Surveillance-audit calendar, recurring obligations and an optional retained ISO to keep the system running.

++
++

AI-AUGMENTED, HUMAN-ACCOUNTABLE

The AI removes the drafting work. It does not sign your Statement of Applicability.

Auditors are entitled to ask how your documentation was produced, and increasingly do. Here is the line we hold on every engagement, and the line you can state to your certification body without hesitation.

Isometric illustration of a balance scale representing technical controls

WHERE AI ACCELERATES

Volume, consistency and cross-referencing

  • Tailoring the 139-artifact library to your entity, scope, terminology and org structure
  • Drafting control descriptions and procedure text against your actual environment
  • Building and maintaining clause-to-clause mappings across all in-scope frameworks
  • Consistency checks — terminology, cross-references, document control metadata, orphaned controls
  • Gap analysis first passes and evidence-request lists
Isometric illustration of a segmented pie chart with a person icon representing one framework, multiple standards

WHERE PEOPLE ARE ACCOUNTABLE

Judgement, risk decisions and attestation

  • Risk acceptance, risk ownership and treatment decisions — yours, formally recorded
  • Statement of Applicability inclusion and exclusion justifications, reviewed control by control
  • Internal audit under Clause 9.2, performed by an auditor independent of the build
  • Management review inputs, outputs and decisions
  • Every artifact reviewed and approved by a named consultant before it enters your ISMS
++

ONE MANAGEMENT SYSTEM

ISO 27001 is the spine. The other frameworks bolt onto it.

A unified ISMS means one control set, one risk register, one evidence repository and one audit calendar — with a mapping layer that tells you, for any control, which obligations it satisfies and which auditor will ask for it. You collect evidence once and present it many times.

Isometric illustration of an audit checklist, evidence stacks and reviewers representing a central evidence repository

CENTRAL EVIDENCE REPOSITORY

One record, many audits

Access reviews, vulnerability scans, incident records, supplier assessments and training logs are stored once, versioned, with owner and review date. Each is tagged to every obligation it satisfies, so an auditor request resolves to an existing artifact rather than a fire drill.

Isometric illustration of a dashboard window with charts and a person icon representing certifiable extensions on the same ISMS

Certifiable extensions on the same ISMS

  • ISO/IEC 27701 — privacy information management, extending your ISO 27001 scope to PII controller and processor obligations alongside GDPR work
  • ISO 22301 — business continuity management, reusing your continuity and ICT readiness controls as a certifiable BCMS
  • ISO/IEC 20000-1 — service management, sharing Clause 4–10 structure, document control and improvement machinery with the ISMS

Harmonised structure means Clauses 4–10 are largely common. The incremental effort is the discipline-specific content, not a second management system.

Isometric illustration of a certificate with shields, a checklist and a bank stack representing attestations and regulatory obligations

Attestations and regulatory obligations it feeds

  • SOC 2 Type II — an auditor-issued attestation, not a certification. Your ISO controls supply most Trust Services Criteria evidence; the observation period is planned into the same calendar
  • PCI DSS v4.0.1 — validated against cardholder data environment scope. Shared control ground on access, logging, vulnerability management and third parties
  • NIS2 — transposed national law for in-scope essential and important entities. Article 21 measures and Article 23 reporting duties map to your existing controls and incident procedure
  • DORA — for EU financial entities and their critical ICT providers. ICT risk management, incident classification and reporting, resilience testing, third-party register
  • Cyber Resilience Act — product-side obligations for products with digital elements: secure development, vulnerability handling and coordinated disclosure, actively exploited vulnerability reporting

Applicability is confirmed in Phase 1. Where an obligation does not apply to you, we say so and drop it from the plan rather than selling scope you don't need.

++
++

WHAT YOU RECEIVE

A working management system you own, not a consultant's document set.

Every artifact in the library carries a tailoring tier, so you can see exactly where our effort goes and where yours is needed. Nothing is delivered as a placeholder with your logo on it.

TIER 01

98artifacts · light review

Stable structural documents. Branding, scope references and approvals confirmed, then adopted. Roughly two hours each.

TIER 02

21artifacts · substantive tailoring

Documents that must reflect how you actually operate — procedures, control descriptions, role assignments. Roughly six hours each.

TIER 03

20artifacts · population required

Registers and records only your organisation can fill: assets, risks, suppliers, legal obligations, evidence. Roughly 24 hours each, with us facilitating

++
Isometric illustration of an arch and a sphere on steps representing the system handed over at closeout

  • Complete ISMS document set under your document control, in your repository
  • Statement of Applicability with justifications for all 93 Annex A controls
  • Risk register, risk treatment plan and asset inventory, populated
  • Internal audit programme, report and corrective action log
  • Management review minutes and decision record
  • Multi-framework control mapping matrix, maintained and versioned
  • Project plan with 204 activities, RACI and artifact register as a live tracker

++

PROVEN, NOT THEORETICAL

The library, the phase model and the tiering all came out of a real ISO/IEC 27001:2022 build that went through certification — then were turned into a template so the next client doesn't pay for the learning curve.

WHAT CARRIED OVER

139 artifacts, already audit-tested

The management system library was built and certified against ISO/IEC 27001:2022 in a live engagement, including the 2022 Annex A control structure. It arrives at your project having already survived an external auditor, which is a materially different starting position from a template marketplace download.

The ten-phase plan, the RACI, the artifact tiering and the evidence mapping are all derived from that delivery.

++
++

BEFORE YOU BOOK

The questions we get on the first call.

How long does a first certification actually take?

Our plan targets the Stage 1 audit from around week 6 and Stage 2 from around week 12, with both sitting as milestones inside the operational evidence window. That is achievable for a contained scope with responsive stakeholders. Broad scope, multiple entities, thin internal capacity or a certification body with limited availability all move the date, and we will tell you which of those applies to you in Phase 0 rather than after signature.

Can you guarantee we pass?

No consultant can guarantee an independent certification decision. We prepare your organisation through a scoped implementation plan, working controls, internal audit, management review and evidence-based readiness checks. If gaps remain, we identify them and agree corrective action before recommending progression. The certification body makes the final decision.

Will an auditor object to AI-assisted documentation?

AI assistance does not replace the need for accurate, approved documentation that reflects how your organisation operates. We use AI to accelerate drafting, tailoring and consistency checks, with human review before documents enter your ISMS. Your team remains accountable for risk decisions, approvals and control operation. The important question is whether you can demonstrate that the system works—not simply how its documents were drafted.

Should we add the other frameworks now or later?

Identify relevant obligations at the start, then sequence implementation around your business priorities. If a customer, contract or regulation already requires another framework, include its requirements in the initial scope. Where additional frameworks are a future possibility, structure the controls and evidence for reuse without implementing unnecessary scope. Shared evidence reduces duplication, but each framework still needs its own applicability assessment and any additional requirements addressed.

Do we need our own security team first?

You do not need a large dedicated security team, but you do need an executive sponsor and people with the time and authority to own the relevant processes. We provide implementation expertise and help establish responsibilities across management, IT, HR, procurement and other functions. Your organisation retains ownership of its risks and controls. During scoping, we assess available capacity and identify where additional support is needed.

What happens after the certificate?

The ISMS becomes an ongoing operating responsibility. Control owners continue their activities, maintain evidence, review risks and suppliers, investigate incidents and track corrective actions. Internal audits, management reviews and certification-body surveillance remain part of the programme. At handover, we establish ownership and a recurring activity calendar. Optional fractional information security officer support can help maintain the system and coordinate future framework additions.

Who will be doing the work?

Your engagement has named implementation consultants, defined responsibilities and an internal auditor independent of the implementation work. We agree the delivery team and your organisation’s required participation before work starts. Consultants support implementation and readiness; your management and process owners make approvals and operate the controls. The external certification audit is performed separately by your chosen certification body.

++
++

[PROVEN, NOT THEORETICAL]

A 30-minute scoping call. No deck.

A unified ISMS means one control set, one risk register, one evidence repository and one audit calendar — with a mapping layer that tells you, for any control, which obligations it satisfies and which auditor will ask for it. You collect evidence once and present it many times.

An honest read on your scope and timeline
Which of the eight adjacent frameworks actually apply to you
Where your existing controls already earn credit
A tailored 10-phase outline and indicative effort, sent afterwards

Request a scoping call

We reply within one business day