FRAMEWORKS & COMPLIANCE

Framework requirements,
connected to the work behind them.

Bring requirements, owners, assessments and evidence into a shared workspace. Defensiq helps your team record what applies, see what needs attention and follow work through to review.

Use available framework content as a starting point, then document the decisions and supporting records that reflect your organisation.

14-day trial of the GRC platform

Search assets, policies, risks…Defensiq GRCAE
Back to Frameworks

ISO 27001:2022

Version 2022+Amd1:2024

Framework scope

Information security for our people, services and supporting systems.

Assessment96 / 123 reviewed
Implementation78 implemented
Assurance12 reviews due
Attention18 gaps

Requirements

Annex A controlsManagement clauses
All applicableMy workNeeds attention
Illustrative ISO 27001 requirement assessments
RequirementImplementationStatusAssignee
5.1Policies for information securityImplementedTaylor
5.3Segregation of dutiesIn progressMorgan
5.15Access controlImplementedAlex
Access control · Evidence addedQuarterly access review · Alex Example · Awaiting review
Example organisationSample workspace · October 2026
Recreated from Defensiq · Illustrative sample data

THREE PARTS OF A CLEAR ASSESSMENT

Scope it. Do the work.
Record the review.

A control can be implemented while its evidence still needs review. Keep each decision visible.

01

Decide what applies before measuring progress

Select an available framework for your project and review its scope. Record why a requirement applies, why it does not, or how an alternative or inherited measure addresses it.

Set the scope for your ISO 27001 or NIS2 requirements, and keep each decision with its assessment so owners and reviewers can see the reasoning.

02

See the difference between work completed and work reviewed

A control can be implemented while its evidence still needs review. Defensiq lets you record implementation and assurance separately, with an owner, due date and supporting notes.

Use focused views to find requirements that are unassessed, overdue, missing evidence or ready for verification. Give the next action to the person responsible.

03

Keep the supporting records within reach

Connect a requirement to the policies, risks, assets and evidence that explain how you address it. Reuse relevant records across your programme and review suggested relationships before accepting them.

For example, an access-control policy and a completed access review can support several related requirements. Your team decides where each record is relevant and what further evidence is needed.

CONTENT WITH CLEAR BOUNDARIES

Choose content that fits your programme

Framework content varies in scope and edition. The following examples describe the work you can organise with available content; they are not a promise that every provision of a standard or regulation is covered.

01

ISO 27001

2022 + Amendment 1:2024

Organise information security work around ISO/IEC 27001:2022, including Amendment 1:2024. Record applicability, implementation, ownership and supporting evidence for review.

Standard & 2024 amendment
02

GDPR

Organise selected data-protection requirements and their supporting policies and evidence. With the relevant privacy module, maintain processing and legal registers alongside your wider security work.

03

NIS2 and DORA

Coordinate selected cybersecurity and operational-resilience requirements with recorded risks, supplier context, incidents and continuity work where those modules are enabled. Keep responsibility and follow-up visible across the programme.

04

EU AI Act and AI governance

Use selected AI-related requirements alongside a dedicated workspace for AI systems, risk assessments and governance decisions. Explore AI Governance for the inventory, assessment and review workflow.

Explore AI Governance
05

E-ITS 2026 (Estonia)

Work with the 2026 edition of the Estonian Information Security Standard, with module-based scoping for organisations operating in Estonia. Select the modules and measures relevant to your programme.

06

Your own requirements

Create groups for internal policies, customer expectations and other requirements. Review suggested links to the controls already in your workspace.

Confirm the required edition and content scope for your workspace. Available packs contain selected requirements; related supplier, resilience, privacy and audit capabilities have their own access requirements.

A WORKED EXAMPLE

From an access-control requirement to a recorded review

Illustrative workflow · Access management

More about controls & evidence
  1. 01
    Set the scope. Add the available ISO 27001 framework to your project and open the access-control requirement relevant to your programme.
  2. 02
    Record the current position. Assign the responsible owner, describe the measure and record its implementation status.
  3. 03
    Add the supporting context. Link your access policy and the evidence for the review. Keep evidence awaiting review distinct from reviewed assurance.
  4. 04
    Assign the missing work. If the review is incomplete, create a linked follow-up task with an owner and due date.
  5. 05
    Review the result. An authorised reviewer considers the evidence and records the appropriate assessment state and notes.
  6. 06
    Prepare the handover. Export the recorded requirement assessment for discussion with management or an auditor. Check that the selected output contains the material your review needs.

The result is a requirement with its scope, owner, recorded implementation, supporting links and follow-up—not just a percentage on a dashboard.

FROM ASSESSMENT TO HANDOVER

Prepare for review with a clear record

Export supported assessment views for further review. Where Audit Preparation is enabled, organise an engagement around its scope, checklist, controls and confirmed evidence.

Reports reflect the information your team has recorded. Your reviewers remain responsible for deciding whether the scope and evidence meet the needs of the assessment.

Scope and availability

Framework management is part of the Defensiq governance, risk and compliance workspace. Available catalogue content, versions, modules, exports and permissions depend on your workspace and subscription. Some related capabilities require add-ons.

Check the framework edition and content scope in the 14-day trial, especially when you need a particular national implementation or regulatory reporting format. Professional includes one framework of your choice. Assessment records and progress indicators support your work; they do not establish certification or legal compliance.

CLARITY STARTS HERE

Questions about framework management

Details to help you decide where Defensiq fits.

Professional includes one framework of your choice (e.g. ISO 27001, NIS2, DORA or the EU AI Act). See the pricing page for plan details.

You can reuse relevant records and review suggested mappings. Each requirement still needs an appropriate scope and assessment. A link between requirements does not make them equivalent.

Yes. You can record applicability decisions and their rationale, including alternatives or inherited measures where appropriate.

Adding evidence records a relationship. Implementation and assurance have their own states, so your team can distinguish a measure that is in place from evidence that has been reviewed.

Yes. Custom requirement groups let you organise additional obligations and review their relationships with existing controls. Supported import formats and access depend on the workflow you use.

Defensiq helps you organise assessments, evidence and review work. It does not issue certification, replace an independent assessment or guarantee acceptance of a report by an authority.

YOUR NEXT STEP

Start with a framework. Connect the work.

Try the GRC platform for 14 days and begin with your scope, owners and supporting evidence.