Security+ SY0-701 Dashboard
Simulations and lab companions for the C628 CompTIA Security+ Exam Prep course — organised by the five exam domains.
Exam Domains
Objective → Lab Map
Select any lab to open its Lab Companion (steps, commands and verification).
🧪 Lab Companion
Step-by-step companion for each of the 52 C628 hands-on labs.
🗂 Control Classifier
Sort security controls by category and type (SY0-701 1.1).
What is it?
Every security control has a category — who/what implements it (Technical, Managerial, Operational, Physical) — and a type — what it does to a threat (Preventive, Deterrent, Detective, Corrective, Compensating, Directive). Exam questions often hinge on telling these apart.
Exercise: classify 12 controls
Choose a category and a type for each control, then check. Where two answers are defensible, both are accepted.
| Control | Category | Type | Result |
|---|
⚠️ Common Mix-ups
- Signs and lighting deter; locks and mantraps prevent
- CCTV records (detective) but also deters
- Policies are managerial & directive — they tell people what to do
- A compensating control substitutes when the primary control is not feasible
🛡 Defence in Depth
- Layer controls of different types around each asset
- Pair every preventive control with a detective one
- Document compensating controls with an exception and review date
- Map controls to a framework (e.g. NIST CSF, ISO 27001)
🧭 Zero Trust & Deception
Policy decisions, AAA and deception technology (SY0-701 1.2).
What is it?
Zero Trust means "never trust, always verify": every request is evaluated on identity, device and context. In the control plane, the Policy Engine decides and the Policy Administrator issues the instruction; together they form the Policy Decision Point (PDP). In the data plane, the Policy Enforcement Point (PEP) allows or blocks the session. Deception technology (honeypots, honeyfiles, honeytokens) plants decoys that no legitimate user should touch — any access is a high-fidelity alert.
Exercise: Zero Trust access decision
Exercise: honeytoken tripwire
You are an intruder on a fictional file share. Browse the items — the SOC console on the right shows what the defenders see.
⚠️ Warning Signs
- Implicit trust because a request comes from "inside" the network
- Long-lived sessions never re-evaluated
- Any touch of a honeyfile, honeytoken or honeypot
- Impossible travel between two logins
🛡 Defences
- Adaptive identity: combine identity, device and context signals
- Least privilege and micro-segmented access
- Seed decoy credentials and files; alert on any use
- Log every decision for accounting (the third A in AAA)
🔐 Crypto Workbench
Real hashing and encryption in your browser via the Web Crypto API (SY0-701 1.4).
What is it?
Hashing gives a fixed-length fingerprint for integrity; salting makes identical passwords hash differently; symmetric encryption (AES) uses one shared key; asymmetric cryptography (RSA/ECC) uses a key pair for key exchange and digital signatures; PKI binds public keys to identities with certificates signed by a chain of trust. Everything below runs locally — nothing leaves your browser.
1. Hashing & the avalanche effect
Hash of your input:
Hash after changing just the last character ():
2. Salting password hashes
Two fictional users chose the same password. Compare stored hashes with and without a per-user random salt.
| User | Salt | Unsalted SHA-256 | Salted SHA-256(salt + password) |
|---|
Unsalted hashes match, so one rainbow-table lookup cracks both. Production systems also add key stretching (PBKDF2, bcrypt, scrypt, Argon2) to slow guessing.
3. AES-256-GCM encrypt / decrypt
Key derived from a passphrase with PBKDF2-SHA-256 (100,000 iterations, random salt). GCM is authenticated encryption — any tampering or wrong key is detected.
(not encrypted yet)
4. Toy RSA digital signature
Tiny textbook key (p=61, q=53, n=3233, e=17, d=2753) so you can follow the maths. Real keys are 2048+ bits with padding such as RSA-PSS.
Sign the message, then edit it and verify again.
5. Certificate chain validator
You are the browser. Inspect the chain presented by each fictional site and choose a verdict.
⚠️ Warning Signs
- MD5/SHA-1 for integrity or signatures
- Unsalted or fast password hashes
- Hard-coded keys, re-used IVs/nonces
- Certificate warnings users are trained to click through
🛡 Defences
- SHA-256+ for hashing; Argon2/bcrypt for passwords
- AES-GCM or ChaCha20-Poly1305 for data
- Protect private keys in an HSM/TPM; rotate and revoke
- Check expiry, revocation (CRL/OCSP) and name on every certificate
🎭 Threat Actor Profiler
Match scenarios to actor type and motivation (SY0-701 2.1).
What is it?
SY0-701 names six threat actors — nation-state, unskilled attacker, hacktivist, insider threat, organized crime, shadow IT — that differ in being internal or external, in resources/funding and in sophistication. Their motivations include data exfiltration, espionage, service disruption, blackmail, financial gain, philosophical/political beliefs, ethical, revenge, disruption/chaos and war. MITRE ATT&CK catalogues the tactics and techniques they use.
Exercise: profile the attacker
⚠️ Indicators
- Long dwell time and custom tooling suggest a well-funded actor
- Public claims of responsibility suggest hacktivism
- Ransom notes and leak sites point to organized crime
- Valid credentials used out of pattern may be an insider
🛡 Defences
- Threat-informed defence: map detections to ATT&CK techniques
- Prompt de-provisioning and user behaviour analytics for insiders
- Approved-software catalogue to reduce shadow IT
- Threat-intelligence feeds tailored to your sector
📧 Phishing Simulator
Identify suspicious emails — all examples are fictional.
What is Phishing?
Phishing is a social-engineering attack where attackers impersonate trusted senders to trick victims into revealing credentials, clicking malicious links, or downloading harmful attachments.
Simulation: Is this email Safe or Phishing?
🔎 Annotated Walkthrough: Spot the Red Flags
Step through a fictional phishing email one clue at a time.
🔗 Suspicious URL Inspector
Paste any URL (real or made-up). The inspector explains what to check — it does not visit the URL.
⚠️ Warning Signs
- Generic greetings like "Dear Customer"
- Urgent, fear-based language
- Mismatched sender domain
- Suspicious links or attachments
- Requests for passwords or money
🛡 Prevention Tips
- Hover over links before clicking
- Verify sender via another channel
- Enable multi-factor authentication
- Report suspicious emails
- Use spam filters and email security tools
🎓 Quick Quiz
Which is the strongest sign of a phishing email?
💻 XSS Simulator
See how unescaped input can be dangerous — safely.
What is Cross-Site Scripting?
XSS occurs when an application renders user input as HTML/JavaScript without proper escaping, allowing attackers to inject content that could steal sessions or deface pages.
Try It (Conceptual Demo)
Type any text. We'll show how it would render in an unsafe vs safe app.
❌ Unsafe Rendering (illustration)
In a vulnerable app, this raw HTML would execute. We only display the source for safety.
✅ Safe Escaped Output
Here the input is safely escaped and rendered as plain text.
⚠️ Warning Signs
- Pop-ups from untrusted sites
- Unexpected redirects
- Strange characters in URLs
🛡 Prevention Tips
- Always escape/encode output
- Use Content Security Policy (CSP)
- Sanitize user-supplied HTML
- Use frameworks that auto-escape
🎓 Quick Quiz
The best way to prevent XSS is to:
🔒 SQL Injection Simulator
Mock login form using fake in-memory data only.
What is SQL Injection?
SQL injection happens when user input is concatenated into a SQL query, letting attackers alter the query's logic. This demo uses mock data — no real database is queried.
Mock Login (Vulnerable Mode)
Hint: Try username admin with password ' OR '1'='1
SELECT * FROM users WHERE username='' AND password=''
⚠️ Warning Signs
- Login bypass possible with quotes
- Database errors in responses
- Unfiltered input fields
🛡 Prevention Tips
- Use parameterized queries / prepared statements
- Validate and sanitize input
- Apply least-privilege DB accounts
- Use ORMs that escape inputs
🎓 Quick Quiz
The best protection against SQL injection is:
🔑 Password Strength Lab
Estimate strength using simple entropy heuristics.
Test Your Password
⚠️ Weak Examples
- 123456
- password
- qwerty
- your name + birthday
🛡 Strong Password Tips
- 16+ characters with mixed types
- Use a passphrase of unrelated words
- Use a password manager
- Enable MFA whenever possible
🎓 Quick Quiz
Which is the strongest password?
🦠 Malware Visual Demo
Pure animation — no real malware involved.
What is Malware?
Malware is any malicious software designed to harm, exploit, or otherwise compromise a system. Common types include trojans, spyware, adware, and worms.
⚠️ Symptoms
- Slow performance
- Pop-ups and unknown apps
- Disabled antivirus
- Unusual network activity
🛡 Prevention
- Install reputable antivirus
- Keep software updated
- Avoid pirated software
- Don't click unknown links/files
🎓 Quick Quiz
Which is NOT a sign of malware infection?
🦠 Virus Spread Visualizer
Visual animation showing conceptual virus propagation.
What is a Computer Virus?
A virus is a type of malware that attaches itself to clean files and spreads through systems, often when users execute infected files.
⚠️ Spreads Via
- Infected USB drives
- Email attachments
- Downloaded files
- Network shares
🛡 Prevention
- Scan removable drives
- Don't open suspicious attachments
- Patch operating systems
- Use endpoint protection
🚫 Ransomware Demo
A fake locked-screen demo — completely safe.
What is Ransomware?
Ransomware encrypts files and demands payment to restore access. Attackers often exploit phishing or unpatched systems for entry.
⚠️ Warning Signs
- Files renamed with strange extensions
- Ransom note .txt files
- Sudden inability to open files
🛡 Recovery & Prevention
- Maintain offline backups
- Test restores regularly
- Patch and segment networks
- Don't pay — there's no guarantee
🎓 Quick Quiz
Best defense against ransomware:
⚠️ Weak Passwords
See how common weak passwords compare.
Top Weak Passwords vs Strong Alternatives
| Weak | Crack time (approx) | Stronger Alternative |
|---|---|---|
| 123456 | Instant | tea-MOON-river-91! |
| password | Instant | quartz-Otter-Beam-7Q |
| qwerty | Instant | silly-cactus-jumps-Hi9 |
| letmein | Instant | orchid-piano-Storm-44 |
| iloveyou | ~ seconds | willow-Mango-Robot-2x |
⚠️ Why Weak Passwords Fail
- Short and predictable
- Found in leaked password lists
- Easy to brute-force
- Reused across sites
🛡 Prevention
- Use unique passwords per site
- Generate via a password manager
- Enable MFA
- Check breaches periodically
💬 Data Leakage
Sensitive data exposed by accident or attack.
What is Data Leakage?
Data leakage is the unauthorized transmission of data from inside an organization to an external destination. It can be accidental (misconfigured cloud storage) or malicious (insider exfiltration).
Leakage Risk Estimator
Toggle practices and see your leak risk score.
⚠️ Common Causes
- Misconfigured S3 buckets
- Unencrypted laptops
- Phishing-stolen credentials
- Insider threats
🛡 Prevention
- Classify and encrypt sensitive data
- Audit access regularly
- Use DLP tools
- Train staff on handling data
🧱 Firewall Rule Builder
Ordered ACLs, first-match logic, implicit deny and segmentation (SY0-701 3.2).
What is it?
A firewall evaluates its access-control list top-down and applies the first rule that matches. If nothing matches, the implicit deny drops the packet. Segmentation places systems in zones (DMZ, internal, management) so that a compromise in one zone cannot reach everything else. A WAF adds Layer-7 inspection of HTTP content.
Segmentation zones (fictional network)
Security goals: the public may reach the web server on HTTPS only; only the web server and the jump host may reach the database (MySQL 3306); only the jump host may use SSH (22) anywhere internal; users may browse the Internet on HTTPS; DNS (UDP 53) to the internal resolver 10.0.20.53 is allowed from all internal zones; everything else is denied.
Exercise: fix the rule set
The starter rules contain mistakes. Edit, reorder, add or remove rules until every test packet gets the result the security goals require. Use any, an IP address or a CIDR such as 10.0.30.0/24.
| # | Action | Proto | Source | Destination | Port | Order |
|---|---|---|---|---|---|---|
| ∞ | DENY | any | any | any | any | implicit deny |
| Test packet | Proto/Port | Goal | Matched rule | Result |
|---|
Layer 7: WAF check
A network firewall sees ports and addresses; a WAF inspects the request itself. Pick a fictional request to see which signature-style rule (in the spirit of the OWASP Core Rule Set) would match.
⚠️ Warning Signs
- A broad ALLOW above a specific DENY (shadowed rule)
- "any any" rules left from troubleshooting
- Flat networks where users can reach databases
- Management ports exposed to the Internet
🛡 Defences
- Specific rules first, broad rules last, default deny
- Segment by trust level; use a jump host for admin
- Review rules regularly; remove unused ones
- Put a WAF in front of public web applications
🔍 Data Classification & DLP
Find sensitive data, classify it, then mask or tokenise it (SY0-701 3.3).
What is it?
Data classification labels information by sensitivity (e.g. Public, Internal, Confidential, Restricted). Data Loss Prevention (DLP) inspects data in use, in motion and at rest for patterns such as national ID numbers or payment cards, then warns, blocks or encrypts. Masking hides part of a value; tokenisation replaces it with a random token whose real value lives only in a secure vault.
Exercise: scan a document
All samples are fictional. Card numbers are well-known test numbers; NRIC values are textbook examples.
⚠️ Warning Signs
- ID or card numbers in email, chat or tickets
- Bulk exports sent to personal addresses
- Pattern matches with no validation (false positives)
- Unlabelled documents with sensitive content
🛡 Defences
- Classify at creation; label and handle by policy
- Validate matches (checksums, Luhn) to cut noise
- Tokenise card data to shrink PCI DSS scope
- Minimise collection — PDPA requires a purpose for NRIC collection
💾 Resilience Planner
RAID, backups, RPO/RTO and the 3-2-1 rule (SY0-701 3.4).
What is it?
RAID spreads data across disks for performance and/or fault tolerance — but RAID is not a backup. Backups protect against deletion, corruption and ransomware. The Recovery Point Objective (RPO) is how much data you can afford to lose; the Recovery Time Objective (RTO) is how long you can afford to be down.
Exercise: RAID calculator
Click disks to fail or replace them and watch the array status.
Exercise: backup plan checker
Exercise: which backup sets do I need?
⚠️ Warning Signs
- Treating RAID or replication as a backup
- Backups never restored in a test
- All copies reachable with the same admin credentials
- Backup interval longer than the RPO
🛡 Defences
- 3-2-1 (or 3-2-1-1-0) backup rule
- Immutable / offline copies against ransomware
- RAID 6 or 10 for large disks with long rebuilds
- Document and rehearse the recovery runbook
📊 CVSS v3.1 Calculator
Score and prioritise vulnerabilities (SY0-701 4.3).
What is it?
The Common Vulnerability Scoring System rates a vulnerability's severity from 0.0 to 10.0. The base score combines exploitability (attack vector, complexity, privileges, user interaction) with impact on confidentiality, integrity and availability, adjusted for scope. This calculator implements the official v3.1 base-score formula.
Exercise: build a vector
Vulnerability management: prioritise the backlog
Severity alone is not priority. Exposure and known exploitation (e.g. a listing in CISA KEV) raise urgency.
| Finding (fictional) | CVSS | Internet-facing | Known exploited | Priority | Remediation SLA |
|---|
⚠️ Warning Signs
- Patching by CVSS alone, ignoring exposure
- Scanner results never re-tested after fixes
- Out-of-date container base images
- No asset inventory to know what is affected
🛡 Defences
- Scan → prioritise → remediate → validate → report
- Define SLAs per severity and track exceptions
- Use compensating controls when a patch is unavailable
- Scan images and dependencies in the CI pipeline
📜 Log Investigator
Filter fictional logs, answer questions and build a timeline (SY0-701 4.4, 4.9).
What is it?
Investigations start with log data: authentication logs, web server logs, firewall and endpoint logs, aggregated in a SIEM. Analysts filter, correlate by IP, user and time, and reconstruct a timeline of what happened. All entries below are fictional, using documentation-only IP ranges.
Exercise: investigate
Questions
Incident timeline
- Answer questions to build the timeline.
⚠️ Warning Signs
- Many failures followed by a success from one IP
- New accounts or sudo use outside change windows
- SQL keywords or quotes in URL parameters
- Logs with gaps or that were cleared
🛡 Defences
- Centralise logs (SIEM) with synchronised time (NTP)
- Alert on brute-force thresholds; auto-ban (Fail2ban)
- Protect log integrity — ship off-host, restrict access
- Correlate auth, web and endpoint events by time
📱 MFA & TOTP
Generate real RFC 6238 time-based one-time passwords (SY0-701 4.6).
What is it?
Multifactor authentication combines different factor types: something you know, have, are, or somewhere you are. A TOTP authenticator app shares a secret with the server; both compute HMAC-SHA1(secret, floor(time / 30)), truncate it to 6 digits, and compare. No network connection is needed — just synchronised clocks.
Exercise: authenticator app
Provisioning URI (normally shown as a QR code):
Exercise: factor classifier
Assign each authenticator to its factor type.
Is it really MFA?
⚠️ Warning Signs
- Repeated push prompts the user did not start (MFA fatigue)
- SMS codes on numbers vulnerable to SIM swap
- "MFA" made of two things you know
- Shared or standing privileged accounts
🛡 Defences
- Phishing-resistant MFA (FIDO2 / passkeys) for admins
- Number matching for push approvals
- Least privilege with PAM and just-in-time sudo
- Protect TOTP seeds like passwords
🚨 Incident Response
IR lifecycle and order of volatility (SY0-701 4.8).
What is it?
The SY0-701 incident response process runs Preparation → Detection → Analysis → Containment → Eradication → Recovery → Lessons learned. During forensic acquisition, collect the most volatile evidence first (it disappears on power-off), hash every image, and keep a chain of custody.
Exercise: order the IR phases
Drag items, or use the arrow buttons (keyboard friendly).
Exercise: order of volatility (most → least volatile)
⚠️ Common Mistakes
- Pulling the power before capturing memory
- Wiping and rebuilding before scoping the incident
- Working on original evidence instead of a verified copy
- Skipping the lessons-learned review
🛡 Good Practice
- Maintain an IR plan, playbooks and contact lists
- Hash images (e.g. SHA-256) before and after copying
- Record who handled evidence, when and why
- Use legal hold when litigation is possible
⚖️ Risk Calculator & Register
Quantitative and qualitative risk analysis (SY0-701 5.2).
What is it?
Quantitative analysis puts a money value on risk: Single Loss Expectancy SLE = Asset Value × Exposure Factor and Annualised Loss Expectancy ALE = SLE × ARO (annualised rate of occurrence). Qualitative analysis rates likelihood and impact (here 1–5) on a heat map. Each risk is then accepted, avoided, transferred or mitigated and recorded in a risk register with an owner.
Exercise: SLE / ALE and control cost-benefit
Exercise: risk register & 5×5 heat map
| Risk (fictional) | Likelihood | Impact | Score | Treatment |
|---|
Rows: likelihood (5 = almost certain, top). Columns: impact (5 = severe, right). Risk appetite: scores ≥ 15 must not be accepted.
⚠️ Warning Signs
- Risks with no owner or review date
- High risks "accepted" without sign-off
- Control that costs more than the loss it prevents
- Register that never changes
🛡 Good Practice
- Define risk appetite and tolerance up front
- Track inherent vs residual risk
- Use KRIs to monitor changing risk
- Review the register on a fixed schedule
📡 Recon Visualiser
Passive vs active reconnaissance and reading scan results (SY0-701 5.5).
What is it?
Penetration tests begin with reconnaissance within an agreed scope and rules of engagement. Passive recon (OSINT) gathers public information without touching the target; active recon interacts with it — for example, port scanning. Everything here is static, fictional data: nothing is sent anywhere.
How port-scan types differ
Exercise: review scan results for a fictional host
Target: files.acme-lab.test (192.0.2.50) — in scope per the signed rules of engagement. Select a row for analysis.
| Port | State | Service | Version (banner) | Risk |
|---|
Select a port to see what it means and how to harden it.
Exercise: passive or active?
⚠️ Warning Signs
- Cleartext services (Telnet, FTP) exposed
- Databases and SMB reachable from untrusted networks
- Version banners revealing outdated software
- Scanning without written authorisation
🛡 Defences
- Close or firewall everything not needed
- Replace cleartext protocols with SSH/SFTP/HTTPS
- Monitor for scans with IDS (e.g. Suricata)
- Minimise public OSINT exposure of staff and systems
🎓 Final Quiz
20 SY0-701-style questions across all five domains. Pass mark 70%.
🤵 Social Engineering
Attackers exploit trust, fear, and urgency.
What is Social Engineering?
Social engineering manipulates people into giving up confidential information. It targets the human element rather than technical vulnerabilities.
Decision Trainer: What would you do?
🎭 Tactic Reference
Quick definitions of the most common social-engineering techniques.
Pretexting
Inventing a false identity or scenario (fake IT, auditor, vendor) to extract info.
Baiting
Tempting the victim with something attractive — free download, USB stick, gift.
Tailgating
Slipping into restricted areas behind authorized people.
Vishing
Voice phishing — phone calls impersonating banks, IT, or government.
Smishing
SMS-based phishing with fake delivery, bank, or 2FA messages.
BEC / CEO Fraud
Impersonating an executive to authorize wire transfers or gift-card purchases.
Quid Pro Quo
Offering a "favor" (free help, prize) in exchange for credentials or access.
Watering Hole
Compromising a site the target group already trusts and visits.
⚠️ Common Tactics
🛡 Defense
🎓 Quick Quiz
An attacker calls pretending to be from your bank's fraud team and asks for your one-time SMS code. This is: