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
@@ -81,11 +107,20 @@ Best practices for secure algorithms
81
107
82
108
### Description
83
109
84
-
Hash - Sometimes implemented alongside encryption but has a different purpose
110
+
Hash - Sometimes implemented alongside encryption but has a different purpose;
111
+
Cryptography used for confidentiality; keeping information secret except for intended receipient/audience. Hashes are used to ensure the
112
+
integrity of the data, meaning ensuring from it's creation/generation to it's final state, it remains unmodified and untampered with.
113
+
Hashes also used as a substitute for storing data in it's original form. A one way function that - compare starting hash from known good data, to end hash which will indicate changes. Hashing passwords is a common application. Comparing hashes to determine if correct password entered.
-Sources for publishing notices when algorithms become cracked/obsolete and new
106
141
142
+
Cryptographic Failures are the number two most common issue on the OWASP Top 10
143
+
A02:2021 – Cryptographic Failures
144
+
145
+
Related weaknesses include
146
+
Notable Common Weakness Enumerations (CWEs) include CWE-327: Broken or Risky Crypto Algorithm, and CWE-331 Insufficient Entropy.
147
+
148
+
All amount to data being inadvertently being sent in cleartext, sensitive data, the use of old, weak or custom cryptographic algorithms or protocols that are ineffective against attacker efforts to uncover keys, . Best practics is to never build your own crypto mechanisms. Use proven and secure:
149
+
Secure Hashes: SHA-1 has been deprecated as of 2011 with a transition plan released in 2022. Recommenation to move towards orther families SHA256
150
+
Secure Encryption Algorithms; AES is the current standard; secure modes must be emplemented
0 commit comments