Ridgeline Certified AI Security Engineer (RCAE)
Skills measured
Exam RCAE-01: 60 questions in 2 hours 30 minutes; passing score 70%. To keep a copy, print this page or save it as a PDF from your browser.
Skills measured as of November 21, 2026.
Audience profile
You secure applications and agents built on large language models. You work out where untrusted input reaches a model, contain what agents and their tools can do, protect the data a model retrieves and remembers, check the models, packages and AI-written code a system depends on, test systems before release, and detect and respond when an AI system is misused.
You work with application developers, platform and identity teams, the SOC, and the people who govern AI risk. The exam is fair to a practitioner from any stack: models, frameworks and providers vary from case to case, and where a product's behavior matters, the question supplies it.
Skills at a glance
- Model AI system threats (10–15%)
- Defend against prompt injection and unsafe output (15–20%)
- Secure agents, tools and MCP servers (20–25%)
- Protect data in retrieval and memory (10–15%)
- Manage AI supply chain and model risk (10–15%)
- Evaluate and red team AI systems (10–15%)
- Monitor, respond and govern (10–15%)
Model AI system threats (10–15%)
Map an AI system's architecture
- Identify the components of an LLM application, including model, orchestration, retrieval, tools, memory and user interface
- Trace data flows between users, the model, retrieved content and tools
- Identify where untrusted content enters the context window
Threat model AI systems
- Identify trust boundaries in an AI system
- Map threats to OWASP Top 10 for LLM Applications and MITRE ATLAS
- Prioritize threats by what an attacker gains at each boundary
Defend against prompt injection and unsafe output (15–20%)
Defend against prompt injection
- Distinguish direct from indirect prompt injection
- Identify injection carried by documents, web pages, email and tool results
- Evaluate controls against injection, including instruction hierarchy, input separation and output checks
- Identify which controls reduce injection and which only appear to
Handle model output safely
- Treat model output as untrusted input to downstream systems
- Prevent model output reaching HTML, SQL, shell or code execution unchecked
- Validate structured output before it drives an action
Secure agents, tools and MCP servers (20–25%)
Design agent identity and authorization
- Select between an agent acting with a user's delegated access and acting as its own identity
- Scope an agent's permissions to its task
- Manage non-human identities and their credentials
Secure tools and MCP servers
- Evaluate a tool's or MCP server's permissions, inputs and trust
- Restrict which tools an agent may call, and with what arguments
- Identify tool poisoning and malicious tool descriptions
- Secure MCP server authentication and transport
Contain agent actions
- Require human approval for high-impact actions
- Limit an agent's reach, including rate, scope and spend
- Isolate code an agent runs
- Contain multi-agent systems, where one agent's output becomes another's instructions
Protect data in retrieval and memory (10–15%)
Secure retrieval
- Control what content is ingested for retrieval and who can change it
- Enforce the user's permissions on retrieved content
- Identify poisoned or over-shared content in a knowledge base
Protect sensitive data and tenants
- Prevent sensitive data reaching a model, logs or a provider it should not
- Isolate tenants in shared AI applications
- Secure agent memory against poisoning and leakage
- Apply privacy-preserving techniques where data must be used
Manage AI supply chain and model risk (10–15%)
Secure the AI supply chain
- Verify the provenance of models, datasets and packages
- Identify risks in model formats and model loading
- Evaluate a third-party model or AI service before adoption
Manage AI-written code
- Review AI-written code for security defects
- Identify packages an AI assistant invented or misnamed
Defend models against adversarial ML
- Identify evasion, poisoning, extraction and inversion attacks against the company's own models
- Select defenses in proportion to a model's exposure
Evaluate and red team AI systems (10–15%)
Evaluate security before release
- Design security evaluations for an AI system
- Set release gates from evaluation results
- Read evaluation results honestly, including pass rates and their limits
Red team AI systems
- Plan automated and manual red teaming
- Interpret red team findings and decide what they prove
- Turn findings into fixes and regression tests
Monitor, respond and govern (10–15%)
Monitor AI systems
- Select telemetry for AI systems, including prompts, tool calls and decisions
- Detect misuse, injection attempts and abnormal agent behavior
Respond to AI incidents
- Contain an AI incident, including revoking an agent's access and disabling tools
- Investigate an AI incident from its logs, and state what they cannot show
Govern AI security
- Map AI security controls to NIST AI RMF and ISO/IEC 42001
- Maintain an inventory of AI systems and their risks
- Assess third-party AI services and agents
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
| Before | Now | Change |
|---|---|---|
| All skill groups | First published |