SteadfastIQ

SteadfastIQ Blog

GCIH prep: thinking like an incident handler

About a 5-minute read

If Security+ asks whether you know the language of security, GIAC Certified Incident Handler (GCIH) asks whether you can work an incident. The job title in the exam name is the point. You are not being tested on whether you can admire an attack. You are being tested on whether you can detect it, investigate it, and respond without making the situation worse.

This guide is a study plan for the GCIH full course on SteadfastIQ, used with the blue-team campaign in Hack the Globe. SteadfastIQ is not affiliated with, endorsed by, or sponsored by GIAC or SANS. Always treat the official GCIH page as the source for exam shape and objectives.

What to expect from the exam, hedged on purpose

According to GIAC’s current public exam description, GCIH is a proctored exam with 106 questions and a four-hour window, and it includes CyberLive hands-on lab challenges (performance-based tasks) alongside other items. GIAC has published a 69% passing score for exam versions released on or after May 10, 2025. Confirm the current number of items, duration, passing score, and the CyberLive format on the official page when you register, because GIAC does update those details.

Two consequences follow for study. First, four hours with hands-on tasks means you need practice doing work, not only recognizing terms. Second, a passing score around that published mark still leaves no room for a whole topic you skipped.

The outline is a map of investigations, not a tool catalog

GIAC publishes an objective list for GCIH rather than a short set of weighted domains like CompTIA’s. In our catalog we teach to that list, and we do not invent official weights that GIAC does not publish. The themes, though, are consistent: how passwords are attacked and defended, how exploitation and post-exploitation look on a network and an endpoint, how web application and API attacks show up, how you investigate with logs and packet or host evidence, and how you run incident response itself.

That is why “thinking like an incident handler” is a better study slogan than “learn every tool in the courseware.” Tools change. The questions under the tools do not: What evidence do I have? What is the scope? What do I preserve? What do I change? What do I tell the rest of the team?

Keep the official objective list next to the course. When you finish a video, a lab, or a range level, write the objective ID or title it touched. If you cannot, the session was too vague.

A mindset you can practice on purpose

Incident handlers get paid to be calm and specific. You can practice that in study:

  • Start with evidence, not with a theory. Open the log, the alert, the brief, or the lab state, and write three facts before you name the attack.
  • Think in blast radius. A single compromised account is not the same incident as a domain-wide problem. Your first actions should match the size of what you know.
  • Preserve, then change. If a lab or a range level lets you collect a fact before you remediate, collect it. Exams and real incidents both care that you did not destroy the only copy of the story.
  • Close the loop. After you apply a control, look for the sign that it worked. “I think that’s fixed” is not a finding.

Hack the Globe is built for those habits. The blue-team campaign is 26 levels on a fictional company network. You are there to hold the network: read what it is telling you, act, and prove it. The range is playable on a phone, so a single investigation can happen when you have forty minutes and no desk, though a keyboard is still better for anything you have to type carefully.

A study plan that leaves room for hands-on work

Give yourself more calendar than you would for a purely multiple-choice exam, because CyberLive-style tasks punish rust. An eight-week shape is reasonable if you are also working a job; six is possible if you already handle alerts for a living.

Weeks 1–2: Incident response and investigation foundations. Use the course videos and study guide to lock the IR process in your own words (identification, containment, eradication, recovery, lessons learned — or the phrasing GIAC uses in the current objectives). Start flashcards early for terms you already mix up. Play blue-team levels 1–4 on the range, including the free sample, to learn the interface before the content gets dense.

Weeks 3–4: Attacker techniques as a defender would see them. You still need to understand password attacks, exploitation, endpoint pivoting, and web or API abuse, because you cannot triage what you cannot recognize. Study those objectives from the defender’s chair: what would this look like in a log, on a host, or in an alert? Do the hands-on labs in the course. Interleave a few red-team levels so the attacker’s steps are concrete, then return to blue and investigate the same kind of activity.

Weeks 5–6: Network, log, and host investigations. This is the heart of the exam’s hands-on personality. Slow down. In each lab, narrate what you are looking at. In each range level, write the three facts before the action. Mixed practice questions go on a timer now, in shorter sets, so you can review deeply.

Weeks 7–8: Cloud, modern investigation topics, and full rehearsals. The current objective list includes cloud credential and data issues and newer investigation themes. Do not leave them for a last night. Check the official list so you cover what is actually published, including any objectives that mention current techniques. Then run longer, timed practice in the course, and replay the range levels you missed or barely cleared.

How the rest of the course supports the range

The GCIH course is a full course environment: objective videos, hands-on labs, flashcards, practice questions, and a study guide. Use videos to put an objective into your head, labs and the range to put it into your hands, flashcards for the language you must not fumble, and practice questions to find holes while you still have time to fix them.

Because the official exam includes hands-on challenges, treat every lab as a dress rehearsal for reading a prompt under time. If you get stuck, use the study helper in the lab the way you would use a senior colleague: ask for a nudge, then do the work yourself. The exam will not have the helper. Your notes will.

Ethics and scope still apply on the defensive side

Incident handlers sometimes have more access than anyone in the company. That is a trust, not a toy. Course labs and the range are authorized simulations. Do not take techniques, payloads, or “just checking” hunts to systems you are not authorized to investigate. The same professionalism you would show in a SOC applies to study.

Start with one investigation

Open the GCIH course and the official objective list. Then open Hack the Globe, play the blue-team sample, and write three facts from the brief before you act. If you also need a broader baseline, the Security+ study guide is a good companion, but GCIH study should stay close to investigation and response.

Thinking like an incident handler is a habit you can build on purpose. The course gives you the map. The range gives you a place to practice the habit tonight.

Open the coursePlay Hack the GlobeAll certifications