Data Mapping
The process of documenting how data flows through an organization, including what data is collected, where it is stored, how it is processed, and with whom it is shared.
On this page
What is Data Mapping?
Data mapping (or data flow mapping) creates a visual representation of data movement across systems, processes, and third parties. It documents data sources, types, storage locations, processing activities, access controls, retention periods, and cross-border transfers. Data mapping is required by GDPR (Article 30 Records of Processing Activities) and is foundational for privacy impact assessments, security planning, and vendor management. It reveals vendor data dependencies and potential exposure points.
Application to Vendor Screening
Data mapping identifies which vendors receive what types of data, how data flows between your organization and vendors, and where vendor-processed data is stored. This information is essential for vendor risk assessment, data privacy compliance, and incident response planning.
Practical Examples
- Creating a data flow diagram showing personal data shared with each vendor
- Identifying that a vendor transfers data to sub-processors in multiple countries
- Using data mapping to complete GDPR Article 30 records for vendor processing
Frequently Asked Questions
Why is data mapping important for vendor management?
Data mapping reveals what data vendors access, where they process it, who they share it with, and how it flows. This information drives risk assessment, contract requirements, and compliance with data privacy regulations.
How often should data maps be updated?
At least annually, and whenever there are significant changes to data processing activities, new vendor engagements, or changes in vendor sub-processors. Automated discovery tools can help maintain current maps.