Passwords, API keys, tokens, and certificates are the keys to everything you have built. When they leak, attackers do not need to find a vulnerability; they simply log in. Many serious breaches start with a credential committed to a repository or an account that had far more access than it needed, so handling secrets and permissions well is one of the most valuable habits in DevSecOps.
You'll start with identity and access management, including the principle of least privilege. Then you'll learn secrets management, where tools like HashiCorp Vault store and hand out credentials safely, and secret scanning, which catches keys before they reach a public repository.
Once credentials and access are under control, you'll be ready for the final module, Monitoring, Incident Response & Compliance, where you learn how to detect problems, respond to them, and prove your controls are working.
An overview of IAM and the ideas behind it, including least privilege and zero trust, and how they decide who can reach your accounts and data.
How secrets management tools help teams securely store, manage, and control access to credentials, using Vault and AWS Secrets Manager as examples.
The basics of HashiCorp Vault and how to get started running it on your own machine.
Set up secret scanning with Gitleaks and pre-commit hooks as a last line of defence before credentials reach a public repository.