updated qhelps

Author: chanel-y

powershell/ql/src/queries/security/cwe-327/ApprovedCipherMode.qhelp

@@ -20,25 +20,6 @@
       preferred as it provides both confidentiality and integrity.
     </p>
   </recommendation>
-  <example>
-    <p>
-      The following example shows a weak cipher mode (ECB) being used for encryption:
-    </p>
-    <sample language="powershell">
-# BAD: Using ECB mode which reveals patterns in encrypted data
-$aes = [System.Security.Cryptography.Aes]::Create()
-$aes.Mode = [System.Security.Cryptography.CipherMode]::ECB
-    </sample>
-    <p>
-      The following example shows a recommended approach using CBC mode with a random IV:
-    </p>
-    <sample language="powershell">
-# GOOD: Using CBC mode with a random IV
-$aes = [System.Security.Cryptography.Aes]::Create()
-$aes.Mode = [System.Security.Cryptography.CipherMode]::CBC
-$aes.GenerateIV()
-    </sample>
-  </example>
   <references>
     <li>NIST, SP 800-38A: <a href="https://csrc.nist.gov/publications/detail/sp/800-38a/final">Recommendation for Block Cipher Modes of Operation</a>.</li>
     <li>OWASP: <a href="https://cheatsheetseries.owasp.org/cheatsheets/Cryptographic_Storage_Cheat_Sheet.html">Cryptographic Storage Cheat Sheet</a>.</li>

powershell/ql/src/queries/security/cwe-327/ObsoleteKDFAlgorithm.ql

@@ -18,7 +18,6 @@ import powershell
 import semmle.code.powershell.ApiGraphs
 import semmle.code.powershell.dataflow.DataFlow
 
-
 class CryptDeriveKeyCall extends DataFlow::CallNode {
     CryptDeriveKeyCall() {
         this = API::getTopLevelMember("system")

powershell/ql/src/queries/security/cwe-327/WeakHashes.qhelp

@@ -18,28 +18,7 @@
       like PBKDF2, bcrypt, or Argon2.
     </p>
   </recommendation>
-  <example>
-    <p>
-      The following example shows the use of weak hash algorithms:
-    </p>
-    <sample language="powershell">
-# BAD: Using MD5 which is cryptographically broken
-$md5 = [System.Security.Cryptography.MD5]::Create()
-$hash = $md5.ComputeHash($data)
-
-# BAD: Using SHA1 which has known collision vulnerabilities
-$sha1 = [System.Security.Cryptography.SHA1]::Create()
-$hash = $sha1.ComputeHash($data)
-    </sample>
-    <p>
-      The following example shows the recommended approach using SHA-256:
-    </p>
-    <sample language="powershell">
-# GOOD: Using SHA-256 which is a strong cryptographic hash
-$sha256 = [System.Security.Cryptography.SHA256]::Create()
-$hash = $sha256.ComputeHash($data)
-    </sample>
-  </example>
+ 
   <references>
     <li>NIST, SP 800-131A: <a href="https://csrc.nist.gov/publications/detail/sp/800-131a/rev-2/final">Transitioning the Use of Cryptographic Algorithms and Key Lengths</a>.</li>
     <li>OWASP: <a href="https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html">Password Storage Cheat Sheet</a>.</li>

powershell/ql/src/queries/security/cwe-327/WeakSymmetricAlgorithm.qhelp

@@ -21,31 +21,7 @@
       AES is the current standard for symmetric encryption and is considered secure when used correctly.
     </p>
   </recommendation>
-  <example>
-    <p>
-      The following examples show the use of weak symmetric algorithms:
-    </p>
-    <sample language="powershell">
-# BAD: Using DES which has a 56-bit key
-$des = [System.Security.Cryptography.DES]::Create()
-
-# BAD: Using Triple DES which is deprecated
-$tdes = [System.Security.Cryptography.TripleDES]::Create()
-
-# BAD: Using RC2 which has known weaknesses
-$rc2 = [System.Security.Cryptography.RC2]::Create()
-    </sample>
-    <p>
-      The following example shows the recommended approach using AES:
-    </p>
-    <sample language="powershell">
-# GOOD: Using AES which is the current standard
-$aes = [System.Security.Cryptography.Aes]::Create()
-$aes.KeySize = 256
-$aes.GenerateKey()
-$aes.GenerateIV()
-    </sample>
-  </example>
+  
   <references>
     <li>NIST, FIPS 197: <a href="https://csrc.nist.gov/publications/detail/fips/197/final">Advanced Encryption Standard (AES)</a>.</li>
     <li>NIST, SP 800-131A: <a href="https://csrc.nist.gov/publications/detail/sp/800-131a/rev-2/final">Transitioning the Use of Cryptographic Algorithms and Key Lengths</a>.</li>