Ridgeline Certification

RCTH · Official exam study guide · RCTH-01

Ridgeline Certified Threat Hunting Specialist

What the RCTH exam assesses, how it is delivered, and how to prepare for it, with or without Ridgeline training.

Introduction

The Ridgeline Certified Threat Hunting Specialist (RCTH) exam assesses your ability to hunt across an enterprise estate: turning threat intelligence into hunts, recognizing identity, cloud, endpoint and network tradecraft in hunt results, separating it from administration and ordinary software, and turning findings into escalations, detections and reports.

Each question gives you results (a stack of values across thousands of hosts, beacon scores, sign-ins, Graph activity, DNS shapes, a hunt plan or log) and asks what they show or what you would do. The exam has no hands-on lab and no queries to write: it tests the judgment you bring to hunt results.

Who should sit it. Threat hunters, detection engineers and senior SOC analysts who hunt across an estate. The exam is fair to a hunter from any stack: results are shown rather than written, and where a platform detail matters, the question supplies it.

Recommended experience. Working experience of threat hunting or detection engineering across at least two of identity, endpoint, cloud and network data. No course is required to sit the exam.

Exam specifications

ExamRCTH-01
Questions60: 12 individual questions, then case studies of 6 to 6 questions each, 48 questions in all
Duration2 hours 30 minutes (150 minutes), on one clock for the whole exam. Extra time can be agreed as a reasonable adjustment.
Passing score70%: 42 of 60 correct. Every question carries equal weight.
DeliveryUnsupervised, online, on this site, in a desktop browser. There is no proctor and no identity document check; see exam security.
MaterialsOpen book: your own notes and reference documentation. No help from another person or an AI model.
AttemptsTwo per voucher; 24 hours between an attempt that does not pass and the next
Validity3 years from the day the certification is issued

Assumed knowledge

  • Evidence. Identity provider sign-ins, consent and directory audit, Graph activity, Domain controller events (Kerberos, directory changes), Endpoint process, registry, pipe and persistence collections across Windows, macOS and Linux, Proxy, DNS and firewall records, Software inventories and remote tool logs, Hunt plans, logs, change records and threat reports. Where a field, an event or a platform's behavior matters, the question or its exhibits supply it.
  • Frameworks. MITRE ATT&CK and the PEAK threat hunting framework at the level of their ideas.
  • Platforms. No question depends on one SIEM, EDR or query language.

Exam objectives

The exam is scored in seven areas. Every paper draws the same number of questions from each area, so every candidate sits the same balance, and your result reports your score in each. Every scored question in the pool maps to one of the objectives below, and every objective has questions behind it. The same list is published as a versioned document: RCTH-01 exam objectives.

A. Hunts from threat intelligence

11.7% of the exam

Behavior over indicators, testable hypotheses, baseline and model-assisted hunts (PEAK), and checking data before hunting it.

  1. A1 Turn intelligence into a hunt
    • Build hunts on behavior an attacker must show rather than indicators that rotate
    • Write a hypothesis that names the behavior, the data and what a positive looks like
  2. A2 Run baseline and model-assisted hunts
    • Establish normal for a population and examine every departure
    • Read a model's ranking for what it measures, below the top as well as at it
  3. A3 Check data and coverage before trusting a result
    • Confirm the data holds a known example before hunting it
    • State the populations a hunt's data could not see

B. Identity and cloud tradecraft

20% of the exam

Session replay, consent grants, device code phishing, AzureHound and ROADrecon, Kerberoasting, AS-REP roasting and RBCD.

  1. B1 Recognize session and consent abuse
    • Separate replayed sessions from VPN and mobile network changes
    • Recognize a malicious consent grant and what a password reset does not end
  2. B2 Recognize enumeration and directory attacks
    • Recognize attack path collectors and directory enumeration by fingerprint and pace
    • Read Kerberoasting and delegation chains from domain controller events
  3. B3 Hunt an automated attack framework
    • Choose indicators that survive renaming, and place each hit in its context
    • Turn an attacker's speed into a requirement for detection

C. Endpoint tradecraft

15% of the exam

Built-in tools in attacker patterns, Cobalt Strike and Go implant traces, and persistence stacked across Windows, macOS and Linux.

  1. C1 Recognize framework and built-in tool traces
    • Recognize default framework artifacts, sacrificial processes and implant traits
    • Tell an attacker's use of a built-in tool from administration by its parent and arguments
  2. C2 Find persistence at scale
    • Stack persistence locations across Windows, macOS and Linux and explain rare values with records
    • Pivot from persistence hits to their common cause
  3. C3 State endpoint coverage and leave detections
    • Name the hosts a collection could not see and what that means for a count
    • Write detections from persistence and framework findings

D. Command and control and tunnels

15% of the exam

Beacon timing and jitter, rare and young destinations, generated domains, DNS tunnels, cloudflared, ngrok and Tailscale.

  1. D1 Find beacons by timing and rarity
    • Read intervals, jitter, prevalence and destination age together
    • Use reply sizes and generated domains to find and time a channel
  2. D2 Find tunnels
    • Recognize cloudflared, ngrok, Tailscale and DNS tunnels, and what each exposes
    • Separate approved tunnel use from shadow IT and attacker use
  3. D3 Separate benign beacons and state network coverage
    • Route software that beacons by design to its owner
    • Name the traffic a network hunt did not score

E. Remote access and hand-offs

11.7% of the exam

Remote support and management tools outside approval, instance and tenant checks, and access broker hand-offs.

  1. E1 Find unapproved remote access
    • Check remote tools by instance or tenant, not product
    • Read remote tool installs and logs for unattended access
  2. E2 Recognize access changing hands
    • Recognize a broker's quiet phase and a buyer's arrival
    • State what the evidence can and cannot establish about a sale

F. Separating malicious from benign

15% of the exam

Stacking and rarity, admin against attacker use of one tool, pivoting, scoping out noise, and validating a hunt that finds nothing.

  1. F1 Stack, explain and pivot
    • Treat rarity as a lead and explain values with records
    • Pivot from a finding to its source, and scope out known noise precisely
  2. F2 Separate administrator from attacker
    • Compare source and account with a tool's normal use
    • Clear an administrator's unusual use with records
  3. F3 Validate a hunt that finds nothing
    • Test a method with a planted positive and state its coverage
    • Report a null result for what it is worth

G. Outcomes

11.7% of the exam

Escalation, hand-overs, detections tested on the hunt's data, coverage gaps, and program measures that show outcomes.

  1. G1 Escalate and hand over
    • Escalate confirmed compromise at once, and route policy findings to their owners
    • Write a hand-over that incident response can act on
  2. G2 Leave detections and record gaps
    • Test a detection on the hunt's own data
    • Record coverage gaps and an escalated finding in the hunt report
  3. G3 Report a hunt program
    • Choose measures that show outcomes, not activity
    • Refuse claims the log does not support, and report dwell time honestly

Question formats

Individual questions

The first 12 questions stand alone. Most carry no exhibit and ask for a judgment hunters make often; some carry one: a stack, a log extract or a set of values.

Case studies

Each case study is one situation that unfolds over 6 to 6 questions, as many as the case's depth calls for: a threat report turned into a hunt, a stolen token used to map a tenant, post-exploitation framework pipes, a tunnel on a build server, an access broker handing over, a hunt that finds nothing. It opens with a brief in tabs (Organization, Environment, What has happened so far, Requirements and constraints), then four or five exhibits. The brief and exhibits stay on screen beside every one of the case's questions.

The brief matters. What the data covers, what is approved and who owns a finding often decides between two answers that are otherwise sound.

The sample case study is a complete case in this format, with the answers and the reasoning behind each option. It is not in the exam.

Problem-solution sets

Some case studies give one problem and a goal, then propose a different change in each question. You answer Meets the goal or Does not meet the goal. These answers lock as soon as you give them and cannot be changed from the review screen, so later questions in the set cannot change an earlier judgment. Every other answer can be changed until you finish.

Preparing

The table suggests one way to practice each area and what readiness looks like. It is a guide, not a syllabus: the objectives above are what the exam measures.

AreaPracticeYou are ready when
Hunts from threat intelligenceTake three threat reports and write a testable hypothesis from each, naming the data that would prove it.Your hypotheses rest on behavior that survives a change of infrastructure.
Identity and cloud tradecraftRead a week of your tenant's sign-ins and consents and explain every unusual one.You can tell replay, consent abuse and enumeration from VPNs, phones and approved tools.
Endpoint tradecraftStack one persistence location across your fleet and explain every rare value.Every value you clear rests on a record, and the ones you cannot clear are escalated.
Command and control and tunnelsScore a day of proxy traffic for regular connections and attribute the top twenty.You can separate update services from a channel by prevalence, age and process.
Remote access and hand-offsList every remote access tool in your estate and the instance or tenant each connects to.You can name what is approved, where, and to whom it connects.
Separating malicious from benignPlant a harmless test in your data and confirm a hunt finds it.You can say what your empty results are worth, and where your data is blind.
OutcomesWrite the hand-over for a finding and the detection it should leave, and test the detection on the hunt's period.Your hand-over lets someone act at once, and your detection fires only where it should.

Readiness check

Before you book an attempt, check that you can:

  • Turn a threat report into a hunt on behavior rather than indicators
  • Explain rare values with records before calling them
  • Recognize identity and cloud tradecraft against users, VPNs and approved tools
  • Find a command and control channel among software that beacons by design
  • Tell an approved remote tool from the same tool pointed elsewhere
  • Separate an administrator's use of a tool from an attacker's
  • Say what a hunt could not see, and when an empty result means something
  • Escalate at the right time and leave a tested detection behind

Confidence is not a substitute for practice: work through the sample case study without looking at the answers first.

Rare is where to look, not the answer

Rollouts, vendors and administrators produce rare values too. Explain each with a record before you call it, and look below the top of any ranked list.

Knowing what a hunt could not see

An empty result means something only if the method was tested and the data covered the target. Several answers depend on saying what was not covered.

Resources

Official references

Free documentation for each part of the work. The exam assumes nothing beyond what these cover.

SubjectReference
Attacker techniquesMITRE ATT&CK
A threat hunting frameworkPEAK Threat Hunting Framework (Splunk SURGe)
Choosing durable indicatorsThe Pyramid of Pain (David J. Bianco)

Ridgeline courses (optional)

Ridgeline training covers the exam's skills; it is one way to prepare, never a requirement. Core: SEC402 Practical Threat Hunting with Microsoft Defender XDR and KQL, plus SEC201 KQL for Security Analysts or SEC405 Splunk for Security Analysts. Recommended: FOR403 Network Detection and Forensics, SEC406 Defending Active Directory, SEC401 Threat Detection Engineering. A yearly Ridgeline training plan, or a Business seat, includes one exam voucher a year.

On exam day

Time

A suggested plan, not enforced by the exam: about 24 minutes for the 12 individual questions, 116 minutes for the case studies (about 2.4 minutes a question), and 10 minutes to review flagged questions. Some cases take longer than others, and answers in a problem-solution set cannot be revisited in your review time.

Navigation

  • Flag a question you are unsure of and come back to it from the review screen, which can step through only the flagged or unanswered questions.
  • Unanswered questions count as incorrect, so answer every one.
  • Problem-solution answers lock when given; everything else can be changed until you finish.

If your connection drops

The clock runs on our server and every answer is saved as you give it. Reload the page or sign in again and you return to the same question with your answers intact; the clock keeps running while you are away. If the time runs out before you return, the attempt ends with the answers you gave.

If something fails on our side

If a fault in the exam system affects your attempt, such as the exam not loading or answers not saving, report it from the exam screen or write to certification@ridgelinecyber.com the same day. It is handled under the appeals procedure; where we confirm a fault on our side, the attempt is replaced at no cost.

Permitted materials

  • Allowed: your own notes, your own files, reference documentation and web searches for documentation.
  • Not allowed: any AI model or AI assistant, including AI answers built into search engines and tools; any other person; anything that copies or sends the exam's content elsewhere.

Disputing a question

Report a question you believe is wrong with the link under it on the exam screen, during the exam; it does not stop the clock. After the exam, you can appeal your result on that ground under the appeals procedure. If an appeal about a question is upheld, every attempt it affected is reviewed.

Before you start

  • Check your name on your account: it is printed on your certification exactly as entered.
  • Use a desktop or laptop with a large screen. The exam screen has text size controls and a dark mode.
  • If you need an adjustment, such as extra time, ask before you start: see reasonable adjustments.

Results and policies

You see your result as soon as you finish: your overall score and your score in each area. After an attempt that does not pass, it stays on the exam page until your next attempt. The correct options are not shown, because the questions stay in use. A pass issues your certification at once, with an ID anyone can check at verification. It is valid for 3 years and renews by passing the current version of the exam in its last twelve months; the renewal runs 3 years from your current expiry date.

A voucher gives two attempts at the exam, and starting an attempt uses one. After an attempt that does not pass, the next opens 24 hours later with a new draw of questions.

The candidate agreement

You accept these terms on screen before each attempt (version 2026-11-16):

  1. Identity. You are the person named on this account, and you will sit the exam yourself.
  2. Independent work. You will work alone. You will not get help from another person, an AI model or an automated answer service while the exam is open.
  3. Permitted resources. The exam is open book: you may use your own notes and reference documentation, within the independent-work term.
  4. Confidentiality. The questions, case studies, exhibits and answers are confidential. You will not copy, photograph, record, reproduce, share or discuss them, during or after the exam.
  5. Integrity. You will follow the published exam rules and will not obtain or distribute unauthorized exam material. Suspected misconduct is investigated under the exam security policy and can lead to cancelled attempts or a revoked certification; every decision can be appealed.

The full rules are in the policies.

Document control

Exam versionRCTH-01
Objectives publishedNovember 16, 2026
Candidate agreementVersion 2026-11-16

A change to the objectives, the question formats or the scoring comes with a new exam version and is announced here before it applies.