Identity protection
Argon2id password hashing, server-backed sessions, session invalidation and blocked-account handling.
A private portal benefits from careful defaults and external security review. No web application can promise absolute security.
Argon2id password hashing, server-backed sessions, session invalidation and blocked-account handling.
CSRF tokens, same-origin checks, strict response headers and parameterized SQL queries.
Secure random invitation and license codes, keyed hashes and atomic one-time redemption.
A safe local build is not a security certification for the public internet.
Use a valid TLS certificate, protected secrets and HSTS. The development web server must stay bound to localhost.
Configure WAF rules, bot mitigation, DDoS protection, IP rate limiting and actionable alerts.
Perform penetration testing, dependency scanning, operating-system patching, backups and regular security reviews.
The bot must have Manage Roles and its highest role must be above the role it grants. OAuth should request only necessary scopes.