Integrations Inventory and Attributes - Security attributes for the Integrations Inventory

Integrations Inventory and Attributes

Security attributes for the Integrations Inventory

Security attributes capture the sensitivity of data moving through this Integration and the access controls governing the integration channel.

Attribute Name	Maturity	Description and Notes
Data Sensitivities [Multi-Value]	Crawl	Description — The sensitivity classifications of the data or information transmitted through this integration. A single integration may carry multiple sensitivity types simultaneously. Benefit(s) — Enables per-integration sensitivity governance rather than entity-level approximation. Two applications may have five integrations between them but only one that transmits PII — this attribute makes that distinction explicit and actionable for privacy impact assessments, regulatory audits, and encryption enforcement. Source — Manual. Examples — PII; PHI; PCI; PFI; Confidential; Regulated; None Notes — Valid values: PII (Personally Identifiable Information), PHI (Protected Health Information), PCI (Payment Card Industry data), PFI (Protected Financial Information), Confidential (internal sensitive but not regulated), Regulated (subject to regulatory handling requirements not covered by the above), None (no sensitive data transmitted). Separate multiple values with semicolons. None is an explicit governance statement — do not leave this field blank.

Attribute Name

Maturity

Description and Notes

Data Sensitivities

[Multi-Value]

Crawl

Description — The sensitivity classifications of the data or information transmitted through this integration. A single integration may carry multiple sensitivity types simultaneously.

Benefit(s) — Enables per-integration sensitivity governance rather than entity-level approximation. Two applications may have five integrations between them but only one that transmits PII — this attribute makes that distinction explicit and actionable for privacy impact assessments, regulatory audits, and encryption enforcement.

Source — Manual.

Examples — PII; PHI; PCI; PFI; Confidential; Regulated; None

Notes — Valid values: PII (Personally Identifiable Information), PHI (Protected Health Information), PCI (Payment Card Industry data), PFI (Protected Financial Information), Confidential (internal sensitive but not regulated), Regulated (subject to regulatory handling requirements not covered by the above), None (no sensitive data transmitted). Separate multiple values with semicolons. None is an explicit governance statement — do not leave this field blank.

Legal Disclaimers