Ridgeline Certification

RCEF · Official exam study guide · RCEF-01

Ridgeline Certified Endpoint Forensic Specialist

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

Introduction

The Ridgeline Certified Endpoint Forensic Specialist (RCEF) exam assesses your ability to recognize attacker activity on compromised hosts from the traces it leaves, across initial access, execution and evasion, persistence, credential access, lateral movement and remote access, collection, exfiltration and impact, and findings.

Each question gives you evidence (command lines, a process tree, registry values, a plist, cron entries, the output of an attacker's tool, a device record) and asks what it shows or what it supports. The exam has no hands-on lab and no queries to write: it tests the recognition and judgment you bring to the evidence a host holds.

Who should sit it. 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.

Recommended experience. Working experience of examining compromised hosts, in forensics or incident response, on at least Windows and one other platform. No course is required to sit the exam.

Exam specifications

ExamRCEF-01
Questions60: 12 individual questions, then case studies of 6 to 6 questions each, 48 questions in all
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

  • 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). Where a field, an event or a platform's behavior matters, the question or its exhibits supply it.
  • Attacker techniques. MITRE ATT&CK at the level of what each technique leaves behind.
  • Platforms. No question depends on one forensic tool or one EDR 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: RCEF-01 exam objectives.

A. Initial access

13.3% of the exam

Lures (LNK, ISO, HTA), ClickFix, fake installers, user overrides of platform checks, exploited edge devices and web shells.

  1. A1 Establish how attacker code first ran
    • Find the first malicious process and the action that started it, among the user's ordinary activity
    • Read lures, installers and platform overrides for what they ran
  2. A2 Follow initial access to what it gave the attacker
    • Recognize exploited services and web shells from their traces
    • Trace what a first foothold took or opened, across host and identity records
  3. A3 State the consequences of initial access
    • Separate the host decision from the incident's real scope
    • Name what the records cannot yet show about what was reached

B. Execution and evasion

20% of the exam

Encoded PowerShell, built-in tools in attacker hands, Defender exclusions, vulnerable-driver EDR killers, cleared logs, timestomping, and mobile permission abuse.

  1. B1 Recognize attacker execution
    • Read encoded scripts, built-in tools and installed apps for what they ran
    • Tell an attacker's use of a tool from its normal use by its parent, account and arguments
  2. B2 Recognize evasion
    • Identify exclusions, vulnerable-driver EDR killers, cleared logs, timestomping and hidden apps
    • Fill a gap in one record from the host's other records
  3. B3 Draw findings from execution evidence
    • Read a logon or a permission against its own baseline
    • State what an execution record proves about data, people and second factors

C. Persistence

15% of the exam

Scheduled tasks, services, WMI, Run keys, COM hijacks and accessibility backdoors; launchd; cron, systemd and SSH keys; ESXi startup scripts; web shells; Kubernetes workloads.

  1. C1 Find planted persistence on Windows
    • Pick planted tasks, services, WMI subscriptions and COM entries from genuine ones
    • Recognize accessibility and registry-stored backdoors
  2. C2 Find planted persistence beyond Windows
    • Recognize cron, systemd, SSH key, launchd, web shell, ESXi and Kubernetes persistence
    • Judge an entry by its path, signer, date and action rather than its name
  3. C3 Decide what persistence means for recovery
    • Place persistence in time and apply it to backups and rebuilds
    • State what the attacker could do while the persistence stood

D. Credential access

15% of the exam

LSASS dumps, saved hives and NTDS.dit, browser and keychain theft, Kerberoasting, AS-REP roasting, DCSync, exported tickets and cloud credentials.

  1. D1 Recognize credential theft from its traces
    • Recognize LSASS dumps, saved hives, directory database copies, keychain and browser theft
    • Recognize roasting, replication and cloud credential harvesting
  2. D2 Determine what a credential theft exposed
    • List the accounts and secrets a theft exposed, including ones no longer signed in
    • State what each stolen credential lets an attacker do, and act on exposure when use cannot be shown

E. Lateral movement and remote access

13.3% of the exam

PsExec and Impacket traces, WinRM, DCOM, RDP and tunnels, SSH pivots, and remote support tools the company does not use.

  1. E1 Recognize lateral movement
    • Identify Impacket, WinRM, DCOM, SSH and tunneled RDP traces
    • Separate an attack tool's movement from an administrator's use of the same mechanism
  2. E2 Recognize remote access an attacker installed
    • Tell the company's remote tools from the same tools pointed elsewhere
    • Read a remote tool's own configuration and logs for unattended access
  3. E3 Trace the source and what access survives
    • Trace movement to its source against the account's baseline
    • Determine what a reset, a revocation or an isolation does and does not end

F. Collection, exfiltration and impact

13.3% of the exam

Archive staging, rclone and cloud uploads, shadow copy and backup destruction, hypervisor encryption, and ransom note claims.

  1. F1 Recognize staging and exfiltration
    • Recognize archive staging, cloud sync tools, dumps in memory and uploads to storage the company does not own
    • Read a command for its direction, destination and filters
  2. F2 Recognize destruction and the removal of recovery
    • Identify snapshot, shadow copy and backup destruction before encryption
    • Locate where encryption ran from the records of the hosts it reached
  3. F3 Bound impact and weigh claims
    • Bound what left from the records, against an attacker's claims
    • Follow impact beyond the host, through published packages, partners and stolen secrets

G. Findings

10% of the exam

Attacker against administrator, tool against operator, sequence, and findings stated at the strength of the evidence.

  1. G1 Separate attacker from administrator, and tool from operator
    • Recognize machine-paced activity and genuine alerts from lures
    • Attribute activity to an operator by source, target and scope, not by a tool's artifacts
  2. G2 State findings at the strength of the evidence
    • Write statements that say what is proved and what cannot be known
    • Distinguish consistency from proof in a sequence of events
  3. G3 Turn findings into action
    • Decide what ends an attacker's access, from the findings
    • Recommend actions for people and devices that remain targets

Question formats

Individual questions

The first 12 questions stand alone. Most carry one exhibit: command lines, a registry value, a file listing, a configuration or a log extract. Some carry none and ask what a trace would look like.

Case studies

Each case study is one situation that unfolds over 6 to 6 questions, as many as the case's depth calls for: a fake human check on a laptop, a vulnerable driver that killed the EDR, ransomware run from the hypervisor, an automated AI-driven intrusion on a cloud node, spyware indicators on an executive's phone. It opens with a brief in tabs (Organization, Environment, What has happened so far, Requirements and constraints), then four or five exhibits. The brief and exhibits stay on screen beside every one of the case's questions.

The brief matters. What the SOC has already done, such as a password reset that did not end a session, and what the business wants, such as a laptop back tomorrow, often decides between two answers that are otherwise sound.

The sample case study is a complete 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
Initial accessTake three recent intrusion reports and find the first malicious process in each.You can name the trace that shows how code first ran, and tell it from the user's ordinary activity.
Execution and evasionRead a day of process creation from a server you know and mark what you would expect to see.You can tell an attacker's use of a built-in tool from an administrator's by its parent, account and arguments.
PersistenceList every autostart location on Windows, macOS and Linux and what normally sits in each.You can pick the planted entry from genuine ones by its path, signer, date and action.
Credential accessFor each credential theft technique, write down the trace it leaves and what the stolen material allows.You can say which accounts a compromise exposed, and why.
Lateral movement and remote accessCompare how your administrators use PsExec, RDP and remote tools with how attack tools do.You can separate the two by source, account, service name and timing.
Collection, exfiltration and impactWork through a ransomware report and mark the staging, exfiltration and recovery-removal steps.You can bound what left from the records, whatever the attacker claims.
FindingsRewrite the findings of a report you know so that each matches the strength of its evidence.Every statement names its trace, and the gaps are stated, not filled.

Readiness check

Before you book an attempt, check that you can:

  • Find the first malicious process on a host and tell it from the user's own activity
  • Recognize built-in tools, encoded scripts and remote services used by an attacker
  • Pick a planted autostart entry from the genuine ones on Windows, macOS and Linux
  • Say which credentials a compromise exposed and what each lets an attacker do
  • Tell an attack tool's lateral movement from an administrator's use of the same tool
  • Bound what left a network from the records, against an attacker's claims
  • Separate a tool's artifacts from the identity of whoever ran it
  • 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.

Reading the trace, not the name

Attackers name their files, tasks and services after the system's own. Judge each one by where it runs from, who signed it, when it appeared and what it does, against the genuine entries beside it.

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, and the report must say so.

Resources

Official references

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

SubjectReference
Attacker techniquesMITRE ATT&CK
Collecting and preserving evidenceNIST SP 800-86, Guide to Integrating Forensic Techniques into Incident Response
Incident response within risk managementNIST SP 800-61 Rev. 3 (April 2025)

Ridgeline courses (optional)

Ridgeline training covers the exam's skills; it is one way to prepare, never a requirement. Core: FOR201 Practical Windows Forensics with KAPE and EZ Tools, plus FOR202 Velociraptor for Endpoint Investigation or FOR502 Memory Forensics. Recommended: FOR203 Malware Triage, FOR301 Incident Triage and First Response, FOR403 Network Detection and Forensics. 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 24 minutes for the 12 individual questions, 116 minutes for the case studies (about 2.4 minutes a question), 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 versionRCEF-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.