Skip to content
Menu
Cloud Gal 42
  • Home
Cloud Gal 42

Data Privacy: Maturity Model

June 20, 2021June 24, 2021 by admin

Previous article in series – Data Privacy: Standard Requirements

Maturity models are a recognized means by which organizations can measure their progress against established benchmarks. As such, they recognize that:

  • Becoming compliant is a journey and progress along the way strengthens the organization, whether the organization has achieved all of the requirements or not
  • In certain cases, such as security-focused maturity models, not every organization, or every security application, needs to be at the maximum for the organization to achieve an acceptable level of security
  • Creation of values or benefits may be possible if they achieve a higher maturity level

The AICPA/CICA Privacy Maturity Model is based on GAPP and the Capability Maturity Model (CMM). The PMM uses five maturity levels as follows:

  1. Ad hoc: Procedures or processes are generally informal, incomplete, and inconsistently applied
  2. Repeatable: Procedures or processes exist; however, they are not fully documented and do not cover all relevant aspects
  3. Defined: Procedures and processes are fully documented and implemented and cover all relevant aspects
  4. Managed: Reviews are conducted to assess the effectiveness of the controls in place
  5. Optimized: Regular review and feedback are used to ensure continuous improvement towards optimization of the given process

In developing the PMM, it was recognized that each organization’s personal information privacy practices may be at various levels, whether due to legislative requirements, corporate policies, or the status of the organization’s privacy initiatives. It was also recognized that, based on an organization’s approach to risk, not all privacy initiatives would need to reach the highest level on the maturity model.

Reference: https://iapp.org/media/pdf/resource_center/aicpa_cica_privacy_maturity_model_final-2011.pdf

Privacy-Level Agreements (PLAs)

The Cloud Security Alliance (CSA) has a document that provides a baseline for complying with various frameworks and legislative mandates concerning data privacy. The PLA provides a basis for communication between service provider and consumer where documentation exists related to how the provider protects the data. With clear and concise communication, the proper level of protection is understood and known, compliance with legislative requirements is maintained, and legal pitfalls related to lack of compliance can be avoided.

Next article in series – Data Privacy: Difference Between Data Owner/Controller and Data Custodian/Processor

Related

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Role of AI/ML in Cybersecurity
  • QuickGuide: Security on OCI
  • The Cloud Management Plane
  • Secure Installation and Configuration of Virtualized Cloud Datacenters
  • Cloud Datacenter: Hardware-specific Security Configuration Requirements

Recent Comments

  • Rafael on Installing Debian on OCI
  • Jorge on Installing Debian on OCI
  • admin on Installing Debian on OCI
  • Andreas on Installing Debian on OCI
  • admin on Installing Debian on OCI

Archives

  • December 2022
  • February 2022
  • September 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • February 2021
  • January 2021
  • November 2020
  • October 2020

Categories

  • aws
  • bcdr
  • cloud
  • cloudsecurity
  • compliance
  • informationsecurity
  • oracle
  • pci
  • QuickGuide
  • security
©2025 Cloud Gal 42 | Powered by WordPress and Superb Themes!