The first time I sat the ISC2 CC, I was writing into a fog — a first attempt at a machine I hadn't touched yet. This time is different. I've been inside the exam, I know the terrain, and the prep this round was targeted at the specific gaps. Here's where my head is the day before Round 2 — grounded readiness, not anxious anticipation. 💜

On the ISC2 CC, the scenario questions are a different animal from the knowledge questions — and they're where a lot of people freeze. "What should you do FIRST?" isn't testing what you know; it's testing how you choose. Here's how I'm studying them differently: ISC2's Least/Most/Best framework, reading the call word before the options, and budgeting judgment practice separately from recall. 💜

Two certs on my entry-level path — one I've gone deep on, one I've previewed hands-on. This is the honest version: what the material revealed, and where it exposed gaps I didn't know I had.

Turning raw findings into a threat intelligence report doesn't have to be intimidating. This post walks through mapping a Mirai botnet to MITRE ATT&CK — and explains every tag in plain English, so you can speak the language every SOC team uses.

I failed. Except I didn't. When my ISC2 CC exam stopped at 90 questions, the system gave me bogus results. I could have accepted it. Instead, I found the truth. Now I'm going back in on August 15th to prove it.