Autentikasi dan sesi for GitLab
high5 checks
Authentication is the highest-value target on any site: credential stuffing, session fixation and CSRF all aim at the same door.
What GitLab must have
- Login forms post over HTTPS with a CSRF token
- Rate limiting and lockout on failed attempts
- MFA available for privileged accounts
- Passwords screened against known breach corpora
- No account enumeration through error messages
How to fix it
- 1Add per-account and per-IP throttling
- 2Enforce MFA for admins and screen passwords with a k-anonymity API
GitLab context
Self-hosted DevOps platform with git, CI and registries.
Password-reset account takeover (CVE-2023-7028) hit many self-hosted instances — keep it patched and behind SSO.