ISO/IEC 27701 Privacy Information Management System (PIMS)

Privacy Information Management System (PIMS) overview

The European Union’s General Data Protection Regulation (GDPR), has ushered in a new era of privacy regulatory and compliance globally. More privacy regulations, many modeled after the GDPR, have been enacted in different jurisdictions (be that market/industry, or physical location). As a result, organizations must implement policies and procedures to assure compliance with the growing list of privacy regulations. In addition, we are collectively in the midst of rapid digital transformation where data collection and processing are increasing dramatically. The simultaneous growth in data volume and regulatory requirements pertaining to that data makes compliance increasingly complex for organizations of all types.

The new international standard ISO/IEC 27701 Privacy Information Management System (PIMS) (formerly known as ISO/IEC 27552 during drafting period), helps organizations reconcile privacy regulatory requirements. The standard outlines a comprehensive set of operational controls that can be mapped to various regulations, including the GDPR. Once mapped, the PIMS operational controls are implemented by privacy professionals and audited by internal or third-party auditors resulting in a certification and comprehensive evidence of conformity.

Compliance challenges

Expecting vendors to certify against PIMS will be effective for establishing responsible privacy practices by suppliers and partners no matter the size of your organization. ISO/IEC 27701 addresses three key compliance challenges:

  • Too many regulatory requirements to juggle: Reconciling multiple regulatory requirements through the use a universal set of operational controls enables consistent and efficient implementation.
  • Too costly to audit regulation-by regulation: Auditors, both internal and third party, can assess regulatory compliance using a universal operational control set within a single audit cycle.
  • Promise of compliance without proof is potentially risky: Commercial agreements involving movement of personal information may warrant certification of compliance.

Too many regulatory requirements to juggle

ISO/IEC 27701 includes an annex containing the operational controls of the standard that are mapped against relevant requirements in GDPR for controllers and processors. This mapping is just an example of how privacy regulations can be operationalized with the ISO framework. As additional mappings with other regulations become available and are validated, the operational controls from the standard can be transferred directly from regulatory review to implementation. This universal framework allows organizations to reliably operationalize the relevant regulatory requirements without 'reinventing the wheel.' A pending open-source project is underway to enable the privacy community to map other regulations and validate existing mappings. Stay tuned for announcement.

Too costly to audit regulation-by-regulation

Let’s go back to our opening statement on the current landscape. As more privacy regulations come into force in various jurisdictions, the pressure to provide evidence of compliance will also increase. But the costs of disparate regulatory certifications become prohibitive if every regulation calls for its own unique audit. By outlining a set of universal operational controls, PIMS also outlines a universal compliance framework to audit against, and potentially certify, for multiple regulatory requirements.

It is important to recognize that an official GDPR certification requires pending approval decisions to be made by the European regulators. While the alignment between PIMS and GDPR is evident, a PIMS certification should be taken as evidence of GDPR compliance, not as an official GDPR certification until regulatory decisions are finalized.

Promises of compliance without proof is potentially risky

Modern organizations engage in complex data transfers with a deep network of business partners including partner organizations or co-controllers, processors such as cloud providers, and sub-processors such as vendors who support those same processors. Failure to comply with regulations in any part of this network may lead to cascading compliance issues across the supply chain. This is where a verification of compliance can be valuable beyond the assurance provided by contractual terms between these organizations. Since the global economy dictates that most of these organizations are spread out around the world, it is practical to use an international standard from ISO to manage compliance across the network.

This reliance on compliance increases the importance of certification to the standard. While not all companies and organizations need to earn such certification, most will benefit from partners and vendors who do, especially when sensitive or high volumes of data processing are involved.

Building blocks of the standard

PIMS is built on top of one of the most widely adopted international standards for information security management, ISO/IEC 27001. If your organization is already familiar with ISO/IEC 27001, it is logical and more efficient to integrate the new privacy controls of PIMS. This means the implementation and audit of both will be less expensive and easier to achieve.

Key points on ISO/IEC 27001 and PIMS:

  • ISO/IEC 27001 is one of the most used ISO standards in the world, with many companies already certified to it.
  • PIMS includes new controller- and processor-specific controls that help bridge the gap between privacy and security and provides a point of integration between what may be two separate functions in organizations.
  • Privacy depends on security. Likewise, PIMS depends on ISO/IEC 27001 for security management. Certification for PIMS must be obtained as an extension of an ISO/IEC 27001 certification and cannot be obtained independently.

What should your organization do with PIMS?

No matter the size of your organization and whether it is a controller or a processor, your organization should consider pursuing certification, either for your own organization, or requesting it from vendors or suppliers based on your business requirements. This applies especially for processors, sub-processors, and co-controllers that are processing sensitive or high volumes of personal data. In any case, your organization should assess its business needs to determine if certification for its own products and services is suitable.

Microsoft in-scope cloud services

  • Azure, Azure Government, and Azure Germany
  • Azure DevOps Services
  • Microsoft Cloud App Security
  • Dynamics 365, Dynamics 365 Government, and Dynamics 365 Germany
  • Microsoft Graph
  • Microsoft Healthcare Bot
  • Intune
  • Microsoft Managed Desktop
  • Power Automate (formerly Microsoft Flow)
  • PowerApps
  • Power BI
  • Power BI Embedded
  • Power Virtual Agents
  • Microsoft Stream
  • Microsoft Threat Experts
  • Windows Defender Advanced Threat Protection

Audits, reports, and certificates

Use Microsoft Compliance Score to assess your risk

Microsoft Compliance Score is a preview feature in the Microsoft 365 compliance center to help you understand your organization’s compliance posture and take actions to help reduce risks. After setting up Compliance Score, select the pre-configured ISO 27701 template from the Template drop-down menu to help your organization meet the requirements for this regulation.

Resources