Ridgeline Certified Detection Engineer (RCDE)
Exam objectives, RCDE-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. Strategy 10%
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.
- 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
- 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
- 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%
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.
- 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
- 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
- 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
- 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
- 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%
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.
- 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
- 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
- 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
- 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%
Planning purple-team tests and reading their results: what was logged, what alerted, what was blocked, and what to fix first.
- 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
- D2 Interpret test results
- Separate logged, alerted and blocked in a results matrix
- Determine why an emulation or a replay produced no alert
- 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%
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.
- 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
- 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
- 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%
Turning a hunt's findings into a detection that keeps the signal and drops the benign activity the hunt found.
- 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
- 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
- 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%
Running detections as code: reviewing a pull request, reading CI and conversion failures, and deploying safely.
- 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
- 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
- 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