Authentication
Passwords are hashed with PHP's current password hashing implementation. Sessions use HttpOnly cookies and regenerate after successful login.
We only describe controls implemented in this build or operational requirements that must be configured before production.
Passwords are hashed with PHP's current password hashing implementation. Sessions use HttpOnly cookies and regenerate after successful login.
State-changing forms and API requests use CSRF tokens. Login, registration and password-reset flows include IP-based rate limiting.
Production must run over HTTPS. When HTTPS is active, the application sends an HSTS header and marks the session cookie Secure.
Project queries are scoped to the authenticated user. Administrative views require the admin role.
Database and transformation-service credentials are stored in server-side configuration and blocked from direct HTTP access.
Key authentication, privacy and administrative actions are recorded with timestamp, IP and user agent for security review.
TUNCBA cannot make an insecure deployment secure by policy text alone. cPanel permissions, database backups, TLS, mail security, server patching and production transformation infrastructure must also be maintained correctly.
Report a security issue