Ridgeline Certification

RCSE · Official exam study guide · RCSE-01

Ridgeline Certified Security Engineer

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

Introduction

The Ridgeline Certified Security Engineer (RCSE) exam assesses your ability to engineer the controls of a Microsoft 365 and Entra ID estate: authentication and Conditional Access, privileged and application access, device trust and endpoint protection, data protection and the detection platform, and to change and prove them without breaking the business.

Each question gives you configuration and its results (a policy export, sign-in and report-only results, a compliance report, audit events, DLP matches, a change record) and asks what they show or what you would do. The exam has no hands-on lab: it tests the judgment you bring to configuration.

Who should sit it. Security engineers, identity and endpoint engineers, and security architects who own the configuration of a Microsoft 365 and Entra ID estate. Product behavior a question turns on is stated in the brief or an exhibit, so the exam tests judgment, not menu recall.

Recommended experience. Working experience of configuring identity, endpoint or data controls in Microsoft 365 and Entra ID. No course is required to sit the exam.

Exam specifications

ExamRCSE-01
Questions60
Duration2 hours 30 minutes (150 minutes), on one clock for the whole exam.
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. Conditional Access policy exports and sign-in results, including report-only, Directory roles, PIM settings, access reviews and audit events, Application permissions, consent settings and service principal activity, Device compliance, EDR sensor health, attack surface reduction audits and antivirus settings, Sensitivity labels, DLP and auto-labeling matches, sharing and retention settings, SIEM data sources, ingestion, automation rules and response logs, change records. Where a setting, a result or a product's behavior matters, the question or its exhibits supply it.
  • Frameworks. Zero Trust principles (NIST SP 800-207) and phishing-resistant authentication (NIST SP 800-63B) at the level of their ideas.
  • Platform. Microsoft 365 and Entra ID, examined as configuration decisions, never as menu paths or licence names.

Skills measured

The same list is published on its own page to print or save: RCSE skills measured.

Skills measured as of November 21, 2026.

Audience profile

You configure and maintain the security controls of a Microsoft 365 and Entra ID estate: identity and authentication, Conditional Access, privileged and application access, device compliance and endpoint protection, data protection, and the detection platform the SOC relies on. You plan changes to those controls, roll them out in stages, and show evidence that they work.

You work with identity, endpoint, messaging, data owners and the SOC.

Skills at a glance

  • Design identity architecture and authentication (15–20%)
  • Engineer Conditional Access (15–20%)
  • Manage privileged access and governance (15–20%)
  • Engineer endpoint security (15–20%)
  • Protect data (10–15%)
  • Configure the detection and response platform (10–15%)
  • Design, change and validate controls (15–20%)

Design identity architecture and authentication (15–20%)

Secure tenant administration

  • Separate privileged accounts from daily accounts and from on-premises synchronization
  • Design emergency access accounts, including storage of their credentials, methods and monitoring
  • Identify the tier of identity infrastructure, including synchronization servers
  • Remove sign-in from accounts that do not need it, including shared mailboxes

Implement phishing-resistant authentication

  • Select authentication methods for a requirement, including FIDO2 security keys, passkeys and certificate-based authentication
  • Plan the registration of new methods, including Temporary Access Pass settings
  • Restrict security information registration and self-service password reset
  • Plan the retirement of weaker methods without stranding users

Design trust beyond the tenant

  • Configure cross-tenant trust for partner MFA
  • Evaluate federated against cloud authentication

Engineer Conditional Access (15–20%)

Interpret policy results

  • Interpret sign-in results for a policy, including success, failure and not applied
  • Interpret report-only results and plan enforcement from them
  • Identify which policies applied to a sign-in and what each enforced

Design policy scope and exceptions

  • Design exclusions with an owner, a purpose and an expiry
  • Evaluate named and trusted locations as a policy condition
  • Block legacy authentication and plan for the clients that depend on it

Close attack paths

  • Block device code flow and other authentication flows that are not needed
  • Identify the gap a policy left open in a sign-in sequence
  • Recommend detections for attempts against a policy

Manage privileged access and governance (15–20%)

Design administrative roles

  • Select the least privileged role for a task
  • Configure PIM activation settings, including approval, duration, MFA and notifications
  • Scope administration with administrative units and role-assignable groups
  • Require dedicated devices and phishing-resistant sign-in for administrative roles

Govern access

  • Configure access reviews, including reviewers, recommendations and actions on denial
  • Configure access packages with approval and expiry
  • Govern guest accounts

Govern applications and workload identities

  • Evaluate application permissions, including permissions that can assign roles
  • Scope application access to the resources an integration needs
  • Select credentials for workload identities and manage their expiry
  • Configure user consent and admin consent requests

Engineer endpoint security (15–20%)

Configure device compliance

  • Configure compliance policies and the tenant default for devices with no policy assigned
  • Configure grace periods for noncompliance
  • Include device risk from endpoint detection and response in compliance

Configure attack surface reduction

  • Evaluate attack surface reduction audit results and move rules to block
  • Configure per-rule exclusions
  • Configure network protection, application control and device control

Maintain endpoint protection

  • Identify devices with missing or impaired sensors
  • Configure antivirus exclusions, tamper protection and passive and block modes
  • Remove standing local administrator rights and shared local passwords
  • Configure macOS permissions the EDR needs

Protect data (10–15%)

Implement labels and data loss prevention

  • Configure default and automatic labeling
  • Evaluate simulation results for DLP and auto-labeling policies
  • Configure DLP exceptions and actions, including policy tips and overrides
  • Assess the effect of encrypting labels on external partners
  • Restrict sharing links

Implement retention

  • Configure retention for records and legal holds
  • Configure insider risk policies for departing users

Control AI assistants and agents

  • Identify over-shared content before enabling an AI assistant
  • Configure how an agent authenticates and what actions it may take
  • Govern agents built by business teams

Configure the detection and response platform (10–15%)

Manage security data

  • Identify detections that lack the data they query
  • Plan data collection against a budget and storage tiers
  • Monitor data source health

Configure automated response

  • Configure remediation levels by device group
  • Configure automation rules and playbooks in proportion to the signal
  • Test automated response end to end

Design, change and validate controls (15–20%)

Evaluate designs

  • Evaluate a design against the people and devices it must serve
  • Identify the risk a design accepts
  • Design access to sensitive systems by identity rather than network location

Manage change

  • Validate a change against everyone it affects
  • Plan staged rollouts and rollback, including access for whoever rolls back
  • Manage policies as code and detect configuration drift
  • Document exceptions with an owner, compensating controls and an expiry

Prove controls work

  • Test that a control allows what it should and refuses what it should
  • Select measures that show coverage
  • Identify what the records cannot show

The skills listed under each objective illustrate how it is assessed; related topics may be covered. Where a product's behavior matters to a question, the question or its exhibits state it.

Change log

BeforeNowChange
All skill groupsFirst published

Question formats

Individual questions

The first 14 questions stand alone. Most carry no exhibit and ask for a design judgment engineers make often; some carry one: a report or a set of values.

Case studies

Each case study is one situation that unfolds over several questions: a catch-all exclusion group, a policy in report-only, a device code in a chat message, a leaked application secret, compliant by default, an AI agent with its author's access, a change that locked out administrators. It opens with a brief in tabs (Organization, Environment, What has happened so far, Requirements and constraints), then four exhibits. The brief and exhibits stay on screen beside every one of the case's questions.

The brief matters. Who must keep working, what the business has agreed and what a change may not break 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.

Preparing

The table suggests one way to practice each area and what readiness looks like. It is a guide, not a syllabus: the skills measured above are what the exam assesses.

AreaPracticeYou are ready when
Identity architecture and authenticationList every account that can administer your tenant, where its password is set and how it signs in.You can name each path from the on-premises domain or a phishing page to tenant control, and the change that closes it.
Conditional Access engineeringExport your Conditional Access policies and, for one week of sign-ins, explain every one that no enforced policy covered.You can say what each policy did from its results, and which exclusions are gaps.
Privileged access and governanceList every role holder and every application with application permissions, with its owner and last use.You can justify each assignment against the job, and remove the rest.
Endpoint security engineeringCompare your device compliance report with your EDR's device list and your asset inventory.You can explain every device that is compliant, unprotected or unknown.
Data protectionRun a DLP and auto-labeling policy in simulation on one data type and read every match.You can say what enforcement would break and how you would fix it first.
Detection and response platformFor each production detection, check that the table it queries has data today.You can name every rule that cannot fire and the data it needs.
Architecture, change and validationWrite the change plan, rollback and test for one Conditional Access change, then run it in report-only.Your plan names who rolls back, how they sign in, and the evidence that the control works.

Readiness check

Before you book an attempt, check that you can:

  • Find the path from the on-premises domain to tenant administration, and close it
  • Choose methods a relayed phishing page cannot use, and roll them out without stranding users
  • Read what a Conditional Access policy did from its results, report-only included
  • Find the exclusion, trusted location or flow that turned a policy into a gap
  • Design roles, reviews and application permissions to the least each job needs
  • Make device compliance mean a device met a policy, today
  • Move protections and data controls from audit to enforcement without breaking the business
  • Prove a control works, and say when the records cannot show it

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

Results over settings

A policy that is enabled may not apply, a device that is compliant may meet no policy, and a rule that runs may have no data. Judge a control by what its results show.

Changes have users

Several answers are right in principle and wrong on the day. Read who a change affects, and what must be ready first.

Resources

Official references

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

SubjectReference
Zero Trust designNIST SP 800-207, Zero Trust Architecture
Phishing-resistant authenticationNIST SP 800-63B, Authentication and Authenticator Management
Conditional AccessWhat is Conditional Access? (Microsoft Learn)
Secure configuration baselinesSecure Cloud Business Applications (SCuBA) Project (CISA)

Ridgeline courses (optional)

Ridgeline training covers the exam's skills; it is one way to prepare, never a requirement. Core: ARC501 Microsoft 365 Security Architecture, plus ARC502 Entra ID Identity and Access Management or ARC407 Defending Entra ID. Recommended: ARC402 Endpoint Security Engineering, ARC404 Conditional Access Design, ARC403 Microsoft 365 Data Security Engineering, SEC301 Microsoft Security Operations. 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 28 minutes for the 14 individual questions, 112 minutes for the case studies (about 2.4 minutes a question), and 10 minutes to review flagged questions. Some cases take longer than others.

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.
  • Every answer 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, 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 different 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 versionRCSE-01
Skills measured as ofNovember 21, 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.