ISO 27701:2019
PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:2019

ISO 27701:2019 6.11.1: Security requirements of information systems

Security requirements analysis and specification and the protection of application services transactions apply as the base guidance requires, and personal data transmitted over untrusted networks, including the public internet and any facility outside the organization's operational control, must be encrypted for transmission.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 65 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 16 controls

ISO 27002:2022 · 5 controls

  • 0.2 Information security requirements
  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles
  • 8.29 Security testing in development and acceptance

CIS Controls v8 · 4 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-16.14 Conduct Threat Modeling
  • CIS-3.10 Encrypt Sensitive Data in Transit

HIPAA Security Rule · 4 controls

ISO 27001:2022 · 4 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles
  • 8.32 Change management

NIST SP 800-66 Rev 2 · 4 controls

FedRAMP High · 3 controls

  • SA-4 Acquisition Process
  • SC-23 Session Authenticity
  • SC-8(1) Cryptographic Protection

FedRAMP Moderate · 3 controls

  • SA-4 Acquisition Process
  • SC-23 Session Authenticity
  • SC-8(1) Cryptographic Protection
  • NIST-CSF-GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

PCI DSS 4.0 · 3 controls

  • 4.2.1 4.2.1 Strong cryptography safeguards PAN over public networks
  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.2.4 6.2.4 Engineering techniques against common software attacks

C5 (Germany) · 2 controls

  • C5-CRY-02 Encryption of data for transmission (transport encryption)
  • C5-DEV-01 Policies for the development/procurement of information systems

NIST SP 800-161 Rev 1 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-PI1.4 PI1.4 Controls over output delivery
  • AEO-9 Information Exchange, Access and Confidentiality

CMMC 2.0 · 1 control

ISO 27017:2015 · 1 control

  • 14.1 Security requirements of information systems
  • 03.16.01 Security Engineering Principles

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:2019

You are reading one control. How much of ISO 27701:2019 have you already done?

ISO 27701:2019 6.11.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27701:2019 your existing evidence covers. Hold SOC 2 and 58 of 108 ISO 27701:2019 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 289 were rejected on the SOC 2 pair alone.

Query this from an agent

The graph holds this control, the 65 it maps to, and the evidence behind each claim, over MCP and REST.