The Weekly Challenge and Defenders Club

The problem nobody puts on a syllabus

Almost everyone who tries to break into defensive security fails the same way. Not on the material — on the calendar. Week one you do four labs. Week three you do one. Week six you open the tab, remember you have to pick something, close the tab, and that's the last time you log in.

Two things cause that. The first is decision fatigue: a catalog of a hundred labs is a hundred small decisions before you've learned anything, and the easy way out is to pick whatever you're already good at. The second is that you're doing it alone. Nobody notices whether you showed up, nobody's stuck on the same thing you're stuck on, and there's no one to ask when a query returns nothing and you can't tell if that's the answer or a mistake.

Two features shipped this week, and they're both aimed squarely at that: the Weekly Challenge and the Defenders Club.

The Weekly Challenge

One lab. Chosen for the entire platform. Live from Monday at midnight Pacific until Sunday at 11:59 PM Pacific. Then it's gone and a new one takes its place.

Everybody plays the same lab in the same window. There's no choosing, no browsing, and no way to swap it for something more comfortable. When you open the dashboard on a Monday, the week's work is already picked and the clock is already running.

It rotates across every discipline

The pick rotates across the whole catalog — detection engineering, detection tuning, security operations, threat hunting, incident response, MITRE ATT&CK mapping, threat modeling, secure system design, code review, and scripting. Some weeks it's a log query. Some weeks it's a design review with no logs in sight.

That range is the point, and it's the part people resist. If you pick your own labs you will drift toward the skill you already have, because finishing something feels better than struggling with something. A rotation you don't control drops you into the disciplines you've been avoiding, which is exactly where the growth is. Nobody gets hired to only write queries.

No walkthroughs that week

Walkthroughs are normally one of the best things on the platform — when a lab beats you, you can spend a token and read how it should have gone. During the Weekly Challenge they're switched off on that lab, for everyone, no exceptions and no tier differences.

You get the lab and your own head, the same as a real shift. The walkthrough comes back the following week if you want to go see what you missed.

The board, the streak, and the badge

Every challenge has its own leaderboard, ordered by who finished first. Because everyone is on the identical lab under the identical rules, it's a straight race rather than a comparison of who picked the easier exercise.

Beating the challenge adds a week to your Challenge Streak. Miss a week and it resets to zero — that's the whole mechanic, and it's deliberately unforgiving, because a streak you can't break isn't a streak. Reach five weeks in a row and you earn Streak Keeper, which sits on your profile as something more meaningful than a completion count: it says you kept showing up for over a month against labs you didn't choose.

The Defenders Club

The other half of the problem is that learning security alone is miserable. The Defenders Club is the Discord where the people using Defend the Org actually talk to each other — free to join, and you don't need to be any good yet.

What's in there:

• People at every stage. Career changers on their first lab, analysts a year into a SOC, engineers who have been doing this for a decade. The gap between you and the person a few steps ahead is the most useful thing in the room.
• Help when a lab has you stuck. Ask, compare approaches, get pointed in the right direction — without anyone spoiling the answer.
• Career talk that isn't recycled advice. Resumes, interview loops, which certs are worth the money and which ones aren't, from people who have recently sat on both sides of the table.
• Livestreams and Q&As. Labs solved live, walkthroughs you can interrupt with questions, and sessions where you bring the thing you've been quietly confused about for a month.
• Giveaways. Memberships, gear, and other things worth showing up for.

The Weekly Challenge gets its own channel, which is where the two features stop being separate things. Everyone in the server is working the same lab, in the same week, with no walkthrough to fall back on. That's a very different conversation from "has anyone done exercise 47." It's the closest thing to a shift handoff you can get outside a real team.

Why these two shipped together

Skill isn't the bottleneck for most people trying to get into this field. Consistency is. The Weekly Challenge removes the decision that stops you from starting, and the Defenders Club supplies the part a platform can't manufacture on its own — other people noticing whether you showed up.

Both also lean on the thing that makes this platform worth your time in the first place: you don't need a home lab, a hypervisor, or a weekend of setup to participate. The challenge opens in your browser on Monday and you work it. And what you build doing it — reading logs, reasoning about attacker behavior, defending a design, writing a detection that survives contact with reality — moves with you to whatever stack your employer happens to run. The tooling changes. The thinking doesn't.

Where to start

The first Weekly Challenge goes live on Monday, September 14 at midnight Pacific. There is nothing to sign up for — it appears on your dashboard when it opens, and it closes Sunday night whether you started it or not.

Do one thing before then: Join the platform to get access to the Defenders Club so you're in the room when the first one drops. If you don't have an account yet, grab a seat and be there Monday.

Five weeks from now, one of two things will be true. Either you'll have a Streak Keeper badge and five disciplines you wouldn't have chosen for yourself, or you'll have meant to start. The difference is smaller than it looks — it's one lab, on a Monday.