We actively support and provide security updates for the following versions of AI Sidekick for Splunk:

We take the security of AI Sidekick for Splunk seriously. If you discover a security vulnerability, please report it responsibly.

🚨 DO NOT create public GitHub issues for security vulnerabilities.

Instead, please report security issues privately to:

Email: security@deslicer.com

When reporting a security vulnerability, please include:

1. Description: A clear description of the vulnerability
2. Impact: Potential impact and attack scenarios
3. Reproduction: Step-by-step instructions to reproduce the issue
4. Environment:
   • Version of AI Sidekick for Splunk
   • Python version
   • Operating system
   • Deployment method (Docker, local, etc.)
5. Evidence: Screenshots, logs, or proof-of-concept code (if applicable)
6. Suggested Fix: If you have ideas for remediation

We are committed to responding to security reports promptly:

• Initial Response: Within 48 hours of receiving your report
• Status Update: Within 7 days with our assessment and planned actions
• Resolution: Security fixes will be prioritized and released as soon as possible

We follow responsible disclosure practices:

1. Investigation: We will investigate and validate the reported vulnerability
2. Fix Development: We will develop and test a fix
3. Coordinated Release: We will coordinate the release of the fix with you
4. Public Disclosure: After the fix is released, we may publicly acknowledge the vulnerability and your contribution (with your permission)

When using AI Sidekick for Splunk, please follow these security best practices:

• Never commit API keys to version control
• Use environment variables for sensitive configuration
• Rotate API keys regularly
• Use least-privilege access for service accounts

• Keep dependencies updated to patch known vulnerabilities
• Use HTTPS/TLS for all communications
• Implement proper authentication for production deployments
• Run with minimal privileges (avoid root/administrator accounts)
• Enable audit logging for security monitoring

• Restrict network access to necessary ports and services
• Use firewalls to limit exposure
• Implement rate limiting to prevent abuse
• Monitor for suspicious activity

• Encrypt sensitive data at rest and in transit
• Implement proper access controls for Splunk data
• Follow data retention policies
• Sanitize logs to prevent information disclosure

AI Sidekick for Splunk includes several built-in security features:

• Input validation for all user inputs
• Secure session management with Redis
• Rate limiting for API endpoints
• Audit logging for security events
• Configurable authentication methods
• TLS/SSL support for encrypted communications

Security updates will be:

• Released promptly for supported versions
• Documented in release notes with CVE numbers when applicable
• Announced through our security advisory channels
• Backward compatible when possible

We currently do not have a formal bug bounty program, but we greatly appreciate security researchers who help us improve the security of our project. We will:

• Acknowledge your contribution in our security advisories (with your permission)
• Provide recognition in our project documentation
• Consider your feedback for future security improvements

For security-related questions or concerns:

• Email: security@deslicer.com
• Response Time: Within 48 hours during business days
• Encryption: PGP key available upon request

We will not pursue legal action against security researchers who:

• Report vulnerabilities responsibly through proper channels
• Do not access or modify data beyond what is necessary to demonstrate the vulnerability
• Do not disrupt our services or harm our users
• Follow coordinated disclosure practices

Thank you for helping keep AI Sidekick for Splunk and our community safe!

This security policy is based on industry best practices and is regularly reviewed and updated.