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
{{ message }}
Repository navigation
Commit 9bafbaf
Browse filesBrowse the repository at this point in the historyBrowse files
<!DOCTYPEqhelp PUBLIC "-//Semmle//qhelp//EN" "qhelp.dtd">
2
+
<qhelp>
3
+
<overview>
4
+
<p>
5
+
Modern encryption relies on it being computationally infeasible to break the cipher and
6
+
decode a message without the key. As computational power increases, the ability to break
7
+
ciphers grows and keys need to become larger.
8
+
</p>
9
+
<p>
10
+
RSA keys smaller than 2048 bits are considered weak and can potentially be broken using
11
+
modern hardware. Using such keys compromises the confidentiality and integrity of
12
+
encrypted data.
13
+
</p>
14
+
</overview>
15
+
16
+
<recommendation>
17
+
<p>
18
+
Use an RSA key size of at least 2048 bits. For long-term security, consider using
19
+
4096-bit keys.
20
+
</p>
21
+
<p>
22
+
When calling <code>[System.Security.Cryptography.RSA]::Create()</code> or creating an
23
+
<code>RSACryptoServiceProvider</code>, always specify a key size of 2048 or greater.
24
+
</p>
25
+
</recommendation>
26
+
27
+
<references>
28
+
<li>NIST, SP 800-131A: <ahref="https://csrc.nist.gov/publications/detail/sp/800-131a/rev-2/final">Transitioning the Use of Cryptographic Algorithms and Key Lengths</a>.</li>
0 commit comments