Reference — Verified Available now
Supported control types
Verified covers a specific set of control categories, each backed by one typed assertion in ComplianceAssertions. These four are what’s supported today.
| Control category | What it covers | Assertion method |
|---|---|---|
| Consent capture | A user’s consent is recorded with a valid GDPR lawful basis. | assertConsentRecorded |
| Encryption at rest | Data is encrypted with a strong authenticated algorithm before it’s persisted. | assertEncrypted |
| Data retention / deletion | A record is deleted or expired within a defined, sane retention period. | assertRetentionEnforced |
| Access logging | Access to a resource by a given actor is logged. | assertAccessLogged |
Need to verify a control that isn’t in this list? Tell us — the set grows based on what design partners actually need to verify, not a pre-drawn roadmap.
Framework mapping
Which framework citation applies to each category depends on your own
control matrix, so this page doesn’t hard-code one. The
@ComplianceControl examples show
two real mappings: consent capture to GDPR:Art.30 and
encryption at rest to SOC2:CC6.1.
Related
- The assertion library — full method reference.
- @VerifiesControl — how a test is linked to a control.