Information Security

ISMS.online

UK / wider Europe Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The CISO v1.0 · The GRC Consultant v1.0 · The Drafted IT Officer v1.1 · The Lead Auditor v1.0 · The Evidence Integrator v1.0 · The Skeptic v1.1 · rubric v1 · evaluated 16 Sep 2026

Compare with verinice → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Evidence Integrator

Weighted verdict

Believes evidence that is typed is evidence that is stale. Optimizes for connectors to the live estate — directory, CMDB, ticketing, cloud — continuous control checks, and an API with parity to the UI. Rejects data islands with a CSV drawbridge.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Evidence Integrator

Asset & risk management depth

How this is scored

The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), protection-needs inheritance, incident handling with statutory clocks.

0 — No ISMS substance; "information security" is a chapter in the marketing site.

3 — A flat risk list and an asset spreadsheet import; no treatment tracking, no inheritance, incidents live in the ticket system.

5 — Asset and risk management with configurable matrices and treatment tracking; basic incident handling; inheritance and aggregation need manual work.

8 — A real risk backbone: documented methodology (ISO 27005 or equivalent), inherited protection needs across asset relations, incident workflows with statutory reporting clocks (NIS2 24h/72h), risk acceptance with ownership.

10 — Risk management a certifier works inside: complete asset-risk-treatment chain with inheritance, continuity planning, incident reporting with authority export, and risk reporting the executive level actually reads.

Report an error

The Evidence Integrator

The evidence shows a 'Dynamic Risk Register & Treatment' and an 'automated risk assessments' marketing line, but nothing on asset inventory, a documented risk methodology, protection-needs inheritance, or incident workflows with statutory clocks — the only '24 hours' quote is the vendor's own breach-notification promise about itself, not a customer-facing feature. 2 4 5

Report an error

Controls, SoA & measures

How this is scored

Control catalogs, statement of applicability, measure tracking and internal audit — whether the control side of the ISMS is operable or a checklist.

0 — A static control checklist; applicability, implementation status and evidence are the consultant's spreadsheet.

3 — Control catalogs with status fields, but no SoA generation, no measure ownership, no link between controls and risks.

5 — Controls linked to risks and measures with owners and due dates; SoA producible with manual assembly; internal audit supported by checklists.

8 — SoA on demand from live control status, measure tracking with delegation and escalation, internal audit workflows with findings management, controls carrying their own evidence.

10 — The control fabric as a living system: catalog updates versioned, SoA always current, audit programs with recurring schedules, and every control answerable with linked evidence at any moment.

Report an error

The Evidence Integrator

Pre-configured control templates with version history, approval workflow, owner assignment and automatic mapping to standards clear the checklist bar, and 'update a risk, a policy or a piece of evidence, and the rest of the platform reflects it instantly' hints at real linkage. But the evidence is completely silent on SoA generation, internal audit workflows, findings management and delegation — content packs, not an operable control fabric. 2 1

Report an error

Framework & standard coverage

How this is scored

Which regimes the product actually operationalizes — ISO 27001, NIS2, TISAX/VDA ISA, DORA, BSI IT-Grundschutz, SOC 2 — and whether one control maps across them or each framework is a fresh island.

0 — One framework, hard-coded; anything else is "on the roadmap".

3 — Two or three frameworks as separate checklists; the same control is answered once per framework.

5 — The major regimes for its market with partial cross-mapping; newer regimes (NIS2, DORA) present as content packs of varying depth.

8 — Broad current coverage including NIS2/TISAX/DORA where relevant, one-control-many-frameworks mapping, and visible maintenance as regimes evolve.

10 — Framework coverage as a living product: dozens of regimes, genuine multi-compliance mapping on one data basis, per-industry profiles, and documented update cadence when the standard moves.

Report an error

The Evidence Integrator

100+ frameworks claimed consistently across sources, with NIS 2, GDPR, SOC 2, ISO 42001, EU AI Act and NIST named inside one platform pitch plus localized ISO 27001 content — genuine breadth. What I don't get is proof that one control answer maps across regimes on one data basis rather than 100 fresh islands, nor any evidence of update cadence or per-industry profiles. 2 3 1

Report an error

Audit readiness & evidence

How this is scored

Whether the system produces defensible proof: revision-safe history, evidence collection, reports for auditors, authorities and management.

0 — Exports are screenshots; history is overwritten in place.

3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.

5 — Versioned records, standard report generators, evidence attachments per control; assembling a full audit file still takes days.

8 — Revision-safe change history, audit-scoped evidence packs on demand, management reports current at a click, auditor access roles.

10 — Audit readiness as a standing state: continuous evidence status per framework and scope, exportable proof packs an external auditor accepts as-is, and a defensible answer to "show me the state on date X".

Report an error

The Evidence Integrator

Policy version history and approval workflow and evidence as a platform object are a start, and 'audit readiness' is the marketing word of the day. Zero evidence of platform-wide revision-safe history, audit-scoped evidence packs, report generators or auditor access roles — the evidence never shows an external auditor being handed anything defensible. 5 1

Report an error

Integrations & automation

How this is scored

Whether the platform feeds from the real IT estate — directory import, CMDB, ticketing, scanners, API — and automates evidence collection instead of re-typing it.

0 — A closed island: manual entry in, PDF out, no API.

3 — CSV/Excel import and export; no live connections, no API worth the name.

5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing, CMDB or SSO); automation is reminders and recurrence.

8 — Real connector set (Jira/ServiceNow-class ticketing, CMDB, cloud and endpoint sources), webhooks, SSO/SCIM, automated evidence tests with human review.

10 — The platform behaves like infrastructure: API parity for the data model, event streams, continuous control monitoring against the live estate, and automation that measurably removes the recurring toil rather than renaming it.

Report an error

The Evidence Integrator

A Public API and a native ServiceNow connector exist, which is more than a CSV drawbridge — but the only documented integration depth is Google Drive as a file picker that 'never accesses, or performs actions on, the file itself'. No directory import, no CMDB, no cloud/endpoint sources, no webhooks, no SSO/SCIM, and 'automates compliance tasks' reads as reminders and recurrence, not continuous control checks against the live estate. 2 3 4 5

Report an error

European sovereignty

How this is scored

Where the security posture of the whole company actually lives and under whose law — entity, hosting, subprocessors, DPA. The risk register is itself a target.

0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your risk register.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.

5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.

8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.

10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, on-premises or sovereign-cloud options, and the whole chain documented publicly.

Report an error

The Evidence Integrator

The risk register would sit with a UK-registered entity (Alliantist, England and Wales) with an EU data centre as one of four co-equal customer choices rather than a default. The only published subprocessor list is the controller-role one, saturated with US CLOUD Act reach — Anthropic, OpenAI, Google, Microsoft, Atlassian — and the processor chain that actually touches customer ISMS content is undocumented in this sheet. 3 4

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.

0 — No public prices at all; every configuration is a sales conversation.

3 — An entry price exists, but module add-ons, scale steps or bundled consulting make the real total incomputable.

5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; only genuine corporate-group contracts are custom.

10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a certification project is a two-minute exercise.

Report an error

The Evidence Integrator

'IO's pricing is bespoke to you' with no published seat or tier prices — every configuration is a sales conversation, which is the 0 anchor by definition. This describes the market norm rather than condemning it, but the evidence leaves nothing to compute. 2

Report an error

European sovereignty — proven facts

3 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Incorporated in GB ⚠ unverified	1/3 pts	4 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	EU optional ⚠ unverified	1/3 pts	4 Report an error
Subprocessors	US CLOUD Act reach ⚠ unverified	0/2 pts	4 Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 11 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Legal entity. Alliantist is registered in the United Kingdom, which is outside the EU since Brexit.
Weak sourcing — Data residency. The notice lists UK, EU, APAC and US data centres for different customers without stating which region is the default assignment, so EU hosting is one choice among several.
Weak sourcing — Subprocessors. The list is scoped to Alliantist's role as Data Controller and mixes marketing tools with service providers, so which of these US-headquartered firms process customer data inside the product is not separated out; the product hosting itself is only described as 'a third-party data centre' and AWS is noted as 'UK and Ireland'.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

41 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
9 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
5 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
4 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
3 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us

Do you know more about ISMS.online? Tell us Report an error on this page

Sources (16)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor homepage www.isms.online Checked 16 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
2 Vendor pricing page www.isms.online Checked 16 Sep 2026 Details →
3 Platform features page www.isms.online Checked 16 Sep 2026 Details →
4 Privacy policy www.isms.online Checked 16 Sep 2026 Details →
5 ISO 27001 framework page www.isms.online Checked 16 Sep 2026 Details →
6 Privacy policy www.isms.online Checked 30 Sep 2026 Details →
7 Asset & risk management depth — found from sitemap support.isms.online Checked 1 Oct 2026 Details →
8 Asset & risk management depth — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
9 Controls, SoA & measures — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
10 Controls, SoA & measures — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
11 Framework & standard coverage — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
12 Framework & standard coverage — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
13 Audit readiness & evidence — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
14 Audit readiness & evidence — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
15 Integrations & automation — found from sitemap www.isms.online Checked 1 Oct 2026 Details →
16 Integrations & automation — found from sitemap www.isms.online Checked 1 Oct 2026 Details →