Integrations Inventory and Attributes - IT Environment attributes for the Integrations Inventory

Integrations Inventory and Attributes

IT Environment attributes for the Integrations Inventory

IT Environment attributes capture the specific operating environments of the source and target entities — the environment-pair that defines where this Integration runs.

Attribute Name	Maturity	Description and Notes
Source Environment	Crawl	Description — The IT operating environment in which the source entity resides for this integration record. External is a valid value, indicating the source entity exists outside the enterprise boundary. Benefit(s) — Enables cross-environment integration governance. Without Source Environment, the Integrations Inventory cannot distinguish a Production-to-Production integration (live operational dependency) from a Production-to-UAT integration (test data flow requiring data sanitization governance) or an External-to-Production integration (inbound third-party feed requiring enhanced security controls). Source — Manual. Examples — Development, Systems Integration Testing, User Acceptance Testing, Production, Disaster Recovery, External Notes — External indicates the source entity is outside the enterprise boundary — a third-party partner, regulator, customer, or external service provider. When Source Environment = External, evaluate the integration for Cross-Border Data Flow and Data Sensitivities governance.
Target Environment	Crawl	Description — The IT operating environment in which the target entity resides for this integration record. External is a valid value, indicating the target entity exists outside the enterprise boundary. Benefit(s) — Completes the environment-pair governance picture. The combination of Source Environment and Target Environment for every integration record produces the enterprise’s complete cross-environment data flow map — including Production-to-non-Production flows that require data sanitization and External-facing flows that require enhanced security governance. Source — Manual. Examples — Development, Systems Integration Testing, User Acceptance Testing, Production, Disaster Recovery, External Notes — Mirror of Source Environment. The query "Source Environment = Production AND Target Environment ≠ Production" immediately surfaces all Production-to-non-Production integrations — a critical data privacy audit list.

Attribute Name

Maturity

Description and Notes

Source Environment

Crawl

Description — The IT operating environment in which the source entity resides for this integration record. External is a valid value, indicating the source entity exists outside the enterprise boundary.

Benefit(s) — Enables cross-environment integration governance. Without Source Environment, the Integrations Inventory cannot distinguish a Production-to-Production integration (live operational dependency) from a Production-to-UAT integration (test data flow requiring data sanitization governance) or an External-to-Production integration (inbound third-party feed requiring enhanced security controls).

Source — Manual.

Examples — Development, Systems Integration Testing, User Acceptance Testing, Production, Disaster Recovery, External

Notes — External indicates the source entity is outside the enterprise boundary — a third-party partner, regulator, customer, or external service provider. When Source Environment = External, evaluate the integration for Cross-Border Data Flow and Data Sensitivities governance.

Target Environment

Crawl

Description — The IT operating environment in which the target entity resides for this integration record. External is a valid value, indicating the target entity exists outside the enterprise boundary.

Benefit(s) — Completes the environment-pair governance picture. The combination of Source Environment and Target Environment for every integration record produces the enterprise’s complete cross-environment data flow map — including Production-to-non-Production flows that require data sanitization and External-facing flows that require enhanced security governance.

Source — Manual.

Examples — Development, Systems Integration Testing, User Acceptance Testing, Production, Disaster Recovery, External

Notes — Mirror of Source Environment. The query "Source Environment = Production AND Target Environment ≠ Production" immediately surfaces all Production-to-non-Production integrations — a critical data privacy audit list.

Legal Disclaimers