diff --git a/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/guidance.md b/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/guidance.md
new file mode 100644
index 00000000..7e0f18f7
--- /dev/null
+++ b/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/guidance.md
@@ -0,0 +1,5 @@
+# Guidance
+
+Provide a step-by-step walkthrough with a screenshot on how you exploited the vulnerability. This will speed triage time and result in faster rewards. Please include specific details on where you identified the incomplete cleanup of keying material, how you identified it, and what actions you were able to perform as a result.
+
+Attempt to escalate the vulnerability to perform additional actions. If this is possible, provide a full Proof of Concept (PoC).
diff --git a/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/recommendations.md b/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/recommendations.md
new file mode 100644
index 00000000..5b31d5bb
--- /dev/null
+++ b/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/recommendations.md
@@ -0,0 +1,7 @@
+# Recommendation(s)
+
+Implement strong cryptography and keep up to date algorithms, protocols, and keys in place. It is best practice for the application to retain sensitive cryptographic data within memory for longer than needed by the application.
+
+For more information, refer to the following resource:
+
+- <https://owasp.org/Top10/A02_2021-Cryptographic_Failures/>
diff --git a/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/template.md b/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/template.md
new file mode 100644
index 00000000..108e0d54
--- /dev/null
+++ b/submissions/description/cryptographic_weakness/incomplete_cleanup_of_keying_material/template.md
@@ -0,0 +1,22 @@
+# Incomplete Cleanup of Keying Material
+
+## Overview of the Vulnerability
+
+Cryptography is used to ensure secure storage and transmission of data. However, there are a number of best practices that must be followed to ensure the cryptography in use remains secure and does not result in the exposure of sensitive data. It was identified that the application's cleanup of keying material is incomplete and it retains sensitive cryptographic data in memory longer than is necessary. This can allow an attacker to break the confidentiality of requests sent to and from the endpoint.
+
+## Business Impact
+
+This vulnerability can lead to reputational damage of the company through the impact to customers’ trust, and the ability of an attacker to view data. The severity of the impact to the business is dependent on the sensitivity of the accessible data being transmitted by the application.
+
+## Steps to Reproduce
+
+1. Enable a HTTP interception proxy, such as Burp Suite or OWASP ZAP
+1. Setup {{software}} to intercept and log requests
+1. Use a browser to navigate to: {{URL}}
+1. {{action}} to view unencrypted requests
+
+## Proof of Concept (PoC)
+
+The following screenshot(s) demonstrate(s) this vulnerability:
+
+{{screenshot}}