Skip to content

Modern Docker Management, Designed for Everyone

chore: Update security report guidelines

Kyle Mendell3c2420cca7a8
diff --git a/SECURITY.md b/SECURITY.md
index 4f0f641b4..494dc8570 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -11,6 +11,11 @@ Instead, please report security vulnerabilities directly to our security team vi
### What to Include in Your Report
+> [!IMPORTANT]
+> Reports must be written by a human, not generated by AI. This requirement may seem unusual, but it serves as a validation step to ensure submitted security issues are genuine and well-understood, rather than low-effort CVE farming.
+>
+> If a report appears to be AI-generated, it may be closed unless our team can independently understand and validate the issue.
+
To help us address vulnerabilities effectively, please provide:
- A clear description of the vulnerability and its potential impact
@@ -22,7 +27,7 @@ To help us address vulnerabilities effectively, please provide:
We will:
-- Acknowledge receipt of your report within 48 hours
+- Acknowledge receipt of your report as soon as possible
- Investigate and validate the vulnerability promptly
- Work to develop and release a fix as quickly as possible
- Keep you informed of our progress throughout the process