Compliance evidence for auditors
Bricks Technical Documentation
Where an auditor, a DPO or a risk officer starts: the principle behind Bricks's compliance evidence, one page per regulation, the limits that apply to all of them, and how to obtain the evidence.
These pages are written for people who assess an organisation that runs on Bricks: auditors, data protection officers, risk and compliance officers. They say what the platform does and what evidence it gives, not how to build on it.
The principle
An organisation declares what it runs before it runs it, and the platform works from those declarations. Its tables, roles and permissions, apps, workflows, third parties and retention rules are declared first; the platform builds the database, the access rules and the apps from them. The same declarations make the system run and give account of it, so the evidence describes what actually runs rather than what someone wrote about it afterwards.
One page per regulation
| Regulation | What the page covers |
|---|---|
| GDPR | Protection by design, the generated record of processing, processors and transfers, security of processing, retention and erasure, what the people concerned see |
| DORA | Inventory of ICT assets, protection and detection, backup and recovery, the register of third parties, supply-chain screening, exit |
| eIDAS | Identification through BricksID, the simple electronic signature, its sealed evidence and long-term verification |
| eIDAS 2 | The European Digital Identity Wallet: what changes, where BricksID stands, what already fits |
| AI Act | Marking AI content, provenance of apps, telling people they interact with an AI, declared AI assistants |
Each page states its own current limits, so an assessment starts from what runs today.
Limits that apply to all of them
- The platform has not yet been through a formal external audit. The evidence is produced by the platform and can be checked against it; it has not yet been certified by a third party.
- There is no end-to-end encryption: the platform can read the data organisations and people store. Protection comes from access rules, mandates and recorded staff access.
Obtaining the evidence
An organisation's administrators read and export its record of processing, its data flows and its staff-access record from the organisation's settings. Other evidence (the inventory export, trail extracts, the platform's own policies and architecture documentation) is provided to an organisation's auditor on request, under a confidentiality agreement.