Skip to content
All technical docs Bricks technical documentation

DORA

What Bricks provides to a financial entity that runs on it under DORA: the inventory of ICT assets, protection and detection, backups, the register of third parties, supply-chain screening and exit.

DORA

Bricks Technical Documentation

What Bricks provides to a financial entity that runs on it under DORA: the inventory of ICT assets, protection and detection, backups, the register of third parties, supply-chain screening and exit.


DORA places its obligations on the financial entity: an insurer, a bank, an insurance broker above the size of a small enterprise. Bricks is an ICT third-party service provider to that entity. This page says what the platform gives the entity to meet its obligations and what evidence it can hand to its supervisor. Bricks applies the same practices to every organisation, whether or not DORA applies to it. The other regulations are covered in Compliance evidence for auditors.

Art. 8 — Identification of ICT assets

An organisation's system on Bricks is made of declared parts: tables, roles and permissions, apps, workflows, third-party connections, retention rules. Each is declared before it exists, and the platform builds the system from the declarations. The declarations are therefore an inventory of the organisation's software assets and processing that cannot drift from what runs. The inventory can be exported without any of the organisation's data.

Art. 9 — Protection and prevention

  • Access follows from declared roles and permissions, enforced row by row by the database. Each role is read as a mandate.
  • Changes applied to an organisation are checked first and can be run as a dry run that reports what they would do without doing it.
  • Encryption in transit everywhere, at rest by the hosting providers, and by the application for third-party secrets and for values an organisation chooses to protect with its own key.
  • Staff access only at the organisation's request, with a reason, recorded before it runs.

Current limits. There is no end-to-end encryption, and secrets held for third parties share one platform key with no rotation procedure yet.

Art. 10 — Detection

Trail What it records
Writes Every write to the tables an organisation enrols, whatever the channel, with who made it or that it was anonymous; what changed, not a second copy of the data
Membership Every role given or removed, by whom and when
Staff access Every access by Bricks staff, with its reason, its support request, whether it could write and whether an AI agent ran it
Workflow runs Each run: trigger, each step and its outcome, the platform version

The write and membership trails are written by the database itself, so no channel can bypass them.

Art. 11 and 12 — Backup and recovery

  • The database is snapshotted daily; snapshots are kept seven days.
  • Stored files are versioned: a deleted or overwritten file can be recovered.

Current limits. Restoring to a point older than seven days is not possible. Replication of stored files to another region is not confirmed.

Art. 28 — ICT third-party risk and the register of information

  • Every third party is declared and signed. Each connection names the vendor, its jurisdiction, the purpose, the lawful basis and the data concerned, and is signed by an administrator. Undeclared hosts are blocked in the browser and on the server (Data flows). The declarations form the organisation's register of third parties.
  • The supply chain is screened. The code Bricks ships inside an organisation's apps is checked on every platform change: a dependency under a strong copyleft licence, or whose licence cannot be identified, is refused.
  • Critical dependencies are watched. Components on a single platform-wide path (authentication, database, gateway) are catalogued; their releases and security advisories are followed on a set cadence, and upgrading one is a deliberate, reviewed change.

Art. 28(8) — Exit strategy

An organisation can take out what it built: the source of each app, its workflows as a bundle that can be imported again, and its structure without data. Data leaves through exports the organisation declares. Every export of source, allowed or refused, is recorded.

Art. 30 — Contractual provisions

The contractual clauses DORA requires (service description, data location, access and audit rights, termination and exit) belong to the agreement between the financial entity and Bricks, not to the platform. The evidence on this page is what those clauses can refer to.