Skip to content

Commit 0cf5da8

Browse files
committed
Restored about keys secrets certs article
1 parent 5aa40ee commit 0cf5da8

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

articles/key-vault/keys/about-keys.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,23 @@ ms.author: mbaldwin
1717

1818
Azure Key Vault Supports multiple key types and algorithms, and enables the use of Hardware Security Modules (HSM) for high value keys.
1919

20-
Cryptographic keys in Key Vault are represented as JSON Web Key [JWK] objects. The base JWK/JWA specifications are also extended to enable key types unique to the Key Vault implementation. For example, importing keys using HSM vendor-specific packaging, enables secure transportation of keys that may only be used in Key Vault HSMs.
20+
Cryptographic keys in Key Vault are represented as JSON Web Key [JWK] objects. The JavaScript Object Notation (JSON) and JavaScript Object Signing and Encryption (JOSE) specifications are:
21+
22+
- [JSON Web Key (JWK)](https://tools.ietf.org/html/draft-ietf-jose-json-web-key)
23+
- [JSON Web Encryption (JWE)](http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption)
24+
- [JSON Web Algorithms (JWA)](http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms)
25+
- [JSON Web Signature (JWS)](https://tools.ietf.org/html/draft-ietf-jose-json-web-signature)
26+
27+
The base JWK/JWA specifications are also extended to enable key types unique to the Key Vault implementation. For example, importing keys using HSM vendor-specific packaging, enables secure transportation of keys that may only be used in Key Vault HSMs.
28+
29+
Azure Key Vault supports both Soft and Hard keys:
2130

2231
- **"Soft" keys**: A key processed in software by Key Vault, but is encrypted at rest using a system key that is in an HSM. Clients may import an existing RSA or EC (Elliptic Curve) key, or request that Key Vault generate one.
2332
- **"Hard" keys**: A key processed in an HSM (Hardware Security Module). These keys are protected in one of the Key Vault HSM Security Worlds (there's one Security World per geography to maintain isolation). Clients may import an RSA or EC key, in soft form or by exporting from a compatible HSM device. Clients may also request Key Vault to generate a key. This key type adds the key_hsm attribute to the JWK obtain to carry the HSM key material.
2433

25-
For more information on geographical boundaries, see [Microsoft Azure Trust Center](https://azure.microsoft.com/support/trust-center/privacy/)
34+
For more information on geographical boundaries, see [Microsoft Azure Trust Center](https://azure.microsoft.com/support/trust-center/privacy/)
35+
36+
## Cryptographic protection
2637

2738
Key Vault supports RSA and Elliptic Curve keys only.
2839

@@ -33,17 +44,6 @@ Key Vault supports RSA and Elliptic Curve keys only.
3344

3445
Key Vault supports RSA keys of sizes 2048, 3072 and 4096. Key Vault supports Elliptic Curve key types P-256, P-384, P-521, and P-256K (SECP256K1).
3546

36-
## Supporting standards
37-
38-
The JavaScript Object Notation (JSON) and JavaScript Object Signing and Encryption (JOSE) specifications are important background information.
39-
40-
- [JSON Web Key (JWK)](https://tools.ietf.org/html/draft-ietf-jose-json-web-key)
41-
- [JSON Web Encryption (JWE)](http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption)
42-
- [JSON Web Algorithms (JWA)](http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms)
43-
- [JSON Web Signature (JWS)](https://tools.ietf.org/html/draft-ietf-jose-json-web-signature)
44-
45-
## Cryptographic protection
46-
4747
The cryptographic modules that Key Vault uses, whether HSM or software, are FIPS (Federal Information Processing Standards) validated. You don't need to do anything special to run in FIPS mode. Keys **created** or **imported** as HSM-protected are processed inside an HSM, validated to FIPS 140-2 Level 2. Keys **created** or **imported** as software-protected, are processed inside cryptographic modules validated to FIPS 140-2 Level 1.
4848

4949
## EC algorithms
@@ -113,7 +113,7 @@ Users may restrict any of the cryptographic operations that Key Vault supports o
113113

114114
For more information on JWK objects, see [JSON Web Key (JWK)](https://tools.ietf.org/html/draft-ietf-jose-json-web-key-41).
115115

116-
## Key attributes
116+
## Key attributes
117117

118118
In addition to the key material, the following attributes may be specified. In a JSON Request, the attributes keyword and braces, '{' '}', are required even if there are no attributes specified.
119119

0 commit comments

Comments
 (0)