Projects & Labs

Practice That Turns Into a Portfolio.

Reading about cybersecurity only gets you so far. These original project and lab ideas give you something concrete to build, document, and talk about in interviews -- alongside the SpectraShe career roadmaps and guides.

Hands-On Project Ideas

Build Something You Can Show.

None of these require a job, a certification, or expensive hardware -- just a willingness to build, break, and document things in a safe, isolated environment. Always practice in your own lab or with explicit permission, never against systems you do not own or control.

Build a Home Lab

Set up an isolated virtual environment where you can safely practice without touching a real production system.

What you'll build

  • Two or three virtual machines (a target and an attacker/monitoring box) on an isolated internal network.
  • A free SIEM or log-aggregation tool receiving logs from at least one machine.

Skills gained

Virtualization basicsNetwork segmentationLog collection fundamentals

Portfolio write-up

Document your lab topology, what each machine is for, and one problem you had to troubleshoot to get it working.

SIEM Log Triage Exercise

Practice the core SOC analyst skill: scanning a batch of logs, spotting what's suspicious, and deciding what to escalate.

What you'll build

  • A sample set of authentication and firewall logs (from your home lab or a downloadable sample dataset).
  • A short triage pass that flags anomalies and rates their severity.

Skills gained

Alert triagePattern recognitionPrioritization under ambiguity

Portfolio write-up

Write a one-page summary: what you flagged, why, and what you would check next for the two most suspicious entries.

Phishing Email Analysis

Take apart a suspicious email the way an analyst would: headers, links, sender details, and social-engineering cues.

What you'll build

  • Collect a few real-looking sample phishing emails (from public awareness archives, not your own inbox).
  • A checklist covering sender domain, reply-to mismatches, urgency language, and link destinations.

Skills gained

Email header analysisSocial engineering awarenessStructured investigation

Portfolio write-up

Produce a short indicator report for each sample: what tipped you off, and how you'd advise a colleague to verify it safely.

Password Strength Auditing

Learn what actually makes credentials weak or strong, and practice explaining it in plain language.

What you'll build

  • A small set of example passwords (never real ones) of varying strength.
  • An assessment of each one using entropy, reuse risk, and common-pattern checks.

Skills gained

Password policy reasoningRisk communicationBasic entropy concepts

Portfolio write-up

Summarize your findings as guidance you could give a non-technical user, plus the reasoning behind each recommendation.

Network Scanning in a Lab

Practice discovering and documenting what's running on a small network -- entirely inside your own isolated lab.

What you'll build

  • Your home lab network with two or three virtual machines running different services.
  • A scan of the lab network to identify hosts, open ports, and likely services.

Skills gained

Network reconnaissance basicsService identificationDocumentation discipline

Portfolio write-up

Create an asset inventory: each host, its open ports, the service you believe is running, and any configuration you'd flag for review.

Write an Incident Report

Turn a simulated security event into a clear, structured incident report -- a skill hiring teams consistently value.

What you'll build

  • A scenario: use one from your lab exercises above, or write a short hypothetical based on something you've read.
  • A report following identification, containment, eradication, recovery and lessons-learned stages.

Skills gained

Incident response processTechnical writingStakeholder communication

Portfolio write-up

Keep it to one page: what happened, what you did at each stage, and what you'd change next time. This is the single most portfolio-friendly artifact you can produce.

Document Everything

The single best habit you can build across every project here is writing things down as you go: what you tried, what broke, and what you learned. That habit is what turns a weekend of tinkering into a portfolio piece you can talk through confidently. For guidance on packaging this work for applications, see our Portfolio Guide, or bring your questions to the SpectraShe community.