You can see it againUnder pressure people bring back shapes and positions long after the wording has gone.
Picture superiority · Shepard 1967, Standing 1973
PALO ALTO NETWORKSPalo Alto Networks Certified Cloud Security Engineer
The Palo Alto Networks Certified Cloud Security Engineer certification validates the expertise required to secure multicloud estates from code development through production runtime using Cortex Cloud. It is designed for experienced cloud security engineers who plan CNAPP deployments, manage cloud posture and workload protection, and drive automated remediation across the SDLC. Earning it demonstrates job-ready skills for deploying and managing cloud security tooling at scale.
Exam formatCertification
DeliveryPearson VUE
Free questions792
Content last reviewed 30 July 2026 · Up to date
The certification
What Palo Alto Networks Certified Cloud Security Engineer proves, and what it asks of you
What this certification covers, who it is written for, and what the exam itself looks like on the day.
6domains
35objectives
230concepts
What it is
What this certification is
What it validates, who it is written for, and the experience it assumes.
About this certification
The Palo Alto Networks Certified Cloud Security Engineer certification validates the knowledge, skills, and abilities required of experienced cloud security engineers to plan and deploy Cloud-Native Application Protection Platform (CNAPP) solutions, onboard cloud accounts and data sources, and manage security posture across different domains. It confirms the ability to implement cloud workload protection (CWP), Cloud Detection and Response (CDR), and application security workflows, while troubleshooting common platform issues and automating remediation.
This Specialist-level certification focuses on the Cortex Cloud platform and emphasizes end-to-end traceability of issues and the implementation of security guardrails throughout the software development lifecycle (SDLC). It is intended for professionals who are responsible for securing multicloud environments from code to runtime, ensuring compliance, and maintaining a strong security posture across integrated cloud platforms.
Who it’s for
This certification is designed for security engineers, professional services consultants, DevSecOps engineers, technical support engineers, customer success engineers, and security operations engineers. It is also intended for individuals responsible for deploying and managing cloud security tooling and ensuring compliance across integrated cloud platforms. Candidates should have 3+ years in a cloud security-related field and 1–2 years of experience with Palo Alto Networks cloud security solutions or Cortex platform, or with other Cloud-Native Application Protection Platform (CNAPP) solutions.
Recommended experience
3+ years in a cloud security-related field and 1–2 years with Palo Alto Networks cloud security solutions or Cortex platform, or with other CNAPP solutions. Planning and deploying CNAPP solutions; Cloud account and data source onboarding; Security posture management across different domains; Cloud workload protection (CWP) and Cloud Detection and Response (CDR); Application security workflows and automated remediation; Troubleshooting common platform issues
The syllabus
What you’ll learn
Every domain and objective Palo Alto Networks measures, with the weight they carry on the exam.
The official Palo Alto Networks exam outline · checked 30 July 2026 · See the source
Planning and Installation
- 1.1 Evaluate the existing cloud and IT infrastructure to align with Cortex Cloud architecture (i.e., multicloud footprint, workload inventory, Cloud-Native Application Protection Platform [CNAPP] tooling, migration)
- 1.2 Determine Cortex Cloud deployment and license requirements, data source ingestion and retention targets, scanning models (e.g., cloud scan versus Outpost), and cloud provider identity and access management (IAM) requirements (e.g., least-privilege)
- 1.3 Determine network communication and connectivity requirements for Cortex Cloud components (e.g., egress rules, URLs, ports, regional endpoints)
- 1.4 Explain the configuration and management lifecycle of user identity, roles, permissions, and access controls within a Cortex tenant (e.g., Scope-Based Access Control [SBAC], custom Role-Based Access Control [RBAC] roles, API keys)
- 1.5 Identify and describe cost optimization methods (e.g., scan cadence, duplicate audit logs)
Integration
- 2.1 Explain the onboarding and configuration process for cloud provider resources (e.g., AWS, Azure, GCP, OCI)
- 2.2 Explain the process of onboarding and configuring data and AI sources (e.g., Office 365, Databricks, Azure Foundry)
- 2.3 Explain the process of onboarding application development and deployment systems (e.g., GitHub, Jenkins)
- 2.4 Explain the process of container registry integration (e.g., JFrog, Docker, GitLab)
- 2.5 Explain the integration process for third-party static application security testing (SAST) / Software Composition Analysis (SCA) tools (e.g., Semgrep, Veracode, Generic SARIF)
- 2.6 Explain the deployment and configuration process for Broker VM
Posture Security
- 3.1 Explain the process of dashboard creation and configuration using XQL
- 3.2 Explain the creation and configuration process for static and dynamic asset groups
- 3.3 Explain the creation and configuration of cloud security rules and policies (e.g., attack path, configuration, data, identity, network exposure, AI)
- 3.4 Explain the creation and configuration of cloud workload rules and policies (e.g., custom rules, scanner type, misconfiguration, malware, secrets, trusted images)
- 3.5 Explain the creation and management of vulnerability policies (i.e., issue creation and prevention)
- 3.6 Identify and describe methods for managing custom and out-of-the-box compliance standards / controls, assessments, and reporting
- 3.7 Explain the deployment of Kubernetes connectors
- 3.8 Identify and describe data security classification settings and scanning options
Runtime Security
- 4.1 Explain the deployment and configuration of XDR agents (e.g., virtual machines VMs, Containers as a Service [CaaS], serverless functions, Kubernetes)
- 4.2 Explain the process of endpoint protection configuration
- 4.3 Explain the process of third-party API gateway integration (e.g., AWS, API Gateway, APIM, Apigee)
- 4.4 Explain the creation and configuration process for Cloud Detection and Response (CDR) and Threat Management
Application Security
- 5.1 Identify and evaluate Application Security Posture Management (ASPM) features and functionality
- 5.2 Explain rule and policy deployment and management
- 5.3 Explain the configuration and management of repository scanning (e.g., Infrastructure as Code [IaC], secrets, SCA, IaC drift detection)
- 5.4 Explain the deployment and configuration of Cortex Cloud application security IDE plugins (i.e., VS Code, JetBrains)
- 5.5 Identify and describe the steps to install, configure, and execute Cortex CLI in workflows
Troubleshooting
- 6.1 Identify and describe troubleshooting issues related to insufficient cloud service provider (CSP) IAM permissions, CloudFormation / Terraform stack failures, and organization-level onboarding related errors, including ingestion
- 6.2 Demonstrate knowledge of troubleshooting Cortex Cloud Workload components (e.g., agents / connectors, connectivity issues)
- 6.3 Demonstrate knowledge of troubleshooting communication gaps between customer-managed outposts and the Cortex tenant
- 6.4 Demonstrate knowledge of authentication failure resolution (OAuth / PAT) and webhook delivery issues when connecting version control systems (VCS) (e.g., GitHub, GitLab) and CI/CD systems (e.g., Jenkins) to Cortex Cloud
- 6.5 Identify and describe troubleshooting issues related to Application Security components (e.g., proper policy configuration)
- 6.6 Identify and describe access and permissions troubleshooting issues
- 6.7 Explain the process of diagnosing / determining the source of an unexpected Cloud cost increase
On the day
The exam itself
Everything Palo Alto Networks publishes about sitting it, and nothing we inferred.
Prerequisites
No mandatory prerequisites — this certification has no required predecessor exam or credential.
CertificationPalo Alto Networks Certified Cloud Security Engineer
Exam formatCertification
DeliveryPearson VUE
After you pass
Where this credential goes next
The path Palo Alto Networks lays out, how the credential is kept, and where to book.
Step-by-step path to Palo Alto Networks Certified Cloud Security Engineer
Credential earnedPalo Alto Networks Certified Cloud Security Engineer Certification Lifecycle status
This certification is currently active and available. Palo Alto Networks maintains this certification to validate current skills and industry relevance.
Exam status: ActiveMaintained by Palo Alto Networks
Exam registration
Register for the exam through Pearson VUE, Palo Alto Networks’s authorized testing partner.
Schedule your examVisit the official Palo Alto Networks certification page for exam policies and requirements.
View the official pageYour coach
And when you are serious, your coach Pip takes over
Your coach in the app reads what you have answered with the book closed and tells you one thing to do tonight. It will not count an answer you gave with the page open, and it will tell you when you are not ready.
See how the coach worksBefore you book
Questions people ask
Is there a lower-level Palo Alto Networks certification required before taking the Cloud Security Engineer exam?
No. Palo Alto Networks does not require a lower-level certification as a prerequisite for the Cloud Security Engineer exam. However, the recommended experience includes 3+ years in cloud security and 1–2 years with Palo Alto Networks cloud security solutions or other CNAPP platforms.
What job roles does the Cloud Security Engineer certification map to?
The certification is designed for security engineers, professional services consultants, DevSecOps engineers, technical support engineers, customer success engineers, and security operations engineers who are responsible for deploying and managing cloud security tooling and ensuring compliance across integrated cloud platforms.
Is there a hands-on or lab component in the Cloud Security Engineer exam?
The official exam page does not specify whether the exam includes a hands-on or lab component. For detailed exam format information, refer to the Palo Alto Networks Certification Handbook.
How does the Cloud Security Engineer certification relate to the Cloud Security Professional certification?
The Cloud Security Engineer certification is a Specialist-level credential that focuses on the Cortex Cloud platform, while the Cloud Security Professional certification is a Professional-level credential that validates knowledge, skills, and abilities for securing cloud environments with Cortex Cloud. The Engineer certification is more advanced and requires deeper experience.
Can I recertify by passing a different Palo Alto Networks exam?
Palo Alto Networks does not publish a specific recertification path for the Cloud Security Engineer certification. For renewal and recertification policies, refer to the Palo Alto Networks Certification Handbook.
What is the recommended training for the Cloud Security Engineer exam?
Palo Alto Networks recommends reviewing the topics and subtopics in the datasheet and completing the courses found in the digital learning path as needed to prepare for the exam.
Information freshness · Content last reviewed on 2026-07-30 Up to date
Practice free questions 792 questions, free, no account needed.
The curriculum
The whole exam, mapped and written
Every domain, every objective, and every concept Palo Alto Networks measures — each one written out.
6domains
35objectives
230concepts
173free pages
The domains, and what sits inside them
Every objective below is a page you can open and practise now, without an account.
The official Palo Alto Networks exam outline · checked 30 July 2026 · See the source
1Planning and Installation106 questions
1.1 Evaluate the existing cloud and IT infrastructure to align with Cortex Cloud architecture (i.e., multicloud footprint, workload inventory, Cloud-Native Application Protection Platform [CNAPP] tooling, migration)4 concepts · 5 pagesOpen →1.2 Determine Cortex Cloud deployment and license requirements, data source ingestion and retention targets, scanning models (e.g., cloud scan versus Outpost), and cloud provider identity and access management (IAM) requirements (e.g., least-privilege)8 concepts · 5 pagesOpen →1.3 Determine network communication and connectivity requirements for Cortex Cloud components (e.g., egress rules, URLs, ports, regional endpoints)5 concepts · 4 pagesOpen →1.4 Explain the configuration and management lifecycle of user identity, roles, permissions, and access controls within a Cortex tenant (e.g., Scope-Based Access Control [SBAC], custom Role-Based Access Control [RBAC] roles, API keys)8 concepts · 5 pagesOpen →1.5 Identify and describe cost optimization methods (e.g., scan cadence, duplicate audit logs)4 concepts · 4 pagesOpen →
2Integration152 questions
2.1 Explain the onboarding and configuration process for cloud provider resources (e.g., AWS, Azure, GCP, OCI)8 concepts · 6 pagesOpen →2.2 Explain the process of onboarding and configuring data and AI sources (e.g., Office 365, Databricks, Azure Foundry)5 concepts · 5 pagesOpen →2.3 Explain the process of onboarding application development and deployment systems (e.g., GitHub, Jenkins)7 concepts · 6 pagesOpen →2.4 Explain the process of container registry integration (e.g., JFrog, Docker, GitLab)6 concepts · 6 pagesOpen →2.5 Explain the integration process for third-party static application security testing (SAST) / Software Composition Analysis (SCA) tools (e.g., Semgrep, Veracode, Generic SARIF)7 concepts · 5 pagesOpen →2.6 Explain the deployment and configuration process for Broker VM7 concepts · 5 pagesOpen →
3Posture Security164 questions
3.1 Explain the process of dashboard creation and configuration using XQL8 concepts · 6 pagesOpen →3.2 Explain the creation and configuration process for static and dynamic asset groups7 concepts · 4 pagesOpen →3.3 Explain the creation and configuration of cloud security rules and policies (e.g., attack path, configuration, data, identity, network exposure, AI)7 concepts · 4 pagesOpen →3.4 Explain the creation and configuration of cloud workload rules and policies (e.g., custom rules, scanner type, misconfiguration, malware, secrets, trusted images)8 concepts · 4 pagesOpen →3.5 Explain the creation and management of vulnerability policies (i.e., issue creation and prevention)7 concepts · 5 pagesOpen →3.6 Identify and describe methods for managing custom and out-of-the-box compliance standards / controls, assessments, and reporting7 concepts · 6 pagesOpen →3.7 Explain the deployment of Kubernetes connectors5 concepts · 5 pagesOpen →3.8 Identify and describe data security classification settings and scanning options2 concepts · 2 pagesOpen →
4Runtime Security103 questions
4.1 Explain the deployment and configuration of XDR agents (e.g., virtual machines VMs, Containers as a Service [CaaS], serverless functions, Kubernetes)6 concepts · 5 pagesOpen →4.2 Explain the process of endpoint protection configuration7 concepts · 5 pagesOpen →4.3 Explain the process of third-party API gateway integration (e.g., AWS, API Gateway, APIM, Apigee)7 concepts · 6 pagesOpen →4.4 Explain the creation and configuration process for Cloud Detection and Response (CDR) and Threat Management9 concepts · 7 pagesOpen →
5Application Security110 questions
5.1 Identify and evaluate Application Security Posture Management (ASPM) features and functionality7 concepts · 5 pagesOpen →5.2 Explain rule and policy deployment and management6 concepts · 6 pagesOpen →5.3 Explain the configuration and management of repository scanning (e.g., Infrastructure as Code [IaC], secrets, SCA, IaC drift detection)6 concepts · 5 pagesOpen →5.4 Explain the deployment and configuration of Cortex Cloud application security IDE plugins (i.e., VS Code, JetBrains)8 concepts · 6 pagesOpen →5.5 Identify and describe the steps to install, configure, and execute Cortex CLI in workflows4 concepts · 2 pagesOpen →
6Troubleshooting157 questions
6.1 Identify and describe troubleshooting issues related to insufficient cloud service provider (CSP) IAM permissions, CloudFormation / Terraform stack failures, and organization-level onboarding related errors, including ingestion5 concepts · 5 pagesOpen →6.2 Demonstrate knowledge of troubleshooting Cortex Cloud Workload components (e.g., agents / connectors, connectivity issues)8 concepts · 4 pagesOpen →6.3 Demonstrate knowledge of troubleshooting communication gaps between customer-managed outposts and the Cortex tenant4 concepts · 3 pagesOpen →6.4 Demonstrate knowledge of authentication failure resolution (OAuth / PAT) and webhook delivery issues when connecting version control systems (VCS) (e.g., GitHub, GitLab) and CI/CD systems (e.g., Jenkins) to Cortex Cloud5 concepts · 4 pagesOpen →6.5 Identify and describe troubleshooting issues related to Application Security components (e.g., proper policy configuration)6 concepts · 4 pagesOpen →6.6 Identify and describe access and permissions troubleshooting issues13 concepts · 8 pagesOpen →6.7 Explain the process of diagnosing / determining the source of an unexpected Cloud cost increase9 concepts · 6 pagesOpen →
Not a table of contents
Every line on this map already opens
In front of every objective the practice pages are already there, free and without an account. This is one objective, opened.
1.1 Evaluate the existing cloud and IT infrastructure to align with Cortex Cloud architecture (i.e., multicloud footprint, workload inventory, Cloud-Native Application Protection Platform [CNAPP] tooling, migration)5 pagesOpen →
Free in front of it
24 questions on this objective, five to a page. Every range above is a real page, open now, with no account.
Reading the map is not the same as knowing the ground
The curriculum tells you what is on the exam. Proving you know it is a different job — and it is the one the closed-book run does.
Free questions
792 questions. No account, no card.
The whole bank is open. 5 questions to a page, every answer explained, and a discussion thread on each one.
792questions
173pages
35objectives
Freealways
Browse by domain
Every objective, and every page range, is a link — so you can pick up exactly where you left off.
1Planning and Installation106 questions
2Integration152 questions
3Posture Security164 questions
4Runtime Security103 questions
5Application Security110 questions
6Troubleshooting157 questions
What a practice page gives you
1Five to a page
Short enough to finish, long enough to matter.
2Every answer explained
Not only which one is right — why the others are wrong.
3A discussion on each
Ask, answer, and vote. Every question has its own thread.
A question, and the idea behind it
Every question comes from a concept
These are not trivia. Each one is written against a concept in the book, so when you get one wrong there is somewhere to go and find out why.
The visual book
See it once. Carry it into the exam.
The pages shown here come from our AI-900 book — an example of how each concept is written in plain language and, where the idea needs one, drawn as a full page you can take in at a glance.
230concepts
792free questions
Why a picture, and not another paragraph
Three reasons, and each one is a real finding rather than a slogan.
You can see it againThe whole idea at onceWhere it starts, what happens in the middle, what comes out, and the mistake to avoid.
Multimedia principle · MayerThe look-alikes sit togetherThe pairs the exam tests are drawn side by side, so the difference is seen, not told.
Dual coding · PaivioWhat one page is made of
You are never asked to read a poster here — only to see how one is built. After that, every other page is legible at a glance.
1A numbered strip on top
The idea as a sequence, followed with a finger before a word is read.
2Panels for the parts
What it is, how the machine learns it, when it is the right tool.
3The trap, framed
The distinction the exam tests, given its own box instead of buried in prose.
4One line at the bottom
The sentence to carry into the exam room.
Open book, on purpose
Answer it with the picture beside you
This is the part that teaches. The illustration and the written explanation stay where they are while you work, so a scenario stops being a memory test and becomes something you can simply look at.
It teaches · it does not count
A smartphone uses AI to unlock when the owner looks at the camera. Which AI capability is being used?
AImage classification
BFacial recognition
COptical character recognition
DObject detection
Look at the five steps. Detect finds a face, align straightens it, encode turns it into numbers, search compares it with a stored face, and decide answers one question: is this the same person? Classification would only say “a face”. Detection would only draw a box. Neither decides whose.
Then the page shuts, and it starts counting
The same questions come back with the book closed — that run is the one that counts. After it, your coach picks one thing for tonight, sized to the time you have, and brings pages back before you lose them.
Testing effect · Roediger & Karpicke 2006 · spacing effect · Cepeda et al. 2006
Official resources
Straight from Palo Alto Networks
Where the exam is defined, scheduled and scored.
5official links
230concepts mapped
The source
Palo Alto Networks’s own pages
We link to them rather than repeat them, so nothing here goes stale behind them.
Checked against the source
Every objective on the official Palo Alto Networks outline already has questions here
We build from the official skills outline, not from a summary of it — 35 objectives, 230 concepts written under them, and free questions against every one. When Palo Alto Networks changes the outline, this page changes with it.
35objectives on the outline→230concepts written→792free questions
An official page tells you what will be asked. It cannot tell you what you will get right.
That is the only question worth answering the night before, and no link answers it. You answer it by taking the questions with the book closed, and seeing what comes back.