Cheat sheet · Specialise
Cybersecurity cheat sheet (Defensive (SOC))
Opens with creditsFor students and early-career engineers heading for a SOC analyst role: foundations, a safe home lab, logs and telemetry, detection and triage, incident response, certifications and a first job. Every idea in a line or two, with the classic mistake beside it.
Chapters
8 chapters · 62 concepts
1Security foundationsThe ideas every security role shares: what security protects, how risk is judged, the networking and access basics, cryptography as concepts, and the law on testing.12 concepts
- 1CIA triadThe three properties security protects: confidentiality (only the right people can read it), integrity (nobody can change it unnoticed) and availability (it…
- 2Risk, threat and vulnerabilityA vulnerability is a weakness, a threat is someone or something that could exploit it, and risk combines how likely that is with how bad the outcome would be.
- 3CVSSAn open standard from FIRST that scores a vulnerability from 0 to 10 using factors such as how it is reached, the privileges needed and its impact.
- 4Defence in depthUsing several independent layers of control, such as MFA, patching, network rules, monitoring and backups, so one failure does not mean a breach.
- 5Least privilegeGiving each person, service and process only the access it needs to do its job, and only for as long as it needs it.
- 6Networking basics for securityIP addresses and subnets, TCP and UDP, ports, DNS, HTTP and HTTPS, and what firewalls and proxies do: the path every connection takes.
- 7TLSThe protocol that encrypts and authenticates connections such as HTTPS.
- 8Authentication and authorisationAuthentication proves who you are; authorisation decides what you are allowed to do once the system knows who you are.
- 9Multi-factor authenticationRequiring two or more kinds of proof to sign in: something you know, something you have or something you are.
- 10HashingA one-way function that turns data into a fixed-size fingerprint.
- 11Symmetric and asymmetric encryptionSymmetric encryption uses one shared key and is fast.
- 12Authorised testing and the lawIn most countries, accessing or testing a computer system without the owner's permission is a crime, whatever your intention.
12 in this chapterOpen this chapter2A safe home labThe setup for practising without hurting anyone: virtual machines, isolated networks, intentionally vulnerable apps, platform rules and notes.8 concepts
- 1Virtual machineA complete computer running as software inside your own, managed by a hypervisor such as VirtualBox, VMware Workstation or Hyper-V.
- 2SnapshotA saved state of a virtual machine that you can return to in seconds.
- 3Isolated lab networkA hypervisor network mode, such as host-only or internal, that lets lab machines talk to each other but not to your home network or the internet.
- 4Intentionally vulnerable appsApplications built with documented weaknesses so people can learn to find, fix and detect them legally, such as OWASP Juice Shop.
- 5Practice platform rulesEach platform's rules on what you may test (only the machines it gives you), what is banned (attacking the platform or other users) and what you may publish.
- 6Running targets in containersStarting practice apps and tools as containers, with ports published only on 127.0.0.1 so only your own machine can reach them.
- 7Lab notesOne page per exercise recording date, goal, steps, observations, meaning, and how the issue is prevented or detected, with captioned screenshots.
- 8Scripting for securitySmall scripts that read logs, filter and count events, or query a system, written in Python, Bash or PowerShell.
8 in this chapterOpen this chapter- Logs and telemetryWhere a defender's evidence comes from: Windows and Linux events, Sysmon, network and cloud telemetry, and how logs are collected and kept consistent.7 conceptsOpens with credits
- Detection, triage and threat intelligenceHow logs become alerts and alerts become decisions: SIEM, ATT&CK, Sigma, triage, tuning, threat intelligence and phishing analysis.9 conceptsOpens with credits
- Incident responseWhat a team does once an alert is a real incident: the lifecycle, playbooks, containment, evidence, communication and learning afterwards.8 conceptsOpens with credits
- CertificationsWhat certifications prove, the common entry-level ones, the options for each path and the traps. Exam versions change: always check the official page.7 conceptsOpens with credits
- PortfolioEvidence an employer can check: a few finished pieces for your path, write-ups you are allowed to publish, open source work and an honest profile.4 conceptsOpens with credits
- Your first security jobRealistic entry routes, what junior roles expect, how technical rounds work and the scams that target beginners.7 conceptsOpens with credits
- 9Glossary, A to ZEvery concept in the sheet and the smaller terms it uses, in one list.171 terms
About this sheet
Defend systems, test them, secure code.
Related on Sefism
Picked from the other libraries by shared topics.
Roadmaps
See allBest practices
See all- Secrets Management Best PracticesKeep API keys, passwords and tokens out of git, logs and browser bundles: secret managers, scanning, rotation, OIDC in CI and leak response.
- Authentication Best PracticesBuild sign-in that holds up: password rules from NIST, Argon2id hashing, login throttling, MFA and passkeys, secure sessions and safe account recovery.
- Secure Coding Best PracticesWrite code that resists attack: untrusted input, validation, parameterized queries, output encoding, safe parsing, uploads, SSRF and errors that fail closed.
Checklists
See all- Web Application Security ChecklistA practical web application security checklist built on the OWASP Top 10:2025 and ASVS 5.0, with a severity and a way to verify every check.
- API Security ChecklistCheck your REST or GraphQL API against the OWASP API Security Top 10: authentication, object authorization, rate limits, input validation, SSRF, CORS and logging.
- Linux Server Hardening ChecklistHarden an Ubuntu, Debian or RHEL server step by step: accounts and sudo, SSH, updates, firewall and open ports, permissions, logging and CIS benchmark scans.
Project structures
See all- Firebase (Cloud Functions and security rules) project structureFor students building an app on Firebase who need a real backend: Cloud Functions (2nd gen) in TypeScript, Firestore and Storage security rules with tests, and the Local Emulator Suite. The tree starts from
firebase initand grows into feature folders of callables, triggers and scheduled jobs, then adds CI deploys, environments, contract tests and runbooks. - AI agent with an MCP server project structureFor developers who want to give AI assistants safe access to their own data or API. A TypeScript MCP server built on the official SDK, organised by feature (tasks, projects) with each feature owning its tools, resources and prompts, served over stdio for local hosts and Streamable HTTP with OAuth for remote ones, plus a small agent and the evals that prove a model can use it.
- Terraform project structureAn infrastructure repository for a small app on AWS: reusable modules, one folder per environment with its own remote state, pinned providers, tests and security scans, with plan on every pull request and apply from CI. For students who have finished the Terraform tutorials and want to know how a real team lays out the files. The same layout works unchanged with OpenTofu.
Career questions
See all- How do I get into AI security as a student or junior engineer?Build a normal security or software foundation first, then learn how LLM apps fail using the OWASP Top 10 for LLM Applications and MITRE ATLAS, and prove it by building, testing and hardening a small LLM app of your own. Most people reach AI security through AppSec, security engineering or ML engineering, not straight from university.
- Where do I start if I want a career in cybersecurity or IT operations?Start with the foundations both fields share: networking, Linux, and how systems fail. Then choose an entry role such as SOC analyst, IT support or junior cloud operations, and prove it with hands-on labs and one documented project rather than a stack of certificates.
- Can I use AI coding tools at my internship, and what should I never paste into them?Usually yes, but only the tools your company has approved, on the code and data they allow, and in the way they allow. Ask in your first week. Never paste secrets, customer data or code you are not permitted to share, and review everything the tool writes as if your name is on it, because it is.
Work with me
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com