What RCEF validates
Endpoint forensics is judged on recognition and restraint: seeing the attacker's command line among a morning of administration, the planted service among genuine agents, the stolen session behind a sign-in that passed, and then saying only what the evidence supports. Tools change every year; what attackers leave behind changes more slowly. RCEF assesses that recognition across the endpoints an enterprise actually runs.
Threats, not tools
You read command lines, registry values, plists, cron entries, logs written by attacker tools, ransom notes and rclone configurations. No exhibit is a forensic tool's screen, and you never write a query.
Every kind of endpoint
Windows workstations and servers, domain controllers, macOS, Linux servers and desktops, ESXi, cloud nodes and Kubernetes, and company iPhones and Android phones, all in one enterprise estate.
Current tradecraft
ClickFix lures, infostealers, vulnerable-driver EDR killers, help desk impersonation, supply chain packages, hypervisor ransomware and automated AI-driven intrusions, from current incident reporting.
Honest about evidence
Some questions are answered by saying what the evidence does not settle, as the real ones often are.
What a holder has shown
- The holder can tell an attacker's activity from administration and from software doing its normal job, on the endpoints your estate runs.
- They can order what happened on a host, from initial access to impact, and tie each step to the trace that shows it.
- They know which credentials a compromise exposed and what an attacker can do with each.
- They state findings at the strength the evidence supports, and name what it cannot show.
- They passed a timed, open-book, unsupervised online exam under the candidate agreement within the last three years.
Who it is for
Forensic analysts, incident responders and senior SOC analysts who examine compromised hosts. The exam is fair to an analyst from any toolset: exhibits are the traces attackers leave, never a forensic tool's screen, 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 examine compromised hosts, and it expects you to read the traces attackers leave on several kinds of system.
The exam experience
Most of the exam is case studies drawn from current intrusions, all set in one multinational group's estate. Each gives you the evidence an analyst would have at that point, not a summary of it.
Inside a case study
- The brief. Tabs for the Organization, the Environment, What has happened so far, and the Requirements and constraints. What the SOC has already done, and what the business needs, often decide between answers that are otherwise sound.
- The exhibits. Four or five: command lines, process trees, registry values, plists, cron entries, logs written by attacker tools, records from consoles and devices, and working documents such as tickets. Values agree across a case's exhibits.
- Six questions, following the investigation 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
| Activity | Area | What you work from |
|---|---|---|
| A fake human check on a Windows laptop | Initial access | Proxy log, RunMRU, EDR events, sign-ins, a mailbox audit |
| A Mac infostealer with a root backdoor | Initial access | Quarantine record, shell history, EDR events, an MDM record, a LaunchDaemon |
| Built-in tools from a web shell | Execution and evasion | IIS log, process creation, script block and Defender logs, memory triage |
| An EDR killed with a signed driver | Execution and evasion | Logons, service installs, file timestamps, execution records, a firewall |
| A sideloaded app on an Android phone | Execution and evasion | An MDM record, package details, device events, CRM sign-ins |
| Three ways back on a file server | Persistence | Scheduled tasks, services, WMI subscriptions, logons and retention |
| A web shell on a Linux web server | Persistence | Access log, uploads, audit records, persistence and a database |
| LSASS dumped on shared session hosts | Credential access | A credential dumper's output, process creation, session records, DC logons |
| Kerberoasting and DCSync | Credential access | Ticket requests, service accounts, replication requests, logons |
| Impacket beside an administrator's PsExec | Lateral movement and remote access | Process creation, service installs, network logons, share records |
| A fake IT helpdesk call | Lateral movement and remote access | Teams records, process creation, a remote tool's own logs, the SOC ticket |
| Ransomware from the hypervisor | Collection, exfiltration and impact | Directory changes, ESXi logs, a backup console, a ransom note |
| A malicious package on a Linux desktop | Collection, exfiltration and impact | npm output, EDR records, a secret scanner's results, registry records |
| An automated AI-driven intrusion on a cloud node | Findings | Access log, files and processes, cloud audit, a test authorization |
| Spyware indicators on an executive's iPhone | Findings | Threat notifications, a shutdown log, messages and an MDM record |
Evidence
- Windows workstations, servers and domain controllers (EDR, event logs, registry, file system)
- macOS (unified log, quarantine, launchd)
- Linux servers and desktops (shell history, cron, systemd, audit, web logs)
- VMware ESXi and backup consoles
- Cloud nodes and Kubernetes (cloud audit, metadata, cluster audit)
- iPhone and Android (MDM records, diagnostic archives, device events)
Threats, not tools
Exhibits are the traces attacker tradecraft leaves, never a forensic tool's screen. You never write a query. Windows, macOS, Linux, ESXi, cloud nodes and phones all appear.
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.
Initial access
13.3% of the examEstablishes how an attacker first ran code on a host, from lures, installers, exploited services and web shells, and separates it from the user's ordinary activity.
Objectives
- A1 Establish how attacker code first ran
- A2 Follow initial access to what it gave the attacker
- A3 State the consequences of initial access
Execution and evasion
20% of the examRecognizes attacker execution through built-in tools, encoded scripts and remote services, and the evasion that hides it: exclusions, EDR killers, cleared logs and timestomping.
Objectives
- B1 Recognize attacker execution
- B2 Recognize evasion
- B3 Draw findings from execution evidence
Persistence
15% of the examFinds the ways back an attacker planted, on every platform, among the genuine autostart entries of the system and its software.
Objectives
- C1 Find planted persistence on Windows
- C2 Find planted persistence beyond Windows
- C3 Decide what persistence means for recovery
Credential access
15% of the examRecognizes credential theft from its traces and states which credentials a compromise exposed, and what each lets an attacker do.
Objectives
- D1 Recognize credential theft from its traces
- D2 Determine what a credential theft exposed
Lateral movement and remote access
13.3% of the examTraces movement between hosts and the remote access an attacker installed, against how the same tools and accounts are normally used.
Objectives
- E1 Recognize lateral movement
- E2 Recognize remote access an attacker installed
- E3 Trace the source and what access survives
Collection, exfiltration and impact
13.3% of the examRecognizes staging, exfiltration and destruction, bounds what left from the records, and weighs an attacker's claims against them.
Objectives
- F1 Recognize staging and exfiltration
- F2 Recognize destruction and the removal of recovery
- F3 Bound impact and weigh claims
Findings
10% of the examSeparates attacker from administrator and tool from operator, orders the events, and writes findings at the strength the evidence supports.
Objectives
- G1 Separate attacker from administrator, and tool from operator
- G2 State findings at the strength of the evidence
- G3 Turn findings into action
Exam details and requirements
| Exam | RCEF-01 |
|---|---|
| Format | 12 individual questions, then case studies of 6 to 6 questions each, 48 questions in all |
| Questions | 60 |
| Duration | 2 hours 30 minutes |
| Passing score | 70% |
| Delivery | Unsupervised online, on this site, whenever you are ready. There is no proctor and no ID check; you sit it under the candidate agreement. |
| Materials | Open book: your own notes and reference documentation. No help from another person or an AI model. |
| Extra time | Available on request, as 25%, 50% or 100% more time, under the adjustments policy. Ask before you start the exam. |
| Retakes | Two attempts per voucher; the next opens 24 hours after an attempt that does not pass |
| Validity | 3 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
RCEF 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 RCEF again then takes a full voucher.
Verification
Every RCEF 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 a particular forensic tool?
No. Exhibits show what attackers leave behind, not a tool's interface, and you are never asked to write a query.
Is it only Windows?
No. Cases cover Windows workstations, servers and domain controllers, macOS, Linux servers and desktops, ESXi, cloud nodes and Kubernetes, and iPhone and Android phones. Where a platform's behavior matters, the brief or an exhibit states it.
Is there a hands-on lab?
No. The evidence an examination would produce is in the exhibits. The exam assesses what you recognize in it and what you conclude.
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.