Law / Frameworks / NIST CSF 2.0 / Protect
NIST CSF 2.0, ProtectPR.DS-02
The confidentiality, integrity, and availability of data-in-transit are protectedNIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), PR.DS-02
We read each law below as bearing on this control. That does not mean the control, done well, meets the law: what each law asks is on its own page. Law library as of .
- 9
- laws
- 8
- jurisdictions
- 0
- with court rulings behind them
- 0
- not yet in force
Related controls in other frameworks the same duties, in at least two laws we track, reach both
- NIST Privacy FrameworkPR.DS-P2 Data-in-transit are protected., 5 laws
- NIST Privacy FrameworkPR.DS-P5 Protections against data leaks are implemented., 2 laws
- FINOS AIGFAIR-PREV-007 Legal and Contractual Frameworks for AI Systems, 8 laws
- FINOS AIGFAIR-PREV-008 Quality of Service (QoS) and DDoS Prevention for AI Systems, 8 laws
- FINOS AIGFAIR-PREV-012 Role-Based Access Control for AI Data, 8 laws
- 4 more in the FINOS AIGF
- ENISA NIS2 guidance2.1 Risk management framework, 8 laws
- ENISA NIS2 guidance3.1 Incident handling policy, 8 laws
- ENISA NIS2 guidance4.1 Business continuity and disaster recovery plan, 8 laws
- 5 more in the ENISA NIS2 guidance
Sector security regimes
6 laws, 5 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Payment Services Technical Standards on Strong Customer Authentication, Personalized Security Credentials and Common and Secure Open Standards of Communication |
For identification, rely on qualified certificates for electronic seals or for website authentication under Regulation (EU) No 910/2014 that include the additional attributes in Article 34(3) (Article 34). When exchanging data over the internet, apply secure encryption with strong and widely recognized encryption techniques throughout the communication session. If you issue card-based payment instruments or are an account information service provider or a payment initiation service provider, keep the access sessions offered by account servicing payment service providers as short as possible and terminate them as soon as the requested action is completed. Keep personalized security credentials and authentication codes unreadable, directly or indirectly, by any staff at any time, and inform the payment services user and the issuer of the credentials without undue delay of any loss of their confidentiality under your sphere of competence (Article 35). |
|
| Telekommunikationsgesetz (TKG), Section 165 Technical and Organisational Protective Measures |
If you provide telecommunications services or contribute to them, take appropriate technical precautions and other measures, taking the state of the art into account, to protect the secrecy of telecommunications and against personal-data breaches (Section 165(1)). |
|
| Wertpapierhandelsgesetz (WpHG), Section 80 ICT Systems and Security Mechanisms of Investment Services Firms |
Have sound security mechanisms to meet the requirements of Regulation (EU) 2022/2554 that secure and authenticate the channels of information transfer, minimise the risk of data corruption and unauthorised access and prevent information leaks, so that the confidentiality of data is always ensured (Section 80(1) sentence 2 number 4). |
|
| New York Department of Financial Services Cybersecurity Regulation, Encryption of Nonpublic Information |
Implement a written policy requiring encryption that meets industry standards, to protect the nonpublic information you hold or transmit both in transit over external networks and at rest. |
|
| Law on Information Security, ICT Systems of Special Importance and Security Measures |
Take technical, operational, organisational and physical protection measures across the areas Article 10 lists, including multi-factor authentication or a continuous-authentication solution, secured voice, video and text communication, and secured communication channels for emergencies. |
|
| Law No. 40 of 2006 on Electronic Payment Systems and Financial and Banking Operations, Secure-Services and Banking-Confidentiality Duty |
Take the measures necessary to provide secure services to customers and preserve banking confidentiality when conducting an electronic funds transfer. |
Security baseline statutes
3 laws, 3 jurisdictions| Jurisdiction | Law | What it asks, as read here |
|---|---|---|
| Data Classification Policy |
Encrypt Tier 3 (Private Sensitive) and Tier 4 (Highly Sensitive) data whenever you transmit it between physical locations. |
|
| Standards for the Protection of Personal Information of Residents of the Commonwealth |
For personal information you store or transmit electronically, build a computer-system security program with secure user authentication, access controls limiting records to those who need them, encryption of records transmitted across public networks or wirelessly and of personal information stored on a laptop or other portable device, up-to-date firewalls and operating-system security patches for any internet-connected system, up-to-date malware protection, and employee training on the security system. |
|
| Security measures for a data collector accepting payment cards, encryption duty, and conditioned liability shield |
If you do not accept payment cards, do not transfer a Nevada resident's personal information through an electronic, nonvoice transmission other than a facsimile outside your secure system, and do not move a data storage device containing that personal information beyond your logical or physical controls, unless the data is encrypted using an encryption technology adopted by an established standards-setting body, with appropriate management and safeguards of the cryptographic keys. |
Full text of the NIST Cybersecurity Framework, public domain (a US government work). Every control of the framework.