Big news: I just completed Foundations of Cybersecurity, a course by Google on Coursera. š
I'm a frontend developer (Next.js, React, TypeScript) and a BS Cyber Security student at Lahore Garrison University. I've written 100+ posts about building for the web. Now I want to understand how to protect what we build.
Here are the key terms I learned, explained the way a web developer would see them.
1. The CIA Triad
Not the agency. It stands for Confidentiality, Integrity, Availability.
-
Confidentiality: only the right people can see the data.
Web example: a user can't open another user's
/dashboardor read their orders by changing an ID in the URL. - Integrity: data isn't changed by anyone who shouldn't change it. Web example: a user can't edit the price in a request and buy a $500 item for $5. Always validate on the server.
- Availability: the system works when users need it. Web example: your site stays up during traffic spikes or an attack that tries to flood it.
Every security decision protects at least one of these three.
2. Threat, Risk, and Vulnerability
These three get mixed up all the time.
- Threat: something that could cause harm, like an attacker trying to steal logins.
- Vulnerability: a weakness that can be exploited, like a login form that doesn't limit failed attempts.
- Risk: the chance and impact of a threat exploiting a vulnerability.
Web example: an outdated npm package with a known flaw is a vulnerability. Someone scanning sites for that flaw is the threat. The risk is how likely they are to find you and how much damage it would do.
3. Phishing and Social Engineering
Social engineering tricks people instead of breaking code. Phishing is the most common form: a fake email or message that pushes you to click a link or enter your credentials.
Web example: a fake "GitHub security alert" email that sends you to a lookalike login page. One careless click can hand over access to your repos or deploy keys.
This was my biggest takeaway: most attacks don't break the code, they trick the person.
4. Malware and Ransomware
Malware is any malicious software. Ransomware is a type that locks your files and demands payment to unlock them.
Web example: a compromised dependency or a malicious browser extension on a developer's machine can lead to stolen source code or a locked project folder. Keep backups and review what you install.
5. The NIST Cybersecurity Framework
NIST CSF gives teams a repeatable way to manage risk, built around five functions:
- Identify: know your assets and risks (what data do you store?).
- Protect: put safeguards in place (HTTPS, MFA, access control).
- Detect: notice problems quickly (logs, alerts).
- Respond: act when something happens (an incident plan).
- Recover: get back to normal (backups, lessons learned).
Web example: "be secure" is vague. Using this list turns it into tasks you can actually do on a project.
6. SIEM (Security Information and Event Management)
A SIEM collects and analyzes log data from many sources to help analysts spot threats.
Web example: it can flag 5,000 failed login attempts on your app in one minute from the same IP, something nobody would catch by reading raw logs by hand.
What I'm Taking Back to My Code
- Validate and sanitize all input on the server, not just in the browser.
- Use authentication and authorization correctly: logging in is not the same as being allowed.
- Turn on MFA everywhere, especially GitHub and hosting accounts.
- Keep dependencies updated and think twice before adding new ones.
- Never trust a link in an email. Open the site directly instead.
Final Thoughts
Security isn't a separate job from development. It's part of building well. This course was my first step, and I plan to keep going and share what I learn along the way.
š You can find more of my writing at hamidrazadev.com.
What's one security habit every developer should have? Tell me in the comments. š
Top comments (0)