| Version | Supported |
|---|---|
| 1.0.x | ✅ Currently supported |
If you discover a security vulnerability within Prism, please follow these steps:
- Do NOT create a public GitHub issue for the vulnerability.
- Navigate to the Security Advisories page.
- Click "Report a vulnerability" to submit a private report.
- Provide detailed information about the vulnerability:
- Description of the issue
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Initial Response: Within 24-48 hours
- Assessment: Within 1 week
- Fix Deployment: As soon as possible based on severity
- Public Disclosure: After fix is deployed (typically within 30 days)
- Use strong, unique passwords
- Enable two-factor authentication where available
- Keep your Prism installation up to date
- Review access permissions regularly
- Report any suspicious activity immediately
Prism implements the following security measures:
- Password Hashing: bcrypt with salt rounds
- Authentication: JWT tokens with HTTP-only cookies
- Input Validation: Server-side validation on all endpoints
- SQL Injection Prevention: Parameterized queries via SQLite
- CORS: Configured to restrict origins
Thank you for helping keep Prism and its users safe! 🔒