48 Hours Out From the ISC2 CC Exam: A Realistic Game Plan for Rest, Review, and Damage Control

In two days, I'll be sitting for the CC exam. Here's my slightly irreverent, zero-panic plan — and what I'm planning to do the moment I walk out of that test center, whatever happens.

At the Pearson Vue test center, I'll be staring down 100 to 125 questions about security principles, access control models, and whatever else ISC2 decides to throw at me.

The temptation right now is real. Watch every YouTube video at 2x speed. Finally, memorize those port numbers I've been quietly avoiding for weeks. Port 443, I see you.

But I've done that dance before — not for the CC, but for defending my thesis. It ended with me crying into a cold cup of chai tea at 2 AM, second-guessing everything I thought I knew, and waking up on the day of the defense feeling like a wrung-out sponge. (Spoiler: I successfully defended it anyway.)

So this time? I'm doing the opposite. Here's my plan — light review, real rest, and a post-exam protocol I wrote for Future Me in advance, because Future Me cannot be trusted to make good decisions in the parking lot of whatever test center I end up at — especially running on adrenaline and bad vending-machine pretzels.

Why I'm Not Cramming (Even Though I Really Want To)

The ISC2 CC isn't about memorization — it's about whether you basically understand security and can avoid avoidable mistakes. If I don't know something by now, an all-nighter won't save me. But a rested brain might help me logic my way through a question I've never seen before.

The goal for the next 48 hours isn't to learn anything new. It's to show up as the sharpest version of what I already know.

So the strategy is: review lightly, rest heavily, and walk in like I belong there. Because I do. Ninety days of work says I've earned the right to trust myself.

The 48-Hour Plan

Day 1

Thursday, June 18

Light Review + One Practice Exam (No Tears Allowed)

Morning

2–3 hrs

Weakest domains only

I'll pull up my weakest spots from past practice tests — incident response (so many steps) and access control models (MAC, DAC, RBAC — oh my). Just those. No new topics.

Midday

1.5 hrs

One full practice exam — timed, no cheating

100 questions. No phone. No sneaky peeks at notes. Just me and my increasingly dramatic internal monologue. This is the last one before the real thing.

Afternoon

1 hr

Wrong answers only — not to spiral, to learn

Why was the right answer right? Where did my brain go sideways? (Spoiler: it was probably overthinking again.) I'll note the patterns, then put the exam down.

Evening

Done

No screens. Walk. Real food. Early bed.

That's it. No doom-scrolling security subreddits. No "just one more flashcard." Crawling into bed early like the responsible-ish adult I'm pretending to be.

Day 2

Friday, June 19

Logistics, Chill Vibes, and Zero Heroics

Morning

1 hr

Summary cards only — then close the book for real

CIA triad. Security frameworks. NIST vs. ISO. One final quiet pass through the highlights. Then I close everything. Actually close it. No "just one more."

Midday

30 min

Get my life together

Two forms of ID. Confirmation email pulled up. Directions confirmed. Comfortable clothes with layers — exam rooms are either the Arctic or a sauna with no in-between. A snack I won't regret.

Afternoon

Brain vacation

Zero exam content — I mean it

Ridiculous music. Stretching like a sleepy cat. Something with zero educational value on TV. My brain has earned a break before the big moment, not more flashcards.

Evening

Prep + sleep

Early dinner. No caffeine. 47 alarms. Then the mirror.

Lay out my clothes. Set approximately 47 alarms. Then look myself in the mirror and say the words I wrote for this exact moment — see below.

The Mirror Moment — Pre-Exam Pep Talk

Saturday, June 20

Exam Day

The Post-Exam Protocol (Written in Advance Because Future Me Cannot Be Trusted)

Walking out of that test center, my brain is going to be a complete mess. So I wrote Future Me a protocol. Future Me is required to follow it.

Post-Exam Protocol

The "Don't Do Anything Stupid" Hour

Min

0–5

Breathe, you beautiful disaster

Step away from the building. Find a quiet corner. Exhale like you just finished a marathon. Because you kind of did — 90 days of work just crossed the finish line, regardless of the result.

Min

5–15

No phone searching. Non-negotiable.

I will not Google "ISC2 CC tricky question access control."The exam is done. The answers are locked in.

Min

15–20

Check results calmly. Like a normal person.

ISC2 gives a preliminary pass/fail on the spot. I'll open the printout like someone defusing a bomb — slowly, deliberately, one breath at a time. Then:

✓ If I passed

Quiet fist pump. One celebratory text to a supportive human. Then go about my day like the newly certified person I am. The debrief post goes up tomorrow.

◎ If I didn't pass

Ten minutes to feel the sting. Ice cream may be involved. Then I remind myself: many smart people fail the first time. I'll jot down what felt hard, put the exam away for a week, and come back with a plan.

Min

20–60

Do literally anything else

Walk. Eat a real meal. Call someone who doesn't know what a firewall is. Watch cartoons. My brain has earned a full vacation regardless of what that printout says.

One week later

Short post-mortem, whatever the outcome

What worked in my prep? What didn't? If I passed, I'll celebrate and map the next step on the roadmap. If I need to retake, I'll schedule it with a better strategy. Either way, I'll write about it here — because that's what this blog is for.

💬 If you're also in the final stretch of CC prep

Put the new material down. Seriously. If you haven't learned it yet, the next 48 hours won't fix that — but they can absolutely break what you already know by filling your head with noise.

Review your weakest spots. Do one timed practice exam. Sleep. Show up. The CC tests whether you can think like a security professional, not whether you've memorized every RFC ever written. Trust the work you've already done.

The debrief post goes up on June 21 — pass or fail, honest and complete. I'll tell you everything.

Meanwhile, The Stack Keeps Growing

Here's something I haven't mentioned much: while I was deep in CC prep, I also completed Microsoft AI Skills Fest 2026 and earned the Credly badge. The last few weeks have been a masterclass in doing too many things at once — and somehow surviving.

The AI Skills Fest content — AI security, prompt injection, how AI systems can fail — ended up reinforcing a lot of what I was already studying for the CC. Happy accident.

I don't share that to collect badges. I share it because certification prep doesn't happen in a vacuum. Life keeps moving, opportunities show up, and sometimes you say yes even when your brain is already at capacity. Building a credential stack isn't about the badges — it's about building the story of what you can actually do.

Speaking of which: once Saturday is behind me, the next target on the roadmap is the Microsoft Certified: Security Operations Analyst Associate (SC-200). I got a free voucher through AI Skills Fest, and I'm using it on exactly the right cert. SC-200 covers Microsoft Sentinel, Defender, KQL-based threat hunting, and incident response workflows — which is basically the technical language of every SOC analyst role.

The reason SC-200 makes sense right now specifically: my data analytics background is actually an edge here, not a liability. KQL is essentially SQL's security-minded cousin. I've been writing anomaly detection queries professionally for years. I'm not starting from zero — I'm translating. And that's the whole point of this transition: you don't leave your skills behind, you redirect them.

🗺️ The post-CC roadmap

CC (June 20) → SC-200 → Security+ → AWS Cloud Practitioner → CySA+. That's the plan. Saturday is just the first checkpoint — not the destination

Follow the Journey

If you've been reading along — thank you. Genuinely. Building this in public has made the preparation feel less like studying alone and more like something worth documenting.

The full exam debrief drops June 21. Subscribe below so you don't miss it — and if you're on your own certification journey, I want to hear about it.

→ Link to the Exam Debrief