Ridgeline Certification

RCDE ยท Detection engineering

Ridgeline Certified Detection Engineer

Demonstrate your ability to analyze detection requirements, evaluate security telemetry, review detection rules, validate coverage and make sound engineering decisions across the detection lifecycle.

Questions
60
Time
150 min
Case studies
10
Voucher
$149, 2 attempts
Try the sample case study

What RCDE validates

Detection engineering is judged on outcomes: rules that catch the attack, stay quiet on normal business and keep working as the estate changes. Many engineers can write a query; fewer can explain why a detection fails, what telemetry would fix it, whether an exclusion opens an evasion route and whether a change keeps coverage. RCDE assesses that judgment.

Assessment based on evidence and decisions

Most of the exam is case studies: a rule as deployed, the raw rows it ran over, a tuning ticket, a pull request. You pass by reading the evidence and choosing a defensible engineering action, which recalled facts alone cannot do.

The whole detection lifecycle

It covers more than writing queries: deciding what to detect, onboarding data, testing with purple teams, tuning against an alert budget, turning hunts into rules, and running detections as code.

Not tied to one SIEM

Rules appear in KQL, SPL and Sigma, and where a platform detail matters the question supplies it. Implementing what you decide still takes knowledge of your own platform; the exam assesses the decisions.

Judgment under real constraints

Briefs carry what the job carries: an ingest budget, a change freeze, a SOC lead who wants the queue cut and a CISO who wants coverage kept. The exam rewards the answer that fits them.

What a holder has shown

  • The holder can review a rule against raw events and find what it misses or over-matches.
  • They judge which attributes an exclusion trusts and who could reproduce them, and tune noise without losing what the rule must catch.
  • They can plan coverage from intelligence and from the data actually collected, and say honestly what it does not show.
  • They can test detections, read pipeline and health data, and keep rules working in production.
  • They passed a timed, open-book, unsupervised online exam under the candidate agreement within the last three years.

Who it is for

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.

There are no prerequisites and no required course: anyone with a voucher can sit the exam. It is written for people who already write, review or maintain detections, and it expects you to read rules in KQL, SPL and Sigma.

The exam experience

Most of the exam is case studies drawn from the activities of the job. Each gives you the evidence an engineer would have at that point, not a summary of it.

Inside a case study

  1. The brief. Tabs for the Overview, the Environment, the Current detection state, and the Requirements and constraints. The requirements, such as an alert budget or a change freeze, often decide between answers that are otherwise sound.
  2. The exhibits. Two to five: the rule as deployed, the raw rows with the noise around the signal, and working documents such as a tuning ticket or a pull request. Query results are produced by a query engine, never typed.
  3. Five questions that follow the situation as it unfolds, with the brief and exhibits beside each one.

Some case studies are problem-solution sets: one problem and a goal, with a different proposed change in each question, answered Meets the goal or Does not meet the goal. Those answers lock once given.

To see how one reads, work through the sample case study, with its answers explained.

What you work from

ActivityAreaWhat you work from
Turning threat intelligence into a build planStrategyAn intelligence extract, a coverage matrix, a data source inventory
Onboarding a data sourceDataSource options with volume, cost and fields, an ingest budget, required detections
Logging gap analysisDataAudit policy and Sysmon configuration extracts, the techniques to cover
Writing a detection requirement from an incidentRule designA postmortem extract and draft requirements
Rule reviewRule designThe rule as deployed, its alerts and the raw rows, across identity, cloud and endpoint
The SOC feedback loopTuning and operationsPer-rule outcome statistics and analyst notes
Tuning to a goalTuning and operationsA noisy rule, its goal, and a proposed change per question
Purple-team planning and resultsTestingA test plan and a results matrix: logged, alerted, blocked
Hunt to detectionHuntingHunt notebook findings
Detection as codeDetection as codeA pull request diff, CI output, a failed conversion, a deploy log
Migrating to a new SIEMDataA field mapping, parity test results, a cutover plan
Rule health in operationTuning and operationsRule run history, ingestion delay, source heartbeat
Reporting coverage to leadershipStrategyA coverage heatmap, the evidence behind it, a draft board statement

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

Rule languages

KQL, SPL and Sigma, in roughly equal measure. Questions about query work show KQL and SPL side by side, and no more than a few case studies are specific to one vendor's platform.

Domains and weighting

The exam is scored in seven areas. Each paper draws the same number of questions from every area, and your result reports your score in each. The exam objectives list what each area covers.

Strategy

10% of the exam

Builds a detection plan from threat intelligence and the data actually collected, ranks it by risk and effort, and reports coverage to leadership with the evidence behind each claim and its limits.

Objectives
  • A1 Prioritize detection work
  • A2 Choose durable signals from threat intelligence
  • A3 Report detection coverage honestly

Rule design

20% of the exam

Turns an incident into a testable detection requirement, and reviews a deployed rule against raw events to find what it misses, what it over-matches and which exclusions an attacker could reproduce.

Objectives
  • B1 Turn an incident into a detection requirement
  • B2 Interpret what a rule matches and misses
  • B3 Select the rule logic that meets a requirement
  • B4 Evaluate exclusions and the evasion risk they carry
  • B5 Interpret alerts and events for severity and attack sequence

Data

18.3% of the exam

Decides which sources to onboard within an ingest budget, finds the logging gaps that leave techniques invisible, and proves a rule behaves the same after a field mapping or a move to another SIEM.

Objectives
  • C1 Select data sources and collection within constraints
  • C2 Find and close logging gaps
  • C3 Interpret field, time and format problems in data
  • C4 Prove data completeness and parity

Testing

11.7% of the exam

Plans purple-team tests that answer a coverage question, and reads the results to separate what was logged, what alerted and what was blocked, and what to fix first.

Objectives
  • D1 Plan tests that answer a coverage question
  • D2 Interpret test results
  • D3 Turn test results into fixes and supportable statements

Tuning and operations

18.3% of the exam

Uses alert outcomes and analyst feedback to decide what to change, tunes a noisy rule to a goal without losing what it must catch, and spots rules that have silently stopped working.

Objectives
  • E1 Use alert outcomes and analyst feedback
  • E2 Tune a rule to a goal without losing what it must catch
  • E3 Keep rules healthy in operation

Hunting

10% of the exam

Takes a hunt from finding to a durable detection, keeping the malicious pattern and dropping the benign activity the hunt surfaced.

Objectives
  • F1 Form and run a testable hunt
  • F2 Judge what hunt evidence establishes
  • F3 Turn hunt findings into a durable detection

Detection as code

11.7% of the exam

Reviews detection changes as code: reads a pull request diff, CI output, a failed conversion and a deploy log, and decides whether the change is safe to ship.

Objectives
  • G1 Review detection changes as code
  • G2 Interpret pipeline and CI evidence
  • G3 Release, schedule and roll back safely

Exam details and requirements

ExamRCDE-01
Format10 individual questions, then 10 case studies of 5 questions each
Questions60
Duration2 hours 30 minutes
Passing score70%
DeliveryUnsupervised online, on this site, whenever you are ready. There is no proctor and no ID check; you sit it under the candidate agreement.
MaterialsOpen book: your own notes and reference documentation. No help from another person or an AI model.
Extra timeAvailable on request, as 25%, 50% or 100% more time, under the adjustments policy. Ask before you start the exam.
RetakesTwo attempts per voucher; the next opens 24 hours after an attempt that does not pass
Validity3 years

Delivery and integrity

  • Before the exam opens you accept the candidate agreement: identity, independent work, permitted resources, confidentiality and integrity.
  • Each attempt draws its own set of case studies and individual questions from the pool, in its own order.
  • The clock runs on our server. A dropped connection loses no answers, but the clock keeps running.
  • Answers are saved as you give them. You can flag questions and return to them from a review screen.
  • You can report a problem with any question from the exam screen, and every report is reviewed. Results can be appealed under the appeals procedure.

Prepare and maintain

The exam study guide covers how to practice for each kind of question and what to expect on the day. Courses are optional; these cover the exam's skills.

Core courses

Recommended

Examined, but not required.

Voucher

$149

Two attempts at the exam. A bought voucher does not expire.

Payment by card through Stripe. The voucher is added to your account as soon as the payment is confirmed. Refunds follow the Refund Policy.

Included with a yearly training plan

A yearly Ridgeline training plan, and each Business seat, includes one exam voucher a year. Link your training account to this site to claim it. It is usable while the plan renews and expires when it ends. Monthly subscribers buy a voucher like anyone else.

Renewal

RCDE is valid for 3 years from the day it is issued. Renew it by passing the current version of the exam in the last twelve months before it expires; the renewed certification runs 3 years from your current expiry date, so renewing early loses no time. A renewal voucher of two attempts is free with a yearly training plan or Business seat and $49 otherwise. We email you 90 and 30 days before expiry. An expired certification still verifies, shown as expired, and holding RCDE again then takes a full voucher.

Verification

Every RCDE has a public verification page showing the holder, the dates and whether it is valid, expired or revoked. The rules behind the certification are in the published policies.

Questions

Do I need to know KQL, SPL and Sigma?

You need to read all three well enough to say what a rule matches and what it misses. You are not asked to write syntax from memory: rules are shown, and the question is what they do.

Is there a hands-on lab?

No. The evidence a lab would produce is in the exhibits: rules, query results, log rows, pipeline output. The exam assesses the decisions you make from it.

Is it tied to one vendor?

No. Where a platform detail matters, the question or its exhibits supply it.

What do I receive when I pass?

A certification ID, issued at once in the name on your account, with a public verification page that shows its status and dates.

Can I use documentation during the exam?

Yes, your own notes and documentation. You may not get help from another person or an AI model.

Ready to sit RCDE?

Read the study guide, then sit the exam when you are ready.

Exam study guide