Standards and frameworks

ArgueSecure helps you evidence the risk-assessment requirement of a standard or regulation. It does not make you compliant.

The templates

Nine of the bundled templates turn a standard or regulation into a gap analysis. Each control or obligation is a defence set to to do, placed under the threats it addresses. Mark what you have as implemented and shelve what is out of scope. The descriptions summarise the controls; they are not the text of the standards, and not legal advice.

Bundled templates, the standards templates and the examples
TemplateWhat it contains
Northwind Outfitters (demo web shop)A worked example of an assessment in progress.
Four system archetypesPublic web application, multi-tenant SaaS, corporate internal network, connected home device.
ISO/IEC 27001:2022Clauses 4 to 10 and all 93 Annex A controls (ISO/IEC 27002 guidance).
ISO/IEC 42001:2023Clauses 4 to 10 and all 38 Annex A controls of the AI management system standard.
EU AI ActThe operator obligations of Regulation (EU) 2024/1689.
SOC 2All 61 Trust Services Criteria: CC1 to CC9, Availability, Confidentiality, Processing Integrity and Privacy.
GDPRThe controller and processor obligations of Regulation (EU) 2016/679.
NIS2The obligations Directive (EU) 2022/2555 places on essential and important entities, including the Article 21 measures and incident reporting deadlines.
CIS Controls v8.1All 18 Controls and 153 Safeguards, with the 56 Implementation Group 1 safeguards marked.
NIST CSF 2.0All 106 Subcategories of the six Functions, Govern to Recover.
EU Cyber Resilience ActThe essential requirements of Annex I and the manufacturer obligations of Articles 13 and 14 of Regulation (EU) 2024/2847.

The first two rows are examples to learn from; the other nine are the standards templates. Administrators can add templates of their own, or publish a copy of an assessment as one.

How a gap analysis works in the tool

  1. Create the assessment from a template. Every account can do this. The template never changes; you get a copy you own.
  2. Set the status of each control. Every control starts as a defence set to to do. Mark what you already have as implemented and shelve what is out of scope for you.
  3. Argue the risks. The template places controls under risks and attacks. Remove the ones that do not apply to your system, add what is missing, and give the risks and attacks values for your own system. The template's example figures are not copied.
  4. Rate the controls. Set how strongly a defence counters each attack it is linked to, and add costs. The report then ranks defences by cost benefit.
  5. Read the control coverage. The report's Control coverage section lists, for each framework, every cited control, whether it is implemented, planned or shelved, and the defences citing it. It lists what is cited. It is not a whole framework and not a statement of compliance.

Each defence in a standards template cites its control on its References tab, in the form ISO27001-2022:A.5.23. On a defence of your own, choose Control and type a framework code, a colon and the control. The codes are ISO27001-2022, ISO42001-2023, EUAIACT, GDPR, NIS2, SOC2, CIS8, CSF2, CRA. References are checked against each framework's own format.

Part of the Control coverage table in the report of an ISO/IEC 27001:2022 assessment: controls A.5.12 to A.5.27, four of them implemented and the rest planned.

Two ways to use a template

Start from a template

Create an assessment from it. Remove the risks, attacks and defences that do not apply, adjust and quantify the ones that do, and add what is missing. This suits a first gap analysis against one standard.

Take parts of a template

In a blank or existing assessment, use Add from template on a node, or From template in the new-node dialog, to copy in only the relevant risks, or to use a template's attacks and defences as a starting point. Only titles and descriptions are copied; values and citations are left behind. A node whose title already exists is linked instead of copied a second time.

What this supports

Several of these standards ask for a documented risk assessment. ArgueSecure supports a gap analysis against them, and it documents how risks were identified: who added which claim, which changes were made and when, and which versions the assessment went through. The report is something you can hand to a manager or an auditor.

It is not a compliance certificate and not a GRC platform. It is not legal advice. It has no scanner and discovers nothing by itself: it structures what the people in the room know and argue.

Start a gap analysis

Open the demo and create an assessment from a template to see the controls and the coverage section, or run your own instance and keep the work on your server.