Trust Centre

Security & compliance, in the open

ERIO handles enterprise risk data, so security is foundational — not a bolt-on. This page is a transparent summary of our controls, our standards alignment, the sub-processors we rely on, and the legal documents your procurement team will want.

UK GDPR & EU GDPR·AlignedDORA (EU 2022/2554)·AlignedNIS2 (EU 2022/2555)·AlignedEU AI Act (2024/1689)·Aligned (limited-risk)SOC 2 Type II·In progressISO/IEC 27001:2022·In progressNIST CSF 2.0·Mapped

SOC 2 / ISO 27001 control readiness (self-assessed)

64%

7 of 14 core controls in place, with a formal audit programme underway. Honest self-assessment — not a certification.

Security posture

Access control

In place

Role-based access with least privilege, plus a Role x Domain x Clearance model enforced on every request.

Authentication & MFA

In place

Bcrypt-hashed passwords, signed session tokens, and optional TOTP multi-factor authentication with one-time recovery codes.

Brute-force protection

In place

Dual-layer account lockout resists credential-guessing; deactivated accounts fail closed.

Encryption

In place

TLS in transit; integration credentials and MFA secrets encrypted at rest and never returned by the API.

Tenant isolation

In place

Customer data is logically segregated on every read and write; isolation is concurrency-tested.

Tamper-evident audit

In place

Every state change is recorded; assurance manifests are hash-chained and cryptographically signed.

Privacy & data rights

In place

Self-service data export and account erasure; published Privacy Notice and Data Processing Agreement.

Single sign-on & provisioning

In place

Enterprise OIDC single sign-on and SCIM 2.0 user provisioning / deprovisioning for Okta and Microsoft Entra.

Change management

In progress

Version-controlled codebase with release-readiness checks; a formal review and approval workflow is being documented.

Vendor & sub-processor management

In progress

Sub-processors are listed below and governed under the DPA; a living register with periodic security reviews is in progress.

Incident response

In progress

Audit trail plus a contractual breach-notification commitment; a full incident-response runbook and tabletop test are planned.

Backup & disaster recovery

On roadmap

Managed, replicated database hosting with defined RPO/RTO and tested restore is on the production-hardening roadmap.

Monitoring & alerting

On roadmap

Centralised monitoring, uptime checks and on-call alerting are part of the production rollout.

Risk assessment (ISMS)

In progress

ERIO runs a deterministic enterprise risk engine on its own register; a formal ISMS risk assessment and Statement of Applicability are being produced.

Accessibility — WCAG 2.1 AA

In place

The ERIO application is designed and continuously audited against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Automated axe-core checks run in our test suite across public and authenticated pages on every release, covering colour-contrast, ARIA roles/names, keyboard operability and focus order.

Engineering quality

In place

Every release ships with an automated test suite that covers public marketing pages, authenticated dashboards, RBAC enforcement, integration pre-flights, and the critical end-to-end flows that drive board-level decisions. The badge below is rendered offline by our CI — we don't depend on third-party badge services so the signal stays trustworthy when their infra is rate-limited.

Automated tests passing

Tenant-scope verified on every PR

In place

Cross-tenant data isolation is enforced at three independent layers: an auto-scoping Mongo proxy (ScopedDB) for tenant-owned collections, explicit dual-source filters for library/signal feeds, and a static-AST lint that scans every backend query path on every pull request. The lint fails the PR check automatically if a new query forgets to scope by tenant — so leakage cannot be merged accidentally.

  • iter126 — proxy auto-scoping
  • iter129 — function-aware CI lint
  • iter130 — dual-source playbooks

Procurement & questionnaire automations: machine-readable equivalent at /api/well-known/security-trust.json.

Tenant isolation · iter126 / 129 / 130

Tenancy architecture — how your data stays yours

ERIO is logically multi-tenant on a single MongoDB cluster, with isolation enforced at three independent layers. Every tenant-owned collection (risks, suppliers, controls, KRIs, evidence, board digests, briefings, …) is routed through an auto-scoping proxy (ScopedDB) that injects the current tenant's tenant_id into every read and write — so a missing filter in application code is physically impossible to commit. Dual-source feeds (global threat intelligence, sanctions lists, library playbooks) use an explicit, grep-auditable filter helper so the cross-tenant boundary is visible in code review. A static-AST pytest lint, wired into our GitHub Actions, fails any pull request that re-introduces an unscoped query.

Global content is shared by design, not by accident. Threat-intelligence signals (GDELT, NVD CVE, OpenSanctions, ReliefWeb), library playbooks, NIST/ISO control frameworks and sector benchmarks are stored with tenant_id = null and surfaced to every tenant through the dual-source filter — the same pattern Slack, Notion and Linear use for their global library/template surfaces. This gives you fresh, deduplicated public-intel without each customer paying for their own copy and without one customer ever seeing another's private signals or org-cloned playbooks.

If your security or regulatory team requires a dedicated database (common in Tier-1 banking, defence, or healthcare procurement), ERIO supports a drop-in upgrade path: each tenant moves to its own MongoDB database on the same cluster, with a small platform-globals database holding the shared feeds and frameworks. This is the same pattern major SaaS vendors use for their enterprise tier, and we treat it as an enterprise-pricing trigger rather than a default architecture.

Sub-processor register

The third parties that help us deliver the service. We engage sub-processors under equivalent data-protection terms and notify customers of material changes.

Sub-processorPurposeRegion
EmergentApplication hosting & deploymentAs deployed
MongoDBManaged database hostingAs deployed
ResendTransactional email deliveryEU / US
OpenAI, Anthropic & GoogleAI assistance features (via Emergent)US / EU
ElevenLabsText-to-speech narrationUS
Auth0 (Okta)Enterprise SSO (only when a customer enables it)EU / US

Legal & compliance documents

Read or download the documents below. These are templates shared for transparency and procurement review; final versions are completed at contract.

Marketing & positioning materials

Public downloads — drop into a LinkedIn post, attach to a cold email, or print for an event. No form, no NDA.

Positioning vs incumbent GRC · vendor-neutral checklist

LinkedIn-ready · case brief · sector briefs · fact card

Need our security questionnaire responses?

We maintain completed responses to common assessments (SIG-Lite, CAIQ, bespoke vendor questionnaires). Tell us where to send them and we'll follow up promptly.

Procurement pack

One ZIP with everything your security, legal and procurement teams need: the 6 public legal PDFs (Privacy Notice, DPA, Terms, AUP, SLA, AI Governance) plus the live evidence pack (Definition of Done, performance SLOs, prompt registry, session hardening, release-gate smoke report and a live 1-page Trust Snapshot rendered at the moment you click download).

Privacy NoticeData Processing AgreementTerms of ServiceAcceptable Use PolicyService Level AgreementAI Governance Statement+ Live evidence pack (Definition of Done, SLOs, prompt registry, session hardening, release-gate smoke report, Trust Snapshot)

Questions from your security team?

We're happy to complete questionnaires and walk your controls live.

Share LinkedIn X

We use only essential cookies and local storage to keep you signed in and remember preferences. See our Privacy Notice.