Regulatory Agencies Inventory and Attributes - Relationship attributes for the Regulatory Agencies Inventory
Regulatory Agencies Inventory and Attributes
Relationship attributes for the Regulatory Agencies Inventory
Relationship attributes connect each Regulatory Agency to related Noun Instances in other inventories — the regulations, obligations, data types, integrations, vendors, and child agencies it governs or supervises.
Every attribute in this category is Derived from or Calculated from records in other inventories, with the exception of Parent Agency which is manually populated at Walk maturity. Do not create data entry fields for Derived or Calculated attributes.
| Attribute Name | Maturity | Description and Notes |
|---|---|---|
Related Regulations [Multi-Value] | Run | Description — Regulations in the Regulations Inventory published or enforced by this agency, referenced by Semantic ID. The primary downstream cross-inventory relationship — the governing link from regulatory authority to the specific regulations the enterprise must comply with. Benefit(s) — Enables traversal from regulatory agency to specific compliance obligations in a single path. Once the Regulations Inventory is published, this relationship makes the Regulatory Agencies Inventory the root of the compliance governance hierarchy: Agency → Regulations → Obligations. Source — Derived. Notes — Derived from the Regulations Inventory when published: all Regulation records whose Issuing Agency attribute references this agency’s Semantic ID. The Regulations Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. |
Related Regulatory Obligations [Multi-Value] | Run | Description — Specific compliance obligations in the Regulatory Obligations Inventory derived from this agency’s regulations, referenced by Semantic ID. Benefit(s) — Enables direct traversal from regulatory agency to specific compliance controls and evidence requirements — the operational level of the compliance governance hierarchy. Source — Derived. Notes — Derived from the Regulatory Obligations Inventory when published. The Regulatory Obligations Inventory is not yet published — refer to the IF4IT Enterprise Inventory Management Best Practices document. |
Related Data and Information Types [Multi-Value] | Run | Description — Data and Information types in the Data and Information Inventory that are subject to this agency’s jurisdiction — the specific classes of data the agency governs. Referenced by Semantic ID. Benefit(s) — Connects the regulatory governance layer to the data governance layer. Enables the enterprise to answer: which data types are governed by this agency? Which systems handling those data types are subject to this agency’s requirements? Source — Derived. Notes — Derived from the Data and Information Inventory: all Data and Information types whose Regulatory Obligations attribute references obligations from this agency. The Data and Information Inventory and Attributes is published and available. |
Related Integrations [Multi-Value] | Run | Description — Integration records in the Integrations Inventory subject to this agency’s requirements — integrations carrying data types governed by this agency. Referenced by Semantic ID. Benefit(s) — Connects regulatory governance to data flow governance. Enables the enterprise to identify which integrations are in scope for a regulatory audit or compliance review: all integrations carrying personal data governed by a GDPR supervisory authority, or all integrations handling financial data governed by a financial regulator. Source — Derived. Notes — Derived from the Integrations Inventory through the data type linkage: integrations whose Data Sensitivities or Integration Payload references data types governed by this agency. The Integrations Inventory and Attributes is published and available. |
Related Vendors [Multi-Value] | Run | Description — Vendor records in the Vendors Inventory for vendors that are regulated entities under this agency or that supply services subject to this agency’s oversight. Referenced by Semantic ID. Benefit(s) — Connects vendor governance to regulatory governance. Enables the enterprise to identify which vendor relationships are subject to a specific regulatory agency’s oversight — particularly relevant for financial sector regulators with direct vendor oversight authority (DORA, FCA) and for data protection authorities governing data processor relationships. Source — Derived. Notes — Derived from the Vendors Inventory when the regulatory agency relationship is formally established. The Vendors Inventory and Attributes is published and available. |
| Parent Agency | Walk | Description — The Semantic ID of the parent or supervising regulatory body for this agency, where a formal supervisory or hierarchical relationship exists. Self-referential within the Regulatory Agencies Inventory. Benefit(s) — Captures the hierarchical structure of the global regulatory landscape. Requirements from supranational bodies flow down through national agencies; national agencies supervise state or regional bodies. Understanding this hierarchy is essential for determining which agency’s interpretation of a requirement is authoritative when national and supranational requirements diverge. Source — Manual. Examples — REG-EU-EDPB (parent of each EU member state’s national data protection authority); REG-US-FSOC (parent of member U.S. financial regulators); REG-INTL-BCBS (Basel Committee, parent of national banking regulators) Notes — Leave empty for agencies with no formal parent body. For EU member state supervisory authorities under GDPR, the EDPB is the supervising body but also a peer body — document the relationship accurately based on the formal governance structure. |
Related Child Agencies [Multi-Value] | Run | Description — The Semantic IDs of agencies that are formally supervised by or subordinate to this agency in the regulatory hierarchy. Inverse of Parent Agency. Calculated from within the Regulatory Agencies Inventory. Benefit(s) — Enables top-down traversal of the regulatory hierarchy: from a supranational body to all national agencies under its jurisdiction, to all regional agencies under each national agency. Essential for understanding how regulatory requirements propagate through the governance hierarchy. Source — Calculated. Notes — Calculated from within the Regulatory Agencies Inventory: all records whose Parent Agency attribute references this agency’s Semantic ID. Self-referential. |
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers