You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+6-9Lines changed: 6 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,13 @@
1
1
## Correct Use of SEAL-Embedded
2
2
3
3
SEAL-Embedded supports encryption with either a secret key (symmetric) or a public key (asymmetric).
4
-
A secret key is stored in device flash RAM, and is vulnerable against attacker with physiscal access to the deivce.
5
-
Once a secret key is leaked, all previous data encrypted with the secret key or a public key generated by the secret key are at risk.
6
-
Deployments of SEAL-Embedded should avoid using symmetric encryption unless has been reviewed by security and cryptography experts.
4
+
When symmetric encryption is used, the secret key must be stored in device memory and is thus vulnerable to attackers with access to the device.
5
+
Once the secret key is leaked, all previous data encrypted with the secret key (or a public key associated with the secret key) is at risk.
6
+
Therefore, deployments of SEAL-Embedded should avoid using symmetric encryption, unless the deployment has been reviewed by security and cryptography experts.
7
7
8
8
## Correct Use of Microsoft SEAL
9
9
10
-
Homomorphic encryption schemes have various and often unexpected security models that may be surprising even to cryptography experts.
11
-
In particular, decryptions of Microsoft SEAL ciphertexts should be treated as private information only available to the secret key owner, as sharing decryptions of ciphertexts may in some cases lead to leaking the secret key.
12
-
If it is absolutely necessary to share information about the decryption of a ciphertext, for example when building a protocol of some kind, the number of bits shared should be kept to a minimum, and secret keys should be rotated regularly.
13
-
Commercial applications of Microsoft SEAL should be carefully reviewed by cryptography experts who are familiar with homomorphic encryption security models.
10
+
Please see the [SECURITY.md document for Microsoft SEAL](https://github.com/microsoft/SEAL/blob/main/SECURITY.md#correct-use-of-microsoft-seal).
14
11
15
12
## Security
16
13
@@ -24,7 +21,7 @@ If you believe you have found a security vulnerability in any Microsoft-owned re
24
21
25
22
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
26
23
27
-
If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
24
+
If you prefer to submit without logging in, send an email to [[email protected]](mailto:[email protected]). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
28
25
29
26
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
30
27
@@ -50,4 +47,4 @@ We prefer all communications to be in English.
50
47
51
48
Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
0 commit comments