Learn the words developers use

The eight words the rest of the course assumes you already know. Start here even if you think you know them.

• Clients, servers and requestsWhy every website is two computers having a very fast conversation.4 min · 6 questions
• Frontend, backend, databaseThe three layers every web product has, and which one holds the things worth stealing.4 min · 6 questions
• APIs and endpointsThe doors in and out of your product, and why every one of them is a security decision.4 min · 6 questions
• Domains, DNS and where a site livesHow a name becomes a computer, and the two ways that goes wrong.4 min · 6 questions
• HTTPS, TLS and the padlockWhat the padlock promises, what it does not, and why expiry is an outage.4 min · 6 questions
• Hosting, and dev vs staging vs productionWhere code runs, and why the copy nobody guards is the one that gets breached.4 min · 6 questions
• What the browser is actually runningHTML, CSS, JavaScript, and the reason a secret in the frontend is already public.4 min · 6 questions
• Putting it togetherOne request, end to end, through every piece you just learned.5 min · 5 questions

Repos, branches, pull requests, builds, pipelines. The vocabulary of every engineering conversation you will ever sit in.

• Repositories, commits and gitWhat a repo is, and why deleting a secret from a file does not delete it.4 min · 6 questions
• Branches, pull requests and reviewHow teams change code without breaking the live product, and where a security gate belongs.4 min · 6 questions
• Dependencies, packages and the supply chainWhy most of the code in your product was written by strangers.5 min · 7 questions
• Builds, bundles and artifactsWhat happens between "the code is written" and "the code is running".4 min · 6 questions
• CI/CD, explained properlyThe two most-used initials in software, and what actually happens when they run.5 min · 7 questions
• GitHub, GitLab, Bitbucket, Azure DevOpsThe four places code lives, and why CheckVibe connects to all of them twice.4 min · 6 questions
• Secrets, env vars and where they belongThe difference between a value and a secret, and the four places secrets go wrong.5 min · 6 questions
• How a fix actually reaches productionWhy a scanner that only reports is half a product, and what a deterministic fix means.4 min · 6 questions

Docker, images, layers, registries, Kubernetes and cloud accounts. The words you nodded along to on the last call.

• What a container actually isThe answer to "it works on my machine", and why it is not a virtual machine.5 min · 6 questions
• Images, layers and tagsThe difference between an image and a container, and why "latest" is not a version.5 min · 7 questions
• Docker, and what a Dockerfile saysThe tool everyone means when they say container, and the four lines that matter.4 min · 6 questions
• Registries: where images liveThe warehouse for images, and why it is a genuinely dangerous place to be careless.4 min · 6 questions
• Kubernetes and orchestrationWhat runs the containers, in enough detail to hold a conversation and no more.4 min · 6 questions
• What "the cloud" actually meansSomeone else's computers, rented by the second, and the three shapes it comes in.4 min · 6 questions
• How cloud accounts actually go wrongPermissions, public storage and the keys that never expire.5 min · 6 questions
• What container scanning actually findsHow CheckVibe reads an image without running it, and what comes back.4 min · 6 questions

Vulnerabilities, attackers, the OWASP Top 10, severity, and what the scanner initials mean. No prior knowledge assumed.

• Vulnerability, threat, riskThree words used interchangeably by everyone, that mean three different things.5 min · 6 questions
• Who actually attacks a small companyIt is not a hacker in a hood. It is a script that does not know your name.4 min · 6 questions
• The OWASP Top 10The industry's shared list of what actually goes wrong, and what each item means in plain words.6 min · 7 questions
• Injection: SQL, XSS and the one idea behind bothWhat happens when a computer cannot tell data from instructions.5 min · 6 questions
• Authentication vs authorizationWho you are, versus what you may do. Two words, and most breaches live in the second one.5 min · 7 questions
• Severity, confidence and false positivesWhy a tool that reports everything is worse than one that reports carefully.5 min · 6 questions
• SAST, DAST, SCA and the restFive sets of initials that describe five genuinely different things.5 min · 7 questions
• What a breach actually looks likeThe timeline, the cost, and why detection time is the number that matters.5 min · 6 questions

What we actually built, what each part is for, what it costs, and how to say it out loud.

• What CheckVibe is, in one sentenceThe positioning, the honest boundaries, and the sentence to lead with.4 min · 6 questions
• The four assets in the railDomains, Repositories, Containers, Clouds. What each holds and which plan opens it.5 min · 7 questions
• The Feed: one queue for everythingWhy findings from four asset types land in a single list, and what a team does with them.4 min · 6 questions
• What the scanners actually checkA tour of the real list, grouped by the chain from unit one.6 min · 7 questions
• AutoFix and pull request reviewsThe two places we stop reporting and start doing.4 min · 6 questions
• The Runtime suiteFive features that watch the running app instead of scanning it. All team tier.5 min · 7 questions
• Monitoring, threats, uptime and the other scansWhat keeps running after the first scan, and the pillars that are not security.4 min · 6 questions
• The plans, and what each one actually buysFree, Starter, Pro, Max, Team Basic, Team Advanced. Numbers you should know cold.6 min · 8 questions