Path
DevSecOps
Keep secrets out of git, give every account only what it needs, harden SSH and containers, and prove that keys, certificates and downloads are what they claim to be.
By Deboistech 6 labs 1 h 27 minBeginner to intermediate
Showing 1 of 6 labs.
- Subscription Find and remove leaked secrets Track a leaked password through git history, move secrets out of code and scrub the history.
- Subscription Least privilege: permissions and sudo Close world-writable files, lock secrets, add a service account and one narrow sudo rule.
- Subscription Harden an SSH server config Edit a real sshd_config: no root, keys only, an allow list and fewer ways in.
- Subscription Run a small certificate authority Make a CA, sign a service certificate with it, verify the chain and audit expiry and names.
- Subscription Harden a Dockerfile Fix a risky Dockerfile: pin the base by digest, keep secrets out of layers, slim it, drop root.
- Subscription Verify checksums and signatures Catch a tampered download, check who signed the checksum list, and sign your own release.
