Security/Guidelines/Key Management
The goal of this document is to help operational teams with the handling and management of cryptographic material. All Mozilla sites and deployment should follow the recommendations below. The Operations Security (OpSec) team maintains this document as a reference guide for operational teams.
 |
Data classification and handling
Key material
Key material identifies the cryptographic secrets that compose a key. All key material must be treated as restricted data, meaning that only individual with specific training and need-to-know should have access to key material. Key material must be encrypted on transmission. Key material can be stored in clear text, but with proper access control.
Public certificates
Public certificates are public and do not require specific access control or encryption.
Algorithms by security levels
This section organizes algorithms and key sizes for a given validity period that represent the level of security provided. While 10 years validity may be a requirement for very static keys, such as Root CAs, we do recommend preferring 2 years keys and implementing reliable key rotation, instead of trying to keep key material for long periods of time.
10 years
| Type | Algorithm and key size |
|---|---|
| Asymmetric keys | RSA 4096 bits |
| Asymmetric keys | ECDSA 384 bits |
| Hash | SHA-512 |
| Hash | SHA3-256 |
2 years
| Type | Algorithm and key size |
|---|---|
| Asymmetric keys | RSA 2048 bits |
| Asymmetric keys | ECDSA 224 or 256 bits |
| Hash | SHA-256 |
Legacy, not recommended
The following algorithms and sizes are still widely used but do not provide sufficient security for modern services and should be deprecated as soon as possible, unless backward compatibility is a requirement.
| Type | Algorithm and key size |
|---|---|
| Asymmetric keys | RSA 1024 bits and below |
| Asymmetric keys | ECDSA 160 bits and below |
| Hash | SHA-1 |
| Hash | MD5 |