| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
To report a security vulnerability, please email security@ideatech.example.com. We will respond within 48 hours.
- .env usage: Store secrets in
.envfiles, never in source code. - Client-side: Never expose server-side secrets to the client.
- Git: Ensure
.envis added to.gitignore.
- Use generic error messages for the user.
- Log detailed errors on the server only.
- Sanitize and validate all user inputs.
- Prevent SQL injection and XSS via parameterization and escaping.
- Use trusted ORMs (e.g., Prisma, Supabase).
- Enable Row-Level Security (RLS).
- Avoid raw queries where possible.
- Deploy on secure, managed platforms (Vercel, Netlify, AWS).
- Enable DDoS protection and firewalls.
- HTTPS: Enforce HTTPS for all communications.
- Use strict CSP (Content Security Policy).
- Implement HSTS and X-Content-Type-Options headers.
- Dependencies: Regularly run
npm audit. - Code Analysis: Use linters (ESLint) and static analysis tools.
- Testing: Perform regular security assessments.