CSA CCM DSP-11
Personal Data Access, Reversal, Rectification and Deletion

In today's data-driven world, organizations must respect individual privacy rights and provide mechanisms for data subjects to access, modify, and delete their personal information. The Personal Data Access, Reversal, Rectification and Deletion control ensures that companies have well-defined processes and procedures in place to handle data subject requests efficiently and in compliance with applicable laws and regulations. By implementing this control, organizations demonstrate their commitment to data privacy and build trust with their customers.

Where did this come from?

This control comes from the CSA Cloud Controls Matrix v4.0.10 - 2023-09-26. You can download the full matrix here. The Cloud Security Alliance developed this control as part of their ongoing effort to provide a comprehensive framework for securing cloud computing environments. For more information on AWS's approach to data privacy, check out their Data Privacy FAQ.

Who should care?

  • Privacy Officers responsible for ensuring compliance with data protection regulations
  • Application Developers building systems that process personal data
  • Customer Support Representatives handling data subject requests
  • Legal Teams advising on data privacy obligations

What is the risk?

Failing to provide data subjects with the ability to access, modify, or delete their personal data can lead to:

  • Regulatory fines and penalties for non-compliance with data protection laws
  • Reputational damage and loss of customer trust
  • Inability to fulfill contractual obligations with customers or partners

Implementing this control helps mitigate these risks by ensuring that the organization has a well-defined process for handling data subject requests and can demonstrate compliance with applicable regulations.

What's the care factor?

Organizations should prioritize this control if they:

  • Process personal data of individuals in jurisdictions with strict data protection laws (e.g., EU, California)
  • Operate in industries with heightened privacy concerns (e.g., healthcare, finance)
  • Have a large customer base or handle high volumes of personal data

Failure to comply with data subject requests can result in significant financial penalties and damage to brand reputation, making this control a high priority for many organizations.

When is it relevant?

This control is relevant whenever an organization processes personal data and is subject to data protection regulations that grant individuals the right to access, modify, or delete their information. It may not be relevant for organizations that only process anonymized or aggregated data that cannot be linked back to specific individuals.

What are the trade-offs?

Implementing processes and systems to handle data subject requests can be time-consuming and resource-intensive. It may require:

  • Developing custom workflows and user interfaces for data subject interactions
  • Modifying existing systems to enable data access, modification, and deletion
  • Training staff on data privacy requirements and request handling procedures

These investments may divert resources from other business priorities, but they are necessary for compliance and maintaining customer trust.

How to make it happen?

  1. Identify all systems and processes that handle personal data
  2. Document the types of personal data processed and the purposes for processing
  3. Develop a data subject request workflow that includes:
    • Verification of the data subject's identity
    • Confirmation of the specific data being requested
    • Timeframes for responding to requests
    • Escalation procedures for complex cases
  4. Implement technical measures to enable data access, modification, and deletion, such as:
    • APIs for retrieving and updating personal data
    • User interfaces for data subjects to view and manage their information
    • Audit trails to record request fulfillment activities
  5. Train relevant staff on the data subject request process and their responsibilities
  6. Communicate the availability and process for making data subject requests to customers
  7. Monitor compliance with data subject request timeframes and other requirements

What are some gotchas?

  • Ensuring that only authorized individuals can access, modify, or delete personal data may require implementing strong authentication and access control measures. This may involve granting specific permissions like cognito-idp:AdminGetUser to customer support staff. See the Cognito API Permissions Reference for details.
  • Deleting personal data may conflict with other regulatory requirements (e.g., data retention laws) or business needs (e.g., fraud detection). Organizations need to carefully assess these competing obligations.
  • Data subjects may request access to information that is not readily available in structured form (e.g., call recordings, chat logs). Extracting and providing this data can be challenging.

What are the alternatives?

Some organizations may choose to outsource the handling of data subject requests to specialized service providers. These providers offer tools and expertise to streamline the request management process and ensure compliance with applicable regulations. However, the organization remains ultimately responsible for fulfilling data subject rights.

Explore further

  • GDPR Article 15: Right of access by the data subject
  • GDPR Article 16: Right to rectification
  • GDPR Article 17: Right to erasure ('right to be forgotten')
  • CCPA Section 1798.100: Right to access personal information
  • CCPA Section 1798.105: Right to delete personal information
  • CIS Control 13: Data Protection - Manage the data lifecycle to ensure integrity and protection of corporate data from creation through destruction.

?

Blog

Learn cloud security with our research blog