Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by Diligent Corporation · www.diligent.com

Report an error on this page Is this your product? →

Link to this page

Diligent One: AI-assisted analysis on whats-best.ai Diligent One: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Diligent One at a glance

Vendor
Diligent Corporation
Headquarters
Not stated on the vendor’s pages as of 14 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 14 Nov 2026
Free plan
Not stated on the vendor’s pages as of 14 Nov 2026
Panel verdict
The AI panel rates Diligent One 2.5/5, the mean of 6 judges. Diligent One is an AI-powered governance, risk and compliance platform, strongest on audit readiness where scores cluster at 5–6: audits, findings and evidence in one platform, evidence requests drafted and escalated automatically, prior engagements rolled forward, and every consequential agent action held for human approval in a traceable audit trail. how scores are made
As of
Vendor pages captured 3 Nov 2026 to 14 Nov 2026; evaluated by the panel 14 Nov 2026. all sources

Diligent One alternatives, European ones first →

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

The panel's verdict

Diligent One is an AI-powered governance, risk and compliance platform, strongest on audit readiness where scores cluster at 5–6: audits, findings and evidence in one platform, evidence requests drafted and escalated automatically, prior engagements rolled forward, and every consequential agent action held for human approval in a traceable audit trail. Integrations and automation follow at 6–7 — a Terraform provider at version 2.9.2 exposing twenty GRC objects, a REST API with OAuth 2.0 and an OpenAPI specification — though that API serves the Entities product, gated to professional or plus packages. Sovereignty is the weak point at 2: the controller is Diligent Corporation under the EU-U.S., UK and Swiss Data Privacy Frameworks with FTC enforcement, and we found no public information on hosting location, subprocessors or a data processing agreement. Information security management scores 4 — a centralised risk library and asset model, with no public information on incident workflows or a risk methodology. Judges split on controls, 4 to 6: higher scores credit automated control management, lower ones find no public statement of applicability. No price figures are published.

Report an error

Speaks for it

  • Audits, findings and evidence are managed in one platform, with prior engagements rolled forward automatically
  • Every consequential agent action requires human approval and is captured in a complete, traceable audit trail
  • Compliance-ready and board-ready reports are generated at the click of a button
  • A Terraform provider at version 2.9.2 exposes twenty GRC objects, including controls, frameworks and asset types
  • The documented REST API ships with OAuth 2.0, an OpenAPI specification and a Postman collection

Report an error

Held against it

  • We found no public information on hosting location, data residency, subprocessors or a data processing agreement
  • We found no public information on a statement of applicability generated from live control status
  • We found no public information on a documented risk methodology or incident workflows with the NIS2 24-hour and 72-hour reporting deadlines
  • We found no public information on ISO 27001, TISAX, DORA or BSI IT-Grundschutz coverage, with SOX and COSO the regimes named
  • The public REST API serves the Entities product only, and requires a professional or plus package with a site configuration of five to ten business days

Report an error

Best for

  • You run an internal audit function and want audits, findings and evidence in one platform with automated evidence requests and roll-forward of prior engagements
  • Your compliance work centres on SOX and COSO control testing with automated evidence collection and remediation tracking
  • Your team uses infrastructure-as-code and wants GRC objects such as controls, frameworks and asset types queryable through a Terraform provider
  • You need board-ready reporting from a single prompt, with every consequential agent action held for human approval

Report an error

Avoid if

  • Your procurement requires a controller or processor established in Europe — the captured pages name Diligent Corporation, a US company subject to FTC enforcement, as controller
  • Your certification programme runs on ISO 27001, TISAX, DORA or BSI IT-Grundschutz rather than the SOX and COSO regimes the pages name
  • Your integration plan assumes an open API on day one — the documented API serves the Entities product and requires a professional or plus package plus a site configuration of five to ten business days
  • You need operational NIS2 tooling — the NIS2 presence on the captured pages is a German landing page and a downloadable checklist

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Asset & risk management depth 2 of 5
Controls, SoA & measures 2.5 of 5
Framework & standard coverage 2.5 of 5
Audit readiness & evidence 3 of 5
Integrations & automation 3 of 5
European sovereignty 1 of 5

Asset & risk management depth

Show reasoning
How this is scored

The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), inheritance of protection needs (Schutzbedarf) across assets, and security incident handling with its reporting deadlines.

0 — Not an ISMS tool; the product has no asset or risk management.

3 — A risk register with likelihood and impact, and an asset list that can be imported.

5 — Asset inventory and risk management with a configurable risk matrix, risk treatment with owners and measures, and a register for security incidents.

8 — A documented risk methodology (ISO 27005, BSI 200-3 or equivalent), protection needs inherited across asset relations, incident workflows with the NIS2 reporting deadlines (24h/72h), and risk acceptance with named owners.

10 — Risk management a certifier works inside: the complete asset-risk-treatment chain with inheritance, business continuity planning (BIA, ISO 22301 or BSI 200-4), incident reporting with export for the authority, and risk reporting for the executive level.

Report an error

The CISO

Risks are prioritised by likelihood, impact and velocity with a centralised risk library, asset types are real objects in the data model, and remediation owners are assigned automatically — a genuine register, not a spreadsheet. I found no public information on a documented risk methodology such as ISO 27005, on protection-need inheritance across asset relations, or on a security incident register with the NIS2 24-hour and 72-hour reporting clocks. The NIS2 presence in the captured pages is a landing page and a downloadable checklist, which is checklist theatre rather than an incident clock I could defend to an authority. 3 4 8 9

Report an error

The GRC Consultant

Agentic cyber risk assessments prioritised by likelihood, impact and velocity, a centralised risk library, asset types as structured objects in the data model, and risk mapping to strategic objectives and critical processes — a credible risk-register-plus-asset-list footing with business-impact orientation. I found no public information on a configurable risk matrix, risk treatment with owners and measures, protection-need inheritance, or an incident register with NIS2 reporting deadlines, so I cannot place it in the mid band. 3 4 5 9 8

Report an error

The Drafted IT Officer

Asset types with categories and assessment questionnaires, a centralized risk library, risk prioritization by likelihood and impact, and mapping risks to objectives and critical processes are all documented. We found no public information on a documented risk methodology, protection-need inheritance across asset relations, a security incident register or the NIS2 24/72-hour reporting deadlines — and that is exactly the part I would personally be held to. 3 4 5 8 9

Report an error

The Lead Auditor

The cyber risk pages document agentic risk assessments prioritised by likelihood, impact and velocity, a centralised risk library, risks mapped to strategic objectives and critical processes, and asset types as first-class objects carrying assessment questionnaires. We found no public information on a documented risk methodology, protection-need inheritance across asset relations, or security incident workflows with the NIS2 24-hour and 72-hour reporting deadlines. 3 4 5 9

Report an error

The Evidence Integrator

Risks get a centralized library with prioritisation by likelihood, impact and velocity, mapping to strategic objectives and critical processes, consolidated board-level reporting, and asset types exist as first-class objects with categories and assessment questionnaire collections. Beyond that register-plus level, I found no public information on a documented risk methodology, inheritance of protection needs across asset relations, or incident workflows with the 24-hour and 72-hour reporting deadlines. 3 4 5 8 9

Report an error

The Skeptic

The cyber risk pages document risk prioritisation by likelihood, impact and velocity, a centralised risk library, and mapping of risks to strategic objectives and critical processes, and asset types and asset records are real objects in the developer data model. But we found no public information on a documented risk methodology, protection-need inheritance across asset relations, or incident workflows with reporting deadlines — the NIS2 presence we can verify is a landing page with a downloadable checklist, not an incident register. A credible risk register with an asset model, but the ISMS core beneath it is marketing territory. 3 4 5 9 8

Report an error

Controls, SoA & measures

Show reasoning
How this is scored

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

0 — No control catalogue or measures in the product.

3 — Control catalogues (such as ISO 27001 Annex A) with an implementation status per control.

5 — Controls linked to risks and to measures with owners and due dates, a statement of applicability generated from the control status, and internal audits supported with checklists.

8 — A statement of applicability always current from live control status, measure tracking with delegation and escalation, internal audit workflows with findings and corrective actions, and evidence attached to each control.

10 — The control fabric as a living system: catalogue updates versioned, audit programmes with recurring schedules, and every control answerable with linked, current evidence at any moment — all documented.

Report an error

The CISO

Controls are first-class objects carrying an availability status, tied to objectives, AI-mapped to regulations and automatically tested, with remediation plans built per control owner — operable, not a checkbox dump. I found no public information on a statement of applicability, so I cannot tell whether my Annex A would ever be current. The controls story in the captured pages is framed around SOX and COSO rather than an ISO 27001 audit. 5 6 9

Report an error

The GRC Consultant

Controls are first-class objects: the developer docs expose a control source tied to objectives, the product claims automated control testing and evidence collection, AI maps controls to regulations and drafts descriptions for gaps, and remediation owners are assigned with escalation of overdue items, with audit activity and findings managed in one platform. That is operable control management well past a static checklist; I stop short of the top band because the captured pages give no statement of applicability and no versioned catalogue updates. 5 6 10 9

Report an error

The Drafted IT Officer

Automated control testing with evidence collection, AI mapping of controls to regulations, remediation tracking with assigned owners and audit-finding management are documented, and controls and objectives exist as objects in the developer documentation. We found no public information on a statement of applicability generated from live control status — the first thing my auditor asks for — or on versioned catalogue updates. 5 6 9

Report an error

The Lead Auditor

Controls carry an availability status, AI maps each control to regulations and drafts descriptions for gaps, control testing and evidence collection are automated with human review, overdue items escalate, remediation owners are assigned, and monitoring runs around the clock. We found no public information on a statement of applicability generated from live control status, so the control side reads as operable but not demonstrably certifiable. 5 6 10 9

Report an error

The Evidence Integrator

This is an operable control side, not a checklist: control testing executed automatically with exceptions flagged for review, AI mapping controls to regulations and drafting gap descriptions, evidence requests drafted, followed up and escalated to named remediation owners, and controls queryable through the Terraform provider. I found no public information on a statement of applicability, and the linkage of controls to risks appears only indirectly through risk-aligned audit planning. 5 6 10 9

Report an error

The Skeptic

The internal controls pages document automated control testing, AI mapping of controls to regulations, evidence collection workflow, and remediation tracking with owners, and the control is a genuine object in the platform data model tied to objectives. We found no public information on a statement of applicability generated from live control status, or on measures with due dates and escalation paths. '80% time saved' percentages are advertising, not a documented SoA workflow. 5 6 9

Report an error

Framework & standard coverage

Show reasoning
How this is scored

Which regimes the product operationalises — 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 — No security framework built in; a generic task or document tool.

3 — One recognised framework (typically ISO 27001) delivered with its requirements and controls.

5 — Several named frameworks for its market (for example ISO 27001, NIS2, TISAX or BSI IT-Grundschutz), with controls mapped across at least two of them.

8 — Broad current coverage including NIS2, TISAX and DORA where relevant, one control satisfying many frameworks through a documented mapping, and updates published when a standard changes.

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

Report an error

The CISO

The captured pages name SOX and COSO, treat frameworks as first-class objects in the data model alongside compliance regulations and requirements, and claim AI mapping of controls to multiple regulations. NIS2 appears as a marketing landing page and a downloadable checklist covering third-party risk, not as an operationalised regime. I found no public information on ISO 27001, TISAX, DORA or BSI IT-Grundschutz — as a certificate holder, that gap decides the score. 5 7 8

Report an error

The GRC Consultant

The pages name SOX and COSO as the operationalised regimes, with controls tested and reported across both, and market NIS2 through a German landing page and downloadable checklist; AI compliance mapping and a framework object in the data model support one control answering several regimes. I found no public information on ISO 27001, TISAX, DORA, BSI IT-Grundschutz or SOC 2 coverage, and the NIS2 material is campaign-level rather than product documentation. 3 5 7 8

Report an error

The Drafted IT Officer

SOX and COSO are named on the internal controls page, NIS2 is marketed heavily with a downloadable checklist and supply-chain framing, frameworks exist as queryable objects in the developer docs, and AI maps controls to regulations. We found no public information on which catalogues ship pre-built, on TISAX, DORA, BSI IT-Grundschutz or ISO 27001 coverage, or on updates when a standard changes. 5 7 8

Report an error

The Lead Auditor

NIS2 is marketed with a dedicated campaign covering the company and its supply chain, SOX and COSO are named for control testing, and the platform exposes framework, compliance regulation and control objects with AI mapping of one control across regulations. We found no public information on ISO 27001, TISAX, DORA or BSI IT-Grundschutz coverage, nor on published updates when a standard changes. 5 7 8 8

Report an error

The Evidence Integrator

NIS2 is heavily operationalised in the marketing with a dedicated landing page, a downloadable checklist covering boards, cyber risk and third-party risk, and supply-chain management framing; SOX and COSO are named for control testing; frameworks and compliance regulations are first-class objects with availability flags; and AI maps controls to regulations. I found no public information on TISAX, DORA, BSI IT-Grundschutz or ISO 27001, and none on a published update cadence when a standard changes. 5 7 8 8

Report an error

The Skeptic

SOX and COSO are named on the internal controls page with claims of AI mapping between them, and framework, compliance regulation and compliance requirement are genuine objects in the Terraform provider — so the machinery exists. The NIS2 coverage we can verify is a German landing page that markets the platform and hands out a checklist; we found no public information on which framework catalogues actually ship, and no mention of ISO 27001, TISAX or DORA on the captured pages. Framework logos sold harder than they are documented. 5 7 8 8

Report an error

Audit readiness & evidence

Show reasoning
How this is scored

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

0 — No reports, history or evidence; the product only stores the current state.

3 — PDF or Word reports of risks and controls, and documents attachable to records.

5 — Versioned records or a change history, standard report generators (SoA, risk report, management report), and evidence attached per control.

8 — A revision-safe change history, audit evidence packs generated on demand, management reports at a click, and read-only auditor access.

10 — Audit readiness as a standing state: evidence status shown continuously per framework and scope, proof packs an external auditor accepts as they are, and any record reproducible as it stood on a given date.

Report an error

The CISO

Audit is this vendor's home ground: every consequential agent action is captured in a complete, traceable audit trail, compliance-ready reports come at the click of a button, evidence requests are drafted with follow-ups and escalation of overdue items, and a board-ready report is generated from a single prompt. I found no public information on read-only auditor access or on reproducing any record as it stood on a given date. Strong evidence machinery; revision-safety unproven. 5 9 9

Report an error

The GRC Consultant

Reporting is a click away — compliance-ready reports, board-ready reports from a single prompt, real-time reporting — with automated evidence collection and agent actions captured in a single traceable audit trail. I found no public information on revision-safe versioning of records, framework-scoped evidence packs, or read-only auditor access, which is what I need before calling a client audit-ready. 5 9 9 9

Report an error

The Drafted IT Officer

This is the vendor's home turf: audits and findings managed in one platform, automatic roll-forward of prior engagements, evidence requests drafted, chased and escalated automatically, compliance-ready reports at the click of a button, board-ready dashboards, and a complete traceable audit trail on every AI action. We found no public information on read-only auditor access or on reproducing any record as it stood on a given date, which is what I would want at recertification time. 5 9 9

Report an error

The Lead Auditor

Compliance-ready and board-ready reports are produced at the click of a button, evidence collection is automated, and every agentic step is captured in a complete, traceable audit trail with human approval on consequential actions. What I cannot answer from these pages is the certifier's question — we found no public information on read-only auditor access, revision-safe record history, or reproducing any record as it stood on a given date. 5 8 9 9

Report an error

The Evidence Integrator

Compliance-ready reports are generated at the click of a button, real-time and board-ready reporting exist, and every consequential agent action is captured in a complete, traceable audit trail with human sign-off and overridable recommendations. I found no public information on read-only auditor access, revision-safe change history on records, or evidence packs reproducible as they stood on a given date. 3 5 9 9

Report an error

The Skeptic

Compliance-ready reports 'at the click of a button', real-time reporting, automated evidence collection, board-ready dashboards and a board reporter agent are all documented, and the audit agent rolls forward prior engagements automatically. But the 'complete, traceable audit trail' claim is scoped to AI agent actions; we found no public information on read-only auditor access, revision-safe change history, or reproducing any record as it stood on a given date. Good report generators, unproven audit infrastructure. 5 9 9 3

Report an error

Integrations & automation

Show reasoning
How this is scored

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

0 — No import, export or integration; data is typed in and printed out.

3 — CSV or Excel import and export, and reminders for recurring reviews.

5 — Single sign-on, a documented API or a few named connectors (directory, ticketing or CMDB), and recurring tasks with reminders and assignment.

8 — A documented REST API for the core objects, a named connector set (Jira/ServiceNow-class ticketing, CMDB, cloud and endpoint sources), webhooks, SSO with SCIM provisioning, and automated evidence tests with human review.

10 — The platform behaves like infrastructure: API coverage of the whole data model, events or webhooks for every object, continuous control monitoring against the live estate, and recurring evidence collection automated and documented.

Report an error

The CISO

There is real infrastructure here: a documented REST API over HTTPS with OAuth 2.0, an OpenAPI specification and a Postman collection — for the Entities product — and a Terraform provider at version 2.9.2 exposing twenty objects of the core GRC data model, including controls, frameworks, objectives and asset types. Bitsight and SecurityScorecard feed continuous external risk insights, and control tests run automatically with human review. I found no public information on single sign-on with SCIM provisioning, webhooks, or ticketing, directory and CMDB connectors; SAP and Workday appear only as a question. 3 7 11

Report an error

The GRC Consultant

There is a genuine developer platform: a documented REST API with OAuth 2.0, an OpenAPI spec and a Postman collection for Entities data, a Terraform provider at version 2.9.2 exposing twenty GRC objects including controls, frameworks, requirements and asset types, plus Bitsight and SecurityScorecard connectors for external risk signals, with automated control testing held for human review. I found no public information on single sign-on, SCIM provisioning, webhooks, or ticketing and CMDB connectors — an FAQ raises SAP and Workday with no captured answer. 3 5 7 9 11

Report an error

The Drafted IT Officer

There is real plumbing: a documented REST API with an OpenAPI spec, OAuth 2.0 and a Postman collection, a Terraform provider reaching core objects like controls, frameworks and objectives, integrations with Bitsight and SecurityScorecard, and automated control testing and evidence collection with human review. But the publicly documented API serves the entity-management product rather than the risk core, API setup runs 5 to 10 business days and requires a professional or plus package, and we found no public information on single sign-on, SCIM, webhooks or ticketing and CMDB connectors. 3 7 9 11

Report an error

The Lead Auditor

There is a documented REST interface with an OpenAPI specification, Postman collection, OAuth 2.0 and column-level filtering for the Entities module, a Terraform provider at version 2.9.2 covering twenty core objects including controls, frameworks, compliance regulations, asset types and workflows, named connectors to Bitsight and SecurityScorecard, and automated evidence tests held for human review. We found no public information on single sign-on with SCIM provisioning, webhooks, or ticketing and CMDB connectors. 3 5 7 9 11

Report an error

The Evidence Integrator

Genuine infrastructure tooling exists: a REST API over HTTPS returning JSON with OAuth 2.0, an OpenAPI specification and a Postman collection; a Terraform provider at version 2.9.2 exposing twenty highbond data sources including control, framework, compliance regulation, objective and workflow; Bitsight and SecurityScorecard connectors feeding continuous external risk insight; and 24/7 control monitoring held for human review. But that REST API serves the Entities module only, gated to professional or plus packages with a five-to-ten-business-day site configuration, and I found no public information on directory, CMDB, ticketing, cloud or endpoint connectors, webhooks, or single sign-on with SCIM provisioning — SAP and Workday appear only as an unanswered question in a FAQ. 3 5 7 9 11

Report an error

The Skeptic

The developer docs are the strongest thing here: a REST API with OAuth 2.0, an OpenAPI specification, a Postman collection and rate limits — though for the Diligent Entities product — plus a Terraform provider at version 2.9.2 with twenty data sources across assets, controls, frameworks, questionnaires and workflows, named Bitsight and SecurityScorecard connectors, and continuous control monitoring held for human review. We found no public information on single sign-on, SCIM, webhooks, or ticketing and CMDB connectors; the SAP and Workday integration appears only as an unanswered FAQ question, which is exactly the 'coming soon sold as shipped' pattern I watch for. 11 7 3 5 9

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where the security posture of the whole company actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, AI features, email, support tooling), DPA. The risk register is itself a target. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.

0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or EU hosting is offered only on request or on top tiers.

5 — EU hosting stated as the default, a data processing agreement and a subprocessor list published; a parent company or a subprocessor may sit outside the EU.

8 — EU entity, EU hosting in named data centres, a subprocessor list with no non-EU processor touching customer content, and the DPA and TOMs published.

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

Report an error

The CISO

The controller is Diligent Corporation, a US company subject to FTC enforcement that certifies compliance with the EU-U.S. Data Privacy Framework and has appointed EU and UK representatives — the posture of a processor established outside Europe — and an example API endpoint in the developer documentation points to a us. host. I found no public information on hosting locations, subprocessors, or a data processing agreement. My risk register would live under US jurisdiction with unproven hosting, and that decides it. 2 11

Report an error

The GRC Consultant

The privacy policy puts the controller under Diligent Corporation in the EU-U.S. Data Privacy Framework with FTC enforcement, appoints Irish and UK representatives, and discloses that KYC verification providers may process outside your country. Hosting location, a published data processing agreement and a subprocessor list are not stated on the captured pages, so I can score only the documented US-jurisdiction posture with GDPR hygiene. 2 10

Report an error

The Drafted IT Officer

Diligent Corporation is named as controller, certified under the EU-U.S., UK and Swiss Data Privacy Frameworks with the U.S. Department of Commerce, subject to FTC enforcement, holder of FedRAMP and DoD IL5 certifications, with an EU representative in Dublin named for GDPR queries. We found no public information on hosting location, subprocessors, a data processing agreement or any EU hosting option, so the company risk register would sit with a vendor operating under US law frameworks and everything else stays unknown. 2 3

Report an error

The Lead Auditor

The captured pages establish Diligent Corporation as the controller, self-certified under the EU-U.S. Data Privacy Framework, subject to FTC enforcement, and holding FedRAMP and DoD IL5 certifications, with EU and UK representatives in Dublin and London. We found no public information on hosting location, subprocessors, or a published data processing agreement, so the jurisdictional picture is a US entity with the rest unstated. 2 3

Report an error

The Evidence Integrator

A privacy policy is published naming Diligent Corporation and relevant group companies as controllers, with an EU representative in Dublin, a UK representative in London and a data protection officer contact, and the transfer posture rests on the EU-U.S., UK and Swiss-U.S. Data Privacy Frameworks under FTC enforcement. I found no public information on hosting location, data residency, subprocessors or a data processing agreement, so whose law the risk register actually lives under stays opaque. 2 10

Report an error

The Skeptic

The privacy policy names Diligent Corporation as controller, self-certified under the EU-U.S. Data Privacy Framework and subject to FTC enforcement, with EU and UK representatives in Dublin and London — meaning the risk register and its evidence would sit with a controller relying on US adequacy terms rather than EU-only processing. We found no public information on hosting location, a subprocessor list, or a data processing agreement. For a company selling NIS2 tooling into Germany, an unproven hosting and subprocessor chain is the weak point. 2

Report an error

Pricing transparency not rated — the vendor publishes no price

Show reasoning
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 — A public "from" price or one priced edition; the other editions, modules or scale steps are not public.

5 — Public prices per edition or tier with the billing period (monthly or annual) stated and the main inclusions listed.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated, software separated from consulting, and VAT treatment given; 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 CISO

The captured pages contain no price figures; the German page sells only through a demo request, and even API access is gated behind a conversation with the customer success manager about 'professional' and 'plus' packages. 'Flexible pricing for organizations of any size' is a marketing phrase, not a number. Every configuration is a sales conversation. 8 11 1

Report an error

The GRC Consultant

I found no price figures on the captured pages: the German campaign page offers a demo request only, package names such as professional and plus surface in the developer docs without figures, and the homepage speaks of flexible pricing for organisations of any size. Every configuration I can see routes through a sales conversation, so a buyer cannot compute an invoice from public material. 1 8 8 11

Report an error

The Drafted IT Officer

No price figure appears on the captured pages: the German NIS2 page sells only via a demo request, the homepage claims "flexible pricing" without numbers, and the API is gated behind unpriced professional or plus packages. For someone who has to tell the CFO what this costs before booking a consultant demo, this is a sales conversation rather than a computable invoice. 1 8 11

Report an error

The Lead Auditor

The captured pages give no price figures and route sales through a demo request; the only packaging detail published is that the Entities Reports API requires a professional or plus package, and flexible pricing is described in marketing language without numbers. A buyer cannot compute any part of the invoice from public pages alone. 1 8 11

Report an error

The Evidence Integrator

The captured pricing-relevant page itself states it carries no price figures and that sales runs only through a demo request, and the only other signals are a "flexible pricing" claim and package names — professional and plus — with no numbers attached. No edition, module or annual price is computable from the public pages I read. 1 8 11

Report an error

The Skeptic

The captured pages contain no prices at all: the German NIS2 page sells only through 'Demo anfordern', and the developer docs name 'professional' and 'plus' packages without attaching figures to them. The homepage's 'flexible pricing' is an adjective, not a number — nothing on these pages lets a buyer compute an invoice. In a market where this is common, it is still a zero-information position. 8 1 11

Report an error

European sovereignty — proven facts

0 of 6 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.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Diligent One

Is Diligent One European?

Not determined: the vendor’s pages as captured do not say where Diligent One is based.

Where does Diligent One store data?

Not stated on the vendor’s pages as of 14 Nov 2026.

Does Diligent One have a free plan?

Not stated on the vendor’s pages as of 14 Nov 2026.

What are the best alternatives to Diligent One?

As of 18 Nov 2026, the panel rates preeco | informationssicherheit (3.5/5), 6clicks (3.5/5) and Secfix (3.5/5) highest among the other 35 Information Security products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is preeco | informationssicherheit (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Diligent One alternatives.

Where this could be wrong

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.

Sources (11)

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

  1. 1 Vendor page www.diligent.com Checked 14 Nov 2026 Details →
  2. 2 Legal notice — found from the homepage www.diligent.com Checked 14 Nov 2026 Details →
  3. 3 Asset & risk management depth — found from sitemap www.diligent.com Checked 14 Nov 2026 Details →
  4. 4 Asset & risk management depth — found from sitemap developer.diligent.com Checked 14 Nov 2026 Details →
  5. 5 Controls, SoA & measures — found from sitemap www.diligent.com Checked 14 Nov 2026 Details →
  6. 6 Controls, SoA & measures — found from sitemap developer.diligent.com Checked 14 Nov 2026 Details →
  7. 7 Framework & standard coverage — found from sitemap developer.diligent.com Checked 14 Nov 2026 Details →
  8. 8 Framework & standard coverage — found from sitemap www.diligent.com Checked 14 Nov 2026 +1 earlier capture: 3 Nov 2026 Details →
  9. 9 Audit readiness & evidence — found from sitemap www.diligent.com Checked 14 Nov 2026 +2 earlier captures: 3 Nov 2026, 3 Nov 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap www.diligent.com Checked 14 Nov 2026 Details →
  11. 11 Integrations & automation — found from sitemap developer.diligent.com Checked 14 Nov 2026 Details →