whats-best.ai
Search Sign in

Information Security

ibi systems iris

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

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

by ibi systems GmbH · www.ibi-systems.de

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

An asset layer is proven by the API's CMDB import/export, but the evidence is silent on risk methodology, treatment tracking, protection-needs inheritance and incident workflows — no NIS2 clocks, no risk acceptance shown. A dedicated ISMS product clears rubric level 0, but this is flat-list territory at best. 1 2

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

The only control-side evidence is that iris supports requirements from ISO 27001/27002 and BSI IT-Grundschutz plus programmatic creation of Prüfungen via the API. No SoA generation, no measure ownership, no control-risk linkage, no findings management — catalogs implied, operability unevidenced. 2

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

The German-market regime list is genuinely broad — ISO 27001/27002, IT-Grundschutz, BSI 200-4, ISO 22301, MaRisk, NIS-2, DORA, DSGVO/BDSG. But nothing evidences one-control-many-frameworks mapping or a maintenance cadence, and if each regime is a fresh island every control gets re-typed per framework — and typed evidence is stale evidence. 2

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

Report and list exports in Word/PDF/Excel/CSV are the entire evidenced audit story. No revision-safe change history, no evidence packs, no auditor access roles, no 'state on date X' — the API can create Prüfungen automatically but nothing shows results collected or preserved automatically. 2

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

One documented REST API for arbitrary third-party systems, with CMDB asset import/export and automated Prüfungen creation, keeps iris off the CSV-drawbridge list. But no directory import, no SSO/SCIM, no ticketing connectors, no webhooks, and above all no automated evidence tests or continuous control monitoring — a generic API, not a connector fabric feeding from the live estate. 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 Evidence Integrator

German GmbH with a Regensburg register entry, development exclusively in Germany, an on-prem option, and a stated default of no third-country transfer form a solid jurisdictional base. But the SaaS data center is unnamed, no product DPA/TOMs or product subprocessor list is published (the privacy policy covers only website services like Google Ireland and Microsoft Ireland, with US transfer not excluded for Bookings), and ownership is undocumented — short of rubric level 8. 2 3 4 5

Report an error

Pricing transparency

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

The license model is documented — named user, full feature scope, no module tiers — but not a single price is public, so no buyer can compute any invoice. Structure transparent, price opaque: barely off rubric level 0. 2

Report an error

European sovereignty — proven facts

1 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.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

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.

Do you know more about ibi systems iris? Tell us Report an error on this page

Sources (9)

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

  1. 1 Vendor homepage www.ibi-systems.de Checked 16 Sep 2026 Details →
  2. 2 ISMS/GRC product page www.ibi-systems.de Checked 16 Sep 2026 Details →
  3. 3 Company page www.ibi-systems.de Checked 16 Sep 2026 Details →
  4. 4 Imprint www.ibi-systems.de Checked 16 Sep 2026 Details →
  5. 5 Privacy policy www.ibi-systems.de Checked 16 Sep 2026 Details →
  6. 6 Asset & risk management depth — found from sitemap www.ibi-systems.de Checked 1 Oct 2026 Details →
  7. 7 Asset & risk management depth — found from sitemap www.ibi-systems.de Checked 1 Oct 2026 Details →
  8. 8 Framework & standard coverage — found from sitemap www.ibi-systems.de Checked 1 Oct 2026 Details →
  9. 9 Framework & standard coverage — found from sitemap www.ibi-systems.de Checked 1 Oct 2026 Details →