-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Matthew Cummins <79932599+Matt-Cummins@users.noreply.github.com>
- Loading branch information
1 parent
bef2535
commit 963071b
Showing
1 changed file
with
47 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
The following versions of Your_AI_Overlord are actively supported and receive security updates: | ||
|
||
1.x | ||
|
||
:white_check_mark: | ||
|
||
< 1.0 | ||
|
||
:x: | ||
|
||
Reporting a Vulnerability | ||
|
||
If you discover a security vulnerability, please report it by emailing xbard@protonmail.com. Please provide detailed information about the issue, including steps to reproduce the vulnerability. | ||
|
||
We take all security vulnerabilities seriously and will respond as quickly as possible to determine the impact and appropriate course of action. | ||
|
||
Security Best Practices | ||
|
||
Environment Variables: Ensure all sensitive data, such as API keys and MongoDB URIs, are stored in environment variables and not committed to the codebase. | ||
|
||
Access Control: Limit access to configuration files and sensitive information. Only authorized personnel should have the necessary permissions. | ||
|
||
Dependency Management: Keep all dependencies up to date, especially those related to security, to minimize vulnerabilities. | ||
|
||
Rate Limiting: The bot uses rate limiting (ratelimit) to prevent abuse of Twitch services and protect against spam attacks. | ||
|
||
Incident Response | ||
|
||
In the event of a security incident, our response will include the following steps: | ||
|
||
Identification: Confirm the existence of the issue. | ||
|
||
Containment: Prevent further exploitation of the vulnerability. | ||
|
||
Eradication: Fix the root cause of the vulnerability. | ||
|
||
Recovery: Restore normal operations. | ||
|
||
Follow-up: Analyze the incident and improve security measures to prevent future vulnerabilities. | ||
|
||
Contact | ||
|
||
For questions regarding security practices or incident response, please contact xbard@protonmail.com |