We actively maintain and provide security updates for the following versions of Placemento:
| Version | Supported | Status |
|---|---|---|
| 1.0.x | ✅ | Current |
| 0.9.x | ✅ | Previous |
| < 0.9 | ❌ | Deprecated |
- JWT-based Authentication: Secure token-based user authentication
- Role-based Access Control: Different permission levels for admins and students
- Password Hashing: Bcrypt encryption for secure password storage
- Email OTP Verification: Two-factor authentication for account security
- Input Validation: Comprehensive validation for all user inputs
- SQL Injection Prevention: Mongoose ODM with parameterized queries
- XSS Protection: Sanitized user inputs and secure rendering
- Rate Limiting: API rate limiting to prevent abuse and DDoS attacks
- Data Encryption: Sensitive data encrypted at rest and in transit
- Secure Headers: HTTP security headers implementation
- CORS Policy: Controlled cross-origin resource sharing
- Session Management: Secure session handling and timeout policies
We take security vulnerabilities seriously. If you discover a security issue in Placemento, please follow these steps:
- Primary Contact: Create an issue on GitHub Issues
- For Sensitive Issues: Email directly to the development team
- Response Time: We aim to respond within 48 hours
When reporting a vulnerability, please provide:
- Detailed Description: Clear explanation of the vulnerability
- Steps to Reproduce: Step-by-step instructions to replicate the issue
- Impact Assessment: Potential impact and affected components
- Proof of Concept: Code or screenshots demonstrating the issue (if applicable)
- Suggested Fix: If you have ideas for fixing the vulnerability
- Acknowledgment: We'll acknowledge receipt of your report within 48 hours
- Investigation: Our team will investigate and validate the reported issue
- Assessment: We'll assess the severity and impact of the vulnerability
- Resolution: We'll work on a fix and provide an estimated timeline
- Disclosure: Once fixed, we'll coordinate disclosure and credit reporting parties
We appreciate security researchers who help us maintain a secure platform:
- Public Acknowledgment: Recognition in our security credits (if desired)
- Contribution Credit: Listed as a contributor for significant security improvements
- Open Source Spirit: All fixes will be shared with the community
- Environment Variables: Never commit sensitive data like API keys or passwords
- Dependency Updates: Regularly update dependencies to patch known vulnerabilities
- Code Review: All security-related changes must undergo thorough peer review
- Testing: Implement and maintain security tests for critical functionality
- Environment Separation: Use different configurations for development, staging, and production
- Access Control: Limit production access to authorized personnel only
- Monitoring: Implement logging and monitoring for security events
- Backup & Recovery: Regular backups with encrypted storage
- This is an educational project developed by MCA students
- Primarily designed for internal use within NIT Warangal
- Regular security audits are recommended for production deployments
- Enhanced encryption for sensitive student data
- Advanced audit logging and monitoring
- Integration with institutional authentication systems
- Comprehensive security testing framework
Security is a shared responsibility. Thank you for helping us keep Placemento secure! 🛡️