From 2fac1e2f0b011ac4f696ea3d5600f741ce0c0f27 Mon Sep 17 00:00:00 2001
From: Lawrence Lucas Large <162439255+LukeLarge@users.noreply.github.com>
Date: Tue, 9 Dec 2025 21:12:18 -0600
Subject: [PATCH 1/2] Create SECURITY.md

---
 SECURITY.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 SECURITY.md

diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000..034e848
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,21 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 5.1.x   | :white_check_mark: |
+| 5.0.x   | :x:                |
+| 4.0.x   | :white_check_mark: |
+| < 4.0   | :x:                |
+
+## Reporting a Vulnerability
+
+Use this section to tell people how to report a vulnerability.
+
+Tell them where to go, how often they can expect to get an update on a
+reported vulnerability, what to expect if the vulnerability is accepted or
+declined, etc.

From 41fe9e8b5408cdf59c7507c54bde5032a7ffdb1b Mon Sep 17 00:00:00 2001
From: Lawrence Lucas Large <162439255+LukeLarge@users.noreply.github.com>
Date: Tue, 9 Dec 2025 23:33:36 -0600
Subject: [PATCH 2/2] Update SECURITY.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 SECURITY.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/SECURITY.md b/SECURITY.md
index 034e848..92b9f10 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -14,8 +14,8 @@ currently being supported with security updates.
 
 ## Reporting a Vulnerability
 
-Use this section to tell people how to report a vulnerability.
+If you discover a security vulnerability in this project, please report it by emailing **security@example.com** or by submitting a report via our [GitHub Security Advisories](https://github.com/OWNER/REPO/security/advisories).
 
-Tell them where to go, how often they can expect to get an update on a
-reported vulnerability, what to expect if the vulnerability is accepted or
-declined, etc.
+We aim to respond to all vulnerability reports within **5 business days**. You will receive updates on the status of your report at least once per week until the issue is resolved or closed.
+
+After you submit a report, our security team will investigate the issue and contact you for any additional information if needed. If the vulnerability is accepted, we will work with you to coordinate a fix and public disclosure. If the vulnerability is declined, we will provide a clear explanation.