| .. | ||
| img | ||
| asset_proxy.md | ||
| cicd_environment_variables.md | ||
| crime_vulnerability.md | ||
| information_exclusivity.md | ||
| password_length_limits.md | ||
| password_storage.md | ||
| project_import_decompressed_archive_size_limits.md | ||
| rack_attack.md | ||
| rate_limits.md | ||
| README.md | ||
| reset_root_password.md | ||
| ssh_keys_restrictions.md | ||
| two_factor_authentication.md | ||
| unlock_user.md | ||
| user_email_confirmation.md | ||
| user_file_uploads.md | ||
| webhooks.md | ||
| comments | type |
|---|---|
| false | index |
Security
- Password storage
- Password length limits
- Restrict SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- Reset your root password
- Unlock a locked user
- User File Uploads
- How we manage the CRIME vulnerability
- Enforce Two-factor authentication
- Send email confirmation on sign-up
- Security of running jobs
- Proxying images
- CI/CD environment variables
Securing your GitLab installation
Consider access control features like Sign up restrictions and Authentication options to harden your GitLab instance and minimize the risk of unwanted user account creation.