Information Security

HiScout GRC Suite

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 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 5 Oct 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 Lead Auditor

Weighted verdict

Certifies ISMSs for a living and has seen every folder of screenshots. Optimizes for revision-safe history, an SoA generated from live control status, and a defensible answer to "show me the state on date X". Rejects audit trails assembled the week before the audit.

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

Scored by The Lead Auditor

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 Lead Auditor

The risk methodology is real and documented — risk analysis to BSI-Standard 200-3 and 100-3 with measure suggestions drawn from the cross-reference tables, and Grundschutz and BCM risk results flowing together in one tool down to IT implementation. I found no public information on incident handling with statutory reporting clocks or explicit protection-needs inheritance across asset relations, which is what separates a documented methodology from a backbone a certifier works inside. 3 2 7 8

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 Lead Auditor

Measures are genuinely shared rather than re-typed: TOMs selectable from stored catalogs — BSI Grundschutz, compliance guidelines, the Standard-Datenschutz-Modell — measures maintained in other modules assignable to processing activities, and audit findings routed automatically to the correct recipients against the stored infrastructure. I found no public information on generating a statement of applicability from live control status or on delegation and escalation in measure tracking, so the control side is operable but not evidenced as self-documenting. 3 2 11

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 Lead Auditor

For its home market the depth is exceptional: full support of BSI-Standard 200-1/2/3, parallel Kompendium editions, ratings carried forward on updates, and visible preparation for Grundschutz++ in machine-readable OSCAL — that is regime maintenance you can actually watch. Beyond that, ISO 27001 and 22301 appear as certification support and GDPR as a full module; I found no public information on NIS2, TISAX, DORA or SOC 2, and the multi-framework story rests on shared measures on one central data basis rather than demonstrated one-control-many-frameworks mapping. 4 1 2 9 10

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 Lead Auditor

Revision-safe documentation is claimed outright with all information centrally captured, and reports name the underlying Kompendium edition while reports on previous editions remain available — that gives a defensible answer for the state under a given framework edition. Mobile evidence capture in real time, ISO 19011 audit programmes with annual plans, and ad-hoc reporting round it out; I found no public information on auditor access roles or exportable evidence packs per scope, so this is strong but not the standing state I certify against. 10 11 12

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 Lead Auditor

Feeding the real estate is present but dated: direct import from GSTOOL, CMDB and Excel, a dynamic XML interface for binding data in, and a DataExchange extension for database connections — exactly the federal tooling you would expect. I found no public information on a REST API, directory import, SSO, webhooks or ticketing connectors, and the automation evidenced is push-button report compilation and questionnaire imports rather than continuous collection. 3 2

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 Lead Auditor

This is a chain I can mostly defend: a Berlin entity wholly owned by the German HiSolutions AG, development and support 100 percent in Germany, SaaS data in data centers within Germany, and an on-premise variant with equal feature set — plus an ITZBund-hosted standard offering for federal authorities. The published processor list covers the website and customer portal rather than the platform itself, and the webinar chain relies on EU-US Data Privacy Framework certification, so a US reach remains at the periphery. 4 5 6 2

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 Lead Auditor

No public price appears on any captured page; even the audit module's product factsheet is request-only, with the sales address as the path to information. Every configuration is a sales conversation, which the market norm tolerates but the buyer should know upfront. 3 11

Report an error

European sovereignty — proven facts

2 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 DE	3/3 pts	5 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	EU only ⚠ unverified	3/3 pts	6 Report an error
Subprocessors	Not determined ⚠ unverified	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 23 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Data residency. This statement covers HiScout's own website and customer-portal processing, which is hosted by the Berlin-based DEONT GmbH; the excerpt says nothing about where the core HiScout GRC software itself is deployed, and it elsewhere concedes that webinar registrations via GoTo Technologies are processed in a third country.
Weak sourcing — Subprocessors. Not confirmed on the vendor’s own pages as captured.
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.

We found no public information on pricing on the pages we read (hiscout.com, hiscout.com/module/grundschutz, hiscout.com/module/datenschutz, hiscout.com/ueber-uns, hiscout.com/impressum, hiscout.com/datenschutzerklaerung and 6 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
49 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
8 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
7 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
5 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
4 hosting 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
2 data 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
2 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
1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us

Do you know more about HiScout GRC Suite? Tell us Report an error on this page

Sources (12)

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

1 Vendor homepage www.hiscout.com Checked 15 Sep 2026 +1 earlier capture: 23 Aug 2026 Details →
2 IT-Grundschutz module page www.hiscout.com Checked 15 Sep 2026 +1 earlier capture: 23 Aug 2026 Details →
3 Data protection module page www.hiscout.com Checked 15 Sep 2026 Details →
4 About page www.hiscout.com Checked 15 Sep 2026 Details →
5 Imprint www.hiscout.com Checked 15 Sep 2026 Details →
6 Privacy policy www.hiscout.com Checked 15 Sep 2026 +1 earlier capture: 24 Aug 2026 Details →
7 Asset & risk management depth — found from sitemap www.hiscout.com Checked 1 Oct 2026 Details →
8 Asset & risk management depth — found from sitemap www.hiscout.com Checked 1 Oct 2026 Details →
9 Framework & standard coverage — found from sitemap www.hiscout.com Checked 1 Oct 2026 Details →
10 Framework & standard coverage — found from sitemap www.hiscout.com Checked 1 Oct 2026 Details →
11 Audit readiness & evidence — found from sitemap www.hiscout.com Checked 1 Oct 2026 Details →
12 Audit readiness & evidence — found from sitemap www.hiscout.com Checked 1 Oct 2026 Details →