▸ HANDS-ON DEFENSIVE SECURITY · OPEN SOURCE

CYBERSHIELD

9 small, local-first labs that teach the defensive skills teams need as they adopt AI agents, cloud identity, and modern software supply chains. Read the guide, run the script, break the fixture, and learn what the checks miss.

GET STARTED → BROWSE THE LABS ↓ GITHUB ↗
9 HANDS-ON LABS
0 DEPENDENCIES
100% LOCAL & SYNTHETIC
3.9+ PYTHON

Reading About Security
Isn't the Same as Doing It.

Most training stops at slides or needs a cloud account, a vulnerable VM, and an afternoon of setup. CyberSHIELD Labs fit in a lunch break: clone the repo, run one command, and see a real check find a real misconfiguration.

01
NO SETUP TAX

Standard-library Python only. No pip install, no Docker, no API keys, no cloud bill. If you have Python 3.9 or later, you can start now.

02
SAFE BY DESIGN

Every lab uses bundled synthetic data. Nothing touches production systems, and the one network lab refuses to talk to anything except your own machine.

03
HONEST ABOUT LIMITS

Each lab spells out what its checks cannot see. Learning where a control stops is as important as learning what it catches.

9 Labs. One Command Each.

Work through them in order or jump to the area you need. Every lab has a guide, a runnable script, a synthetic fixture, and a takeaway you can apply at work.

LAB 01 — AI AGENTS
AI APPLICATION SAFETY

Flag instruction-like text in untrusted content and tool requests outside an allowlist.

$ python3 -m labs.ai_application_safety.analyze → OPEN LAB
LAB 02 — LEAST PRIVILEGE
CLOUD IAM POSTURE

Audit a provider-neutral policy for wildcard actions, wildcard resources, and public principals.

$ python3 -m labs.cloud_iam_posture.audit → OPEN LAB
LAB 03 — IDENTITY & MFA
IDENTITY THREAT HUNTING

Hunt synthetic auth logs for login-failure bursts and MFA push-fatigue patterns.

$ python3 -m labs.identity_threat_hunting.hunt → OPEN LAB
LAB 04 — DLP & PRIVACY
SENSITIVE-DATA PROTECTION

Detect and redact email addresses, phone numbers, and a demo key pattern in local text.

$ python3 -m labs.sensitive_data_protection.scan → OPEN LAB
LAB 05 — RECOVERY
BACKUP RESILIENCE

Validate simulated backup evidence for encryption, immutability, and recent restore tests.

$ python3 -m labs.backup_resilience.validate → OPEN LAB
LAB 06 — SBOM QUALITY
SOFTWARE SUPPLY CHAIN

Check an SBOM-like inventory for unpinned versions, missing digests, and unknown sources.

$ python3 -m labs.software_supply_chain.audit → OPEN LAB
LAB 07 — WORKLOAD HARDENING
CONTAINER CONFIGURATION

Statically review a Dockerfile for floating base images, root users, and embedded secrets.

$ python3 -m labs.container_configuration.audit → OPEN LAB
LAB 08 — CREDENTIAL HYGIENE
PASSWORD STRENGTH

Estimate strength after discounting common words, keyboard runs, and repeated patterns.

$ python3 -m labs.password_strength.estimate → OPEN LAB
LAB 09 — ATTACK SURFACE
WEB EXPOSURE

Check a local practice server for exposed .git/, backups, and admin paths. Loopback only.

$ python3 -m labs.web_exposure.check --demo → OPEN LAB

Your First Finding
in 60 Seconds.

Lab 9 starts its own throwaway practice server on 127.0.0.1, checks it for commonly exposed paths, and shuts it down again. Nothing leaves your machine.

GETTING STARTED GUIDE ↗
cybershield-labs — zsh
# Clone the repo (no install step)
$ git clone https://github.com/d0uble3L/CyberSHIELD-Labs
$ cd CyberSHIELD-Labs
 
# Scan a throwaway local practice server
$ python3 -m labs.web_exposure.check --demo
 
Checking http://127.0.0.1:55823 ...
[+] Access controlled (403): /admin/
[+] Found (200): /.git/
[+] Found (200): /robots.txt
[+] Found (200): /config.json
[+] Found (200): /backup/
 
# An exposed .git/ can leak your whole source history.
# Now go check that your real servers block it.

Run It. Break It.
Understand It.

Each lab follows the same three-step loop, so the habit carries over to real reviews.

01
RUN THE CHECK

One command against the bundled synthetic fixture. Read every finding and ask why it fired.

02
EDIT A COPY

Fix the risky settings in a copy of the fixture, or add new ones, and rerun. Watch findings appear and disappear.

03
FIND THE GAPS

Every guide lists what the check misses. Try to sneak a risky input past it, then decide how a real control would catch it.

Built for People Who
Learn by Doing.

The labs are small on purpose: easy to read in one sitting, easy to extend, and easy to run in a classroom or a team session.

◆
FOR CAREER CHANGERS & STUDENTS
BUILD REAL INTUITION

Go beyond definitions. See exactly what a wildcard IAM grant, a root container, or an MFA push-fatigue pattern looks like in data.

→ START WITH LAB 1
⚙
FOR SECURITY & PLATFORM ENGINEERS
SHARPEN REVIEW INSTINCTS

Each script is under 200 lines. Read how the check works, then extend it for the configs and logs your team actually ships.

→ EXTEND A LAB
▤
FOR TEAM LEADS & EDUCATORS
RUN A TRAINING SESSION

No accounts to provision and no lab environment to tear down. Hand out the repo link and every attendee is running in minutes.

→ REVIEW SAFETY & SCOPE
⬡
FOR AI & APPSEC BUILDERS
THINK LIKE A DEFENDER

Practice treating retrieved content as untrusted, keeping tool permissions narrow, and redacting data before it reaches a prompt or a log.

→ OPEN THE AI SAFETY LAB

Pick a Lab.
Find Your First Finding.

Open source under Apache 2.0. Runs entirely on your machine. Built by CybersecurityOS.

$ git clone https://github.com/d0uble3L/CyberSHIELD-Labs && cd CyberSHIELD-Labs && python3 -m labs.web_exposure.check --demo