Ridgeline Certification

RCDE · Official exam study guide · RCDE-01

Ridgeline Certified Detection Engineer

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

Introduction

The Ridgeline Certified Detection Engineer (RCDE) exam assesses your ability to interpret technical evidence, evaluate detection logic and make defensible engineering decisions across the detection lifecycle: strategy, rule design, data, testing, tuning and operations, hunting, and detection as code.

Each question gives you evidence (a rule, log rows, a configuration, a pipeline result, a ticket) and asks what it supports or what you would do. The exam has no hands-on lab: it tests the judgment you bring to the evidence a lab or a production system would produce.

Who should sit it. Detection engineers, and SOC analysts and threat hunters who write and maintain detections. The exam is fair to an engineer from any stack: rules appear in KQL, SPL and Sigma, and where a platform detail matters, the question supplies it.

Recommended experience. Working experience with security telemetry and with reading detection rules in at least one of KQL and SPL. No course is required to sit the exam.

Exam specifications

ExamRCDE-01
Questions60: 10 individual questions, then 10 case studies of 5 questions each
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

  • Rule languages. KQL, SPL and Sigma, read rather than written: you say what a rule matches and misses. Questions about query work show KQL and SPL side by side.
  • Telemetry. Windows endpoint (Sysmon and EDR), Linux (auditd and syslog), AWS CloudTrail, Identity (Entra ID and a non-Microsoft provider), Network (Zeek, DNS and proxy), Email, Detection pipeline and operations data. Where a field or an event's meaning matters, the question or its exhibits supply it.
  • Frameworks. MITRE ATT&CK technique IDs and names.
  • Platforms. No question depends on one vendor's product.

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: RCDE-01 exam objectives.

A. Strategy

10% of the exam

Turning threat intelligence into a build plan against the data you have; reporting coverage to leadership with the evidence behind it, and saying what it does not show.

  1. A1 Prioritize detection work
    • Rank a backlog by the threat model, the data actually collected and the effort each item needs
    • Decide where an in-house team adds value beside vendor-supplied content
    • Set a quarter's detection plan from threat intelligence and stated capacity
  2. A2 Choose durable signals from threat intelligence
    • Judge which indicators and behaviors survive an attacker's routine changes
    • Weigh a report's confidence and age before building on it
    • Select the behavior a detection should key on from emulation evidence
  3. A3 Report detection coverage honestly
    • Determine what a coverage figure counts and what it leaves out
    • Select the measure and the statement the evidence supports for leadership
    • Recognize when a coverage target has started to distort the work

B. Rule design

20% of the exam

Writing a detection requirement from an incident; reviewing deployed rules against raw events and alerts: behavior over artifacts, stable identifiers over names, and exclusions judged for the evasion risk they carry.

  1. B1 Turn an incident into a detection requirement
    • Select the draft requirement that is specific, testable and tied to the incident
    • Separate the causes a detection can address from those it cannot
  2. B2 Interpret what a rule matches and misses
    • Read KQL, SPL and Sigma logic against raw events without running it
    • Find the condition that makes a rule silent or noisy, including negation, missing fields and event semantics
  3. B3 Select the rule logic that meets a requirement
    • Choose between candidate rules shown as code, each run over the same events
    • Test capabilities rather than single values, and sequences rather than single events, where the requirement needs it
  4. B4 Evaluate exclusions and the evasion risk they carry
    • Identify which attributes an exclusion relies on and who can reproduce them
    • Prefer narrow exclusions supported by evidence, and handle exclusion requests within the requirements
  5. B5 Interpret alerts and events for severity and attack sequence
    • Determine which event should have raised the highest-priority alert and when the intrusion was first detectable
    • Map a sequence of events to ATT&CK techniques and judge what a related event establishes

C. Data

18.3% of the exam

Choosing what to onboard against an ingest budget; finding logging gaps in audit and Sysmon configuration; mapping fields and proving parity when moving between SIEMs.

  1. C1 Select data sources and collection within constraints
    • Choose a collection option that meets a budget and supports the required detections
    • Explain the cost of collecting everything and filtering later, and who owns a suppression list
  2. C2 Find and close logging gaps
    • Read audit policy, auditd and Sysmon configuration to find techniques left invisible
    • Select the configuration change that closes a gap within stated constraints, and what it brings with it
  3. C3 Interpret field, time and format problems in data
    • Diagnose time zone, sampling, parsing and case-handling problems from an event
    • Determine which source can attribute activity to a process or user
  4. C4 Prove data completeness and parity
    • Select the check that proves every expected source still sends data
    • Evaluate field mappings and parity standards when a rule moves to another SIEM, including retention obligations

D. Testing

11.7% of the exam

Planning purple-team tests and reading their results: what was logged, what alerted, what was blocked, and what to fix first.

  1. D1 Plan tests that answer a coverage question
    • Distinguish what unit tests, emulation and replay each prove
    • Include benign samples so a test catches over-matching
  2. D2 Interpret test results
    • Separate logged, alerted and blocked in a results matrix
    • Determine why an emulation or a replay produced no alert
  3. D3 Turn test results into fixes and supportable statements
    • Recommend the next step for a gap the test exposed
    • Select the statement about coverage the evidence can support

E. Tuning and operations

18.3% of the exam

Using SOC outcome statistics and analyst feedback; tuning a noisy rule to a goal without losing what it must catch; keeping rules healthy through ingestion delay, failed runs and silent sources.

  1. E1 Use alert outcomes and analyst feedback
    • Judge when disposition data can be trusted as labels
    • Decide what benign true positives, fast closes and precision and recall call for, including retirement proposals
  2. E2 Tune a rule to a goal without losing what it must catch
    • Evaluate proposed changes against an alert budget and the behavior the rule must keep detecting
    • Select suppression and exclusion logic that removes noise without hiding an attack
  3. E3 Keep rules healthy in operation
    • Tell a genuinely quiet rule from one that cannot see its data
    • Select the health check that notices failed runs, parser changes and silent sources in time

F. Hunting

10% of the exam

Turning a hunt's findings into a detection that keeps the signal and drops the benign activity the hunt found.

  1. F1 Form and run a testable hunt
    • Recognize a hypothesis that evidence can confirm or refute
    • Select stacking and beaconing analysis suited to the data
  2. F2 Judge what hunt evidence establishes
    • Determine what an alert or a hunt finding does and does not prove
    • State the limits of a hunt that found nothing more
  3. F3 Turn hunt findings into a durable detection
    • Select the rule that keeps the malicious pattern and drops the benign activity the hunt found
    • Estimate the rule's daily load and handle exclusion requests before it ships

G. Detection as code

11.7% of the exam

Running detections as code: reviewing a pull request, reading CI and conversion failures, and deploying safely.

  1. G1 Review detection changes as code
    • Evaluate a pull request against its fixtures and the rule's requirements
    • Select the change that fixes noise without weakening the rule
  2. G2 Interpret pipeline and CI evidence
    • Diagnose drift, conversion and identity problems from pipeline output
    • Select the control that stops a bad change at review time
  3. G3 Release, schedule and roll back safely
    • Determine the safe way to stop or restore a rule under the change policy
    • Set a schedule and look-back that tolerate ingestion delay

Question formats

Individual questions

The first 10 questions stand alone. Most carry one exhibit: output from a detection tool or platform, a rule, a configuration, a log line or a metric. Some offer rules or queries as the answers; read every line, because the options differ in one condition.

Case studies

Each case study is one situation that unfolds over 5 questions: a rule reviewed after its first month, an alert, a purple-team result, a tuning request, a migration. It opens with a brief in tabs (Overview, Environment, Current detection state, Requirements and constraints), then two to five exhibits: the rule as deployed, the raw log rows with the noise around the signal, and working documents such as an alert queue extract or a tuning ticket. The brief and exhibits stay on screen beside every one of the case's questions.

The requirements matter. An alert budget, how exclusions must be scoped, a change freeze or a detection time objective often decides between two answers that are otherwise sound, as it would at work.

The sample case study is a complete 5-question 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
StrategyTake a recent threat report and your own data inventory; rank the detections you would build first.You can justify the order and name a coverage claim the data does not support.
Rule designPut KQL, SPL and Sigma rules beside the raw events they ran over and predict each match and miss.Your predictions hold when you run the rule, and you can say which attributes each exclusion trusts.
DataRead an audit policy, a Sysmon configuration and a sample of ingested events side by side.You can name the techniques the configuration leaves invisible and the change that closes each gap.
TestingRead a purple-team results matrix, or run an emulation and compare what was logged, alerted and blocked.You can say what a passed or failed test proves, and what it does not.
Tuning and operationsTake a noisy rule and its alert outcomes; propose changes against an alert budget.You can say what each change gives up, and tell a quiet rule from one that has lost its data.
HuntingRun a hunt over a week of data with a written hypothesis, then draft the rule it suggests.Your rule keeps the finding and drops the benign activity the hunt surfaced.
Detection as codeReview real detection pull requests, CI output and conversion failures.You can decide whether a change is safe to ship and how to roll it back.

Readiness check

Before you book an attempt, check that you can:

  • Say what a KQL query, an SPL search and a Sigma rule match, and what they miss, without running them
  • Name the telemetry a detection needs and find where collection leaves a gap
  • Assess an exclusion for the attributes it trusts and who could reproduce them
  • Interpret positive and negative test results, and logged, alerted and blocked
  • Evaluate a tuning change against an alert budget and what the rule must still catch
  • Tell a quiet rule from a rule that cannot see its data
  • Review a detection pull request and a pipeline failure
  • Say when the evidence supports a conclusion and when it does not settle it

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

Evaluating exclusions

For every exclusion, identify which attributes it uses, how those attributes are produced and whether an attacker could reproduce the excluded conditions. Consider the permissions and identities available to the attacker, the reliability of the telemetry and the legitimate activity the exclusion is meant to suppress. Prefer narrowly scoped exclusions supported by evidence, and say what detection gap remains: an exclusion on a service account's activity, for example, also hides an attacker who has taken over that account.

Being honest about evidence

Several answers conclude more than the exhibits show. Sometimes the right answer is that the evidence does not settle the question.

Resources

Official references

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

SubjectReference
Threat-informed detectionMITRE ATT&CK
Detections that resist evasionSummiting the Pyramid (MITRE Center for Threat-Informed Defense)
Sigma rulesSigma documentation (SigmaHQ)
KQLKusto Query Language reference (Microsoft)
SPLSplunk Search Reference
Windows endpoint telemetrySysmon (Microsoft Sysinternals)
Linux audit telemetryauditctl(8) manual page
Network evidenceZeek documentation

Ridgeline courses (optional)

Ridgeline training covers the exam's skills; it is one way to prepare, never a requirement. Core: SEC401 Threat Detection Engineering, plus SEC201 KQL for Security Analysts or SEC405 Splunk for Security Analysts. Recommended: SEC407 Detection as Code, SEC408 Sigma Rule Writing, SEC206 Sysmon Configuration and Tuning. 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 20 minutes for the 10 individual questions, 120 minutes for the 10 case studies (about 12 each), 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 versionRCDE-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.