Ten Essential Attributes To Capture In GDPR / CCPA Data Mapping

Master GDPR/CCPA data mapping with Protecto's 10 essential attributes guide.
Written by
Protecto

Table of Contents

Share Article

Data protection requirements vary based on the nature of the data hence organizations must have a comprehensive and accurate data map of what data they collect, store, and process. Here is a quick list of attributes that companies should collect as part of their data discovery process. A data mapping process is typically long and resource-intensive hence having a good list of attributes reduces rework. The goal of a data mapping process is to help companies discover personal data and map various data processing activities. 

Following attributes capture what data they collect, use, share inside their organization and transfer outside the organization.

  1. Data Inventory – What are the data sources and data assets that we collect? What sensitive /personal data does the data sources hold?
  2. Storage – Where is the data stored? Is it secure and encrypted?
  3. Security – Is it stored secure and encrypted?
  4. Data Sources/Data lineage –  What data sources of the data assets? If it is an application, what application generates the data? What data assets were combined or transformed to derive a data asset?
  5. Purpose – What business purposes did we collect the data for? Does it have proper consent?
  6. Data Subject Attributes – Additional metadata needed for data protection
  7. What are the categories of the data subject (customer, employee, partner, contractor) in the data asset?
  8. What is the geographical location of data subjects in the data?
  9. Does the data contain a minor’s data?
  10. Lifespan – When was it created? How long will data be stored? How will it be disposed of?
  11. Processing  – Who has access to the data? Who is using the data? Where is the data processed?
  12. Data Transfer– Where does the data flow? Who do we share or transfer data outside the organization?
  13. Data Owner/Steward – Who or what team is responsible for the data?
Protecto

Related Articles

What is Role-Based Access Control (RBAC)? A Complete Guide

What Is a Prompt Injection Attack? Explained

What is a Prompt Injection Attack?

Protecting Against Prompt Injection at the Data Layer, Not the Prompt Layer

Prompt injection is often treated as a prompt engineering problem. It is not. When untrusted data is allowed to shape model behavior without clear boundaries, the system becomes fragile. This post explores why defending at the prompt layer is fundamentally reactive, and how shifting protection to the data layer creates a more durable, principled security model for AI systems....
Protecto SaaS is LIVE! If you are a startup looking to add privacy to your AI workflows
Learn More