Security
Security is the first requirement, not a feature. Here is how MCDock protects your code and your servers.
Two-factor sign-in and AD/LDAP
TOTP two-factor with recovery codes, required for admins or everyone. Active Directory sign-in.
Push protection
Pushes with private keys, cloud tokens or oversized files are refused with a clear message.
Signed commits
Branches can require signed commits; verified signatures are shown on every commit.
Tamper-evident audit log
Every entry is hash-chained and verifiable, exportable, and can be forwarded to your SIEM.
Encryption at rest
2FA seeds, webhook secrets and CI variables are encrypted and locked to the server. Backups can be encrypted too.
Least-privilege service
Runs as a virtual service account with no rights outside its own folders, which are locked down.
HTTPS by default
New servers answer on HTTPS with their own certificate, or the certificate from your company CA.
Signed releases
Every release is signed by the MCDock owner key and checked before it installs. The server checks it is genuine.
Lockout, allow-lists and safe webhooks
Brute-force lockout across addresses, an IP allow-list, and webhooks that cannot be aimed at the server itself.
What leaves your network
Only the licence check-in: installation ID, version, organisation, contact e-mail and counts (users, active users, repositories, size). Never code, user names, repository names or IP addresses of your users.
How mcdock.dev is protected
- HTTPS only with HSTS preload, strict Content-Security-Policy
- Passwords hashed with Argon2id and checked against known leaks
- Admin behind a hidden address, two-factor sign-in and re-confirmation for risky actions
- Licences signed by a dedicated, revocable key; the release key never touches the web server
- Every admin action in an audit log
Reporting a vulnerability
Please e-mail security@mcdock.dev with the details and steps to reproduce. Do not post vulnerabilities in the community. We answer within 3 working days and credit you if you wish.
Release signing
Every release is signed with the MCDock owner key. Servers install only signed packages and check at start that they run a genuine build. Check the SHA-256 on the download page before you install.