Obligation inventory
Legal, regulatory and contractual obligations that apply are identified, owned and kept current.
DTCF normalises what an organization must achieve into 10 objectives across 10 families, then maps each to the frameworks practitioners face. Mappings are graded: fully addressed, partially addressed, or deliberately absent with the reason recorded. An empty cell is a finding about the framework, not a gap in your programme.
DTCF 2026.1 · published 10 Sep 2026 · CC BY 4.0 · free to use with attribution
Legal, regulatory and contractual obligations that apply are identified, owned and kept current.
What is in scope for each framework or certification is decided, justified and recorded, including deliberate exclusions.
Data held is inventoried, classified and assigned an owner.
Authentication is proportionate to risk, with multi-factor authentication on administrative and remote access.
Administrative access is limited, separately approved, monitored and time-bound where possible.
Changes to production are requested, reviewed, tested and recorded, with emergency changes reconciled afterwards.
Vulnerabilities are discovered, prioritised by risk and remediated within stated timeframes, with exceptions recorded.
Third parties are assessed before onboarding and periodically thereafter, at a depth proportionate to what they touch.
Every control has one accountable owner and named performers for its tasks.
Findings carry an owner, a date, a remediation and evidence that the fix works.
First edition. Objectives are normalised statements of what an organization must achieve. Mappings are graded: full, partial, or a recorded absence with the reason it is absent. An empty cell is a finding about the framework, not about the objective.
Framework names and references are the property of their publishers. DTCF is an independent mapping and is not endorsed by them. Corrections are welcome through the contact form and are published in the edition changelog.