Compliance

The French text governs. This page is the English version of Conformité FR.

4 capabilities only, and a table that says what other compliance pages on the market do not: how many controls are actually self-assessed, and how many are not. The figures below are computed when this page is built, from the map the package ships; they are not copied by hand.

4

capabilities in this family

0

active on installation day, on the Discovery offer

Small business

entry tier of the family

What this family measures

The pack maps the findings produced by the other families to regulatory articles. The table below is the only figure that counts: out of 255 controls catalogued across 8 frameworks, 71 are self-assessed by a detector. The others are not, and this page does not pretend otherwise.

Map 2026.09.1, shipped in the package and read when this page is built: 118 attachments, of which 95 partial in scope and 23 full. “Partial” means the detector observes one named facet of the control, not the whole control — every attachment carries its own scope note inside the application.

The 4 capabilities, one by one

— display tier: nothing to toggle, the offer is enough

Source: read from the package code at the moment this page is built — FeatureGate.FEATURE_TIER for the offer, FeatureGate.CODE_DEFAULTS for the state at install. The label is the one exception: the in-org feature editor is French only, so the English wording in this column was written for this site. Its French counterpart, on /produit/, is the exact string your administrator reads, and the site build fails if the two lists move apart. “Closed” does not mean absent: the capability is shipped, it is waiting for a human to open it inside the org — and a capability whose implementation nothing in the package can reach appears on none of these pages: the build drops it instead of selling it.

What this family does not do

• This is not legal advice, and the shipped map says so in as many words. The interpretation of an article is subjective and is validated with your compliance team.
• A “partial” attachment is not coverage. It observes the facet its evidence names, and nothing else; every attachment carries its own scope note.
• Procedural controls are never self-assessed. Records of processing, 72-hour notification, processor guarantees, backup and restore, impact assessment: no detector observes them, and the map explicitly leaves them out of scope rather than counting them.
• The attestation is signed by you. We supply timestamped evidence, not certification — and DOPAMINE is itself neither ISO 27001 nor SOC 2, as the publisher security page says.