Vendors Inventory and Attributes - Understand the relationship between the Vendors Inventory and the Integrations Inventory
Vendors Inventory and Attributes
Understand the relationship between the Vendors Inventory and the Integrations Inventory
Integrations connect enterprise systems — and many of those systems are supplied by vendors. The Integrations Inventory and Attributes is published and available. The connection between the Vendors Inventory and the Integrations Inventory is indirect: an integration connects a source entity to a target entity, and those entities may be systems supplied by specific vendors. The Related Integrations attribute in the Vendors Inventory is derived by identifying all integration records where the source or target entity is a system supplied by this vendor.
This relationship surfaces the integration footprint of each vendor — how many integrations depend on systems the vendor supplies. A vendor exit that disrupts a large integration footprint requires extensive remediation planning: every integration where the vendor’s system is a source or target must be remapped to an alternative system before the vendor’s systems can be decommissioned. Without the connection between these two inventories, this remediation scope is invisible until the exit is already underway.
The relationship also surfaces data flow sensitivity at the vendor level. A vendor whose systems participate in integrations carrying PII, PHI, or PCI data has a data handling obligation that extends beyond any single application or contract. The combination of the Vendors Inventory, the Integrations Inventory, and the Data and Information Inventory enables the enterprise to identify every vendor that touches sensitive data through integration flows — a critical capability for privacy impact assessments and breach scope assessment.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers