Why I Built Wolf//Sec (Stdout)

tl;dr — I built a free, interactive Security+ SY0-701 study platform called Wolf//Sec. It’s got labs, not just flashcards. Go play with it.

I’ve been doing security since before I had a career in it.

Not in the “I read a blog post about firewalls” sense. In the “I was poking at network traffic on my family’s LAN in the late ’90s because I wanted to know what was happening on the wire” sense. The curiosity came first. The job title came decades later.

I’ve been a sysadmin. I’ve shipped games. I’ve designed systems architecture for platforms that serve some of the most influential executives on the planet. Security has never been a separate discipline for me — it’s been the lens through which I evaluate everything. Every API endpoint, every trust boundary, every access control decision. You don’t bolt security on. You think in it.

So when I started working through Security+ material — not because I needed someone to tell me what a VLAN is, but because I believe in validating knowledge formally — I ran into something that bugged me.

The Gap

There’s plenty of great Security+ material out there. Seriously. Professor Messer is a gift to the community. Chapple and Seidl’s Security+ Study Guide is rock-solid reference material — I’ve been going through the audiobook and it’s thorough in all the right places. Kenmore’s All-in-One guide is a good complement if you’re stacking certs. The official CompTIA resources are solid. There are study guides, video courses, practice exams, and flashcard apps coming out of every corner of the internet.

But most of it is passive.

You read about access control models. You memorize that MAC uses labels and RBAC uses roles. You do a practice question that asks “Which access control model uses security labels?” and you pick the right answer because you just read the definition ten minutes ago. You feel confident. You move on.

Then the exam gives you a scenario with a hospital, five users, four sensitivity levels, and a write request that violates Bell-LaPadula’s star property — and suddenly the definition isn’t enough.

That’s the gap. The distance between recognizing a term and applying the concept under pressure. Between knowing that SQL injection exists and being able to look at a raw HTTP request log and say “that’s a UNION-based injection targeting the search parameter, and here’s the monitoring indicator that would catch it.”

CompTIA knows this. That’s why SY0-701 leans so heavily on “Given a scenario” questions and performance-based questions. They’re not testing your glossary. They’re testing your judgment.

What I Wanted

I wanted study material that worked the way I actually learn: by doing.

Not by watching. Not by highlighting. By getting my hands on something, making decisions, and seeing consequences. The same way I’ve learned every meaningful thing in my career — by building, breaking, and figuring out why.

I wanted to look at a vulnerability scan report and have to decide which finding is actually critical based on the network architecture, not just the CVSS score. I wanted to classify attacks from raw evidence — HTTP requests and crash dumps — the way you’d actually encounter them in a SOC or during an incident. I wanted to evaluate access requests under four different control models simultaneously and see how the same request gets a different answer depending on the model.

I wanted the thing that forces you to think, not just recall.

It didn’t exist in the form I wanted. So I built it.

What Wolf//Sec Is

Wolf//Sec is a free, interactive Security+ SY0-701 study platform. It’s a section of this site, not a separate product. No accounts, no paywalls, no upsell.

The core philosophy is simple: think offensive, defend everything.

Understanding how attackers think isn’t some advanced concept reserved for red teamers. It’s the foundation of effective defense. When you understand why an attacker would target a specific port, you make better firewall rules. When you understand how injection attacks work at the request level, you write better validation. When you understand what a vulnerability scanner is actually checking, you stop treating every “Critical” finding like the sky is falling.

The platform covers all five SY0-701 domains with interactive labs at the core. A few examples of what “interactive” means here:

Application Attack Identifier — you get raw evidence artifacts (HTTP requests, server logs, crash reports) and classify the attack type. No multiple choice. You analyze, then decide.
Vulnerability Scan Analysis — triage a scan report by actual business risk. Identify false positives. Prioritize remediation under constraints. The way you’d do it at work, not on a flashcard.
Crypto Toolkit — select the right algorithm, hash function, or certificate for the scenario. Not “what does AES stand for” — “why would you choose AES-GCM over AES-CBC here, and what property does that give you?”
Chain of Custody — process forensic evidence collection across incident scenarios. Order of volatility, write-blockers, integrity hashing, documentation requirements.

There’s also a full acronym library with flash cards (because yeah, you still need to know the acronyms), a port reference with quizzes, and an exam strategy guide covering PBQ tactics and time management.

More labs are in progress. The platform is actively growing.

Why Free

Because the cert industrial complex is already expensive enough. The exam costs $400+. Most decent prep courses run $200-500. If you’re early in your career or switching fields, that’s a real barrier.

I’m not building a business here. I’m building a resource. The kind of thing I’d want to exist if I were starting out and didn’t have twenty-five years of context to fall back on.

If it helps people pass, great. If it helps people actually understand security instead of just memorizing enough to pass, even better.

Go Break Things

Wolf//Sec is live. Go poke at it. Try the labs. If something’s broken or confusing, that’s useful information — I’m iterating on this constantly.

Think offensive. Defend everything.

> _