Ridgeline Certification

RCTH study guide

Ridgeline Certified Threat Hunting Specialist (RCTH)
Exam objectives, RCTH-01

Published November 16, 2026. 60 questions in 2 hours 30 minutes; passing score 70%. Every scored question maps to one objective below. To keep a copy, print this page or save it as a PDF from your browser.

A. Hunts from threat intelligence 11.7%

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%

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%

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%

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%

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%

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%

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