[HDDS-10234] Regulatory compliance for used cryptography

• Type: Epic
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: pull-request-available
• Epic Name: crypto-compliance
• Assignee: István Fajth
• Reporter: István Fajth
• Created: 29/Jan/24 16:44
• Updated: 26/Jun/24 16:10

Description

In various jurisdictions there are some restrictions on using different cryptographic functions, algorithms, cyphers etc.

There is an international standard issued by ISO under ISO/IEC 19790.

In the US, FIPS 140-3 is based off of the ISO standard, hence it is an easy starting point also considering the fact that most of the legislation probably moves towards the standard rather than creating a new one.
In China, there is the "China Cryptograhy law" that also contains different rules for different security levels.
In the EU the legislators are still debating about how to apply rules in order to protect privacy, but fight crime effectively (esp. child abuse).
Probably there are many more around the world.

This JIRA is about having an umbrella for crypto and security compliance related changes.

Issue Links

• is related to: HDDS-10919 Change ozone.security.crypto.compliance.mode default value in ozone-default.xml
• relates to: HDDS-10744 Standardize byte array conversion to String for LiveFileMetaData in RocksDB
• links to: GitHub Pull Request #6685