We actively support the following versions with security updates:
| Version | Supported |
|---|---|
| 1.x.x | β Yes |
| < 1.0 | β No |
We take security vulnerabilities seriously. If you discover a security vulnerability in the Surrogate Model Platform, please help us protect our users by following responsible disclosure practices.
For security vulnerabilities, please DO NOT create a public GitHub issue.
Instead, please:
- Email directly: Send details to durai@infinidatum.net
- Subject line: "Security Vulnerability - Surrogate Model Platform"
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact assessment
- Any suggested fixes (if available)
- Acknowledgment: We'll acknowledge receipt within 24 hours
- Initial Assessment: We'll provide an initial assessment within 72 hours
- Updates: We'll keep you informed of our progress
- Resolution: We aim to resolve critical vulnerabilities within 7 days
- Disclosure: We'll coordinate public disclosure after the fix is available
This security policy applies to:
- β Core Platform: Backend API and ML algorithms
- β Authentication: JWT and user management systems
- β Database: Data access and storage security
- β API Endpoints: All REST API security
- β Docker Images: Container security
- β Dependencies: Third-party package vulnerabilities
The following are typically out of scope:
- β Social engineering attacks
- β Physical security issues
- β Denial of Service (DoS) attacks
- β Issues in third-party services (GitHub, Docker Hub, etc.)
- β Vulnerabilities requiring admin/root access
When deploying the Surrogate Model Platform:
-
Authentication:
- Use strong, unique passwords
- Enable two-factor authentication where available
- Regularly rotate API keys and secrets
-
Environment Security:
- Keep all dependencies updated
- Use secure communication (HTTPS/TLS)
- Implement proper firewall rules
- Use secure database configurations
-
Data Protection:
- Encrypt sensitive data at rest
- Use secure communication channels
- Implement proper backup strategies
- Follow data privacy regulations (GDPR, etc.)
-
Access Control:
- Follow principle of least privilege
- Regularly audit user permissions
- Use role-based access control (RBAC)
- Monitor access logs
When contributing to the project:
-
Code Security:
- Follow secure coding practices
- Validate all inputs
- Use parameterized queries
- Avoid hardcoded secrets
-
Dependencies:
- Keep dependencies updated
- Audit packages for vulnerabilities
- Use package lock files
- Avoid unnecessary dependencies
-
Testing:
- Include security test cases
- Test authentication and authorization
- Validate input sanitization
- Test error handling
- Authentication: Uses JWT tokens with configurable expiration
- Authorization: Role-based access control implemented
- Input Validation: API endpoints include input validation
- SQL Injection: Protected via SQLAlchemy ORM
- CORS: Configurable CORS settings
- Rate Limiting: Recommended for production deployments
- SSL/TLS: Always use HTTPS in production
- Database Security: Use encrypted connections and credentials
- Secret Management: Use proper secret management systems
- Monitoring: Implement security monitoring and alerting
- Updates: Keep all components updated regularly
For commercial deployments requiring enhanced security:
- Enterprise Support: Contact durai@infinidatum.net
- Security Audits: Available for commercial customers
- Custom Security Features: Can be developed under commercial agreements
- Compliance: Support for industry-specific compliance requirements
- All default passwords changed
- SSL/TLS certificates configured
- Database access properly secured
- API rate limiting configured
- Logging and monitoring enabled
- Backup and recovery procedures tested
- Security scanning completed
- Access controls validated
- Dependencies updated monthly
- Security patches applied promptly
- Access logs reviewed regularly
- User permissions audited quarterly
- Backup integrity verified
- Incident response plan updated
- Security training completed
We provide security updates through:
- GitHub Releases: Security patches in new versions
- Security Advisories: GitHub security advisories for critical issues
- Email Notifications: For commercial customers
- Documentation Updates: Security best practices updates
For security-related inquiries:
- Security Issues: durai@infinidatum.net
- General Security Questions: Create a GitHub Discussion
- Commercial Security: durai@infinidatum.net
We appreciate security researchers who help keep our platform secure. Contributors who report valid security vulnerabilities will be:
- Acknowledged in our security hall of fame (with permission)
- Credited in release notes for security fixes
- Considered for bug bounty rewards (commercial deployments)
- OWASP Top 10
- NIST Cybersecurity Framework
- FastAPI Security Documentation
- Docker Security Best Practices
Remember: Security is everyone's responsibility. When in doubt, please reach out to us.
Last updated: September 2024