PSE Prisma Cloud Professional study materials
PSE Prisma Cloud Professional study resources

PSE Prisma Cloud Professional study plan

PSE Prisma Cloud Professional · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Cortex Cloud platform & Cloud Posture Security

  • Map the Cortex Cloud console navigation to the five exam domains and label which domain each main menu area serves

  • Define CSPM, CIEM, CWPP, and DSPM and state in one sentence each what posture question they answer

  • Explain how Prisma Cloud's agentless and agent-based scanning models differ in what they collect and when

  • Configure a read-only cloud account onboarding in a sandbox tenant and record the roles and permissions it requests

  • Identify the resource inventory views that report misconfigurations versus those that report vulnerabilities

Your checkpoint

A one-page domain map listing every console area, the domain it belongs to, and the top three tasks you would perform there

Week 2

Cloud Posture Security & Cortex Cloud platform

  • Write 15 custom policies (five each for config, network, and identity) using RQL and validate each against the policy tester

  • Trace how a policy becomes an alert: policy, compliance standard, alert rule, and notification channel

  • Build a compliance report against a named benchmark and explain which controls failed and why

  • Configure alert suppression and explain the tradeoff between noise reduction and missed detections

  • Differentiate build-time, deploy-time, and runtime posture checks and give a concrete example of each

Your checkpoint

A working policy pack of 15 RQL policies with expected pass/fail results documented for at least two resources each

Week 3

Cloud Posture Security & Cloud Runtime Security

  • Design an attack path query that chains a public exposure, an over-permissive identity, and a sensitive data store

  • Explain how effective permissions are calculated across nested groups, roles, and resource policies

  • Prioritize a list of 30 findings using severity, exposure, exploitability, and data sensitivity, then justify the ordering

  • Describe how runtime signals (process, network, file) change the priority of a static misconfiguration

  • Set up a CI/CD gate that fails a build on high-severity posture findings and verify it blocks a test pipeline

Your checkpoint

A written triage of 30 findings with assigned priority tiers and the reasoning for each tier

Week 4

Cloud Runtime Security & Cortex Cloud platform

  • Deploy the defensive agent to one Linux and one Windows host in a lab and confirm it reports to the console

  • Write runtime policies for process execution, outbound connections, and file integrity and trigger each deliberately

  • Explain the difference between runtime protection in alert mode and block mode and when each is appropriate

  • Describe how serverless and container runtime coverage differs from host coverage and what telemetry each provides

  • Correlate a runtime alert with the posture finding that made the workload exploitable

Your checkpoint

A lab report showing three triggered runtime alerts, their raw telemetry, and the correlated posture context for each

Week 5

Cloud Runtime Security & Application Security

  • Scan a container image in the registry and in the pipeline and compare the results and timing

  • Interpret a vulnerability report: fixable versus unfixable, base image inheritance, and package path

  • Configure admission control to block a noncompliant image and confirm the block with a test deployment

  • Explain how software composition analysis and infrastructure-as-code scanning fit into the developer workflow

  • Map a container escape scenario from image vulnerability through runtime detection and note where each control fires

Your checkpoint

An end-to-end pipeline demo (IaC scan, image scan, admission control) with screenshots of each gate and the failure messages developers would see

Week 6

Application Security & SOC processes

  • Triage a seeded application-security backlog and separate true positives from false positives with evidence

  • Write remediation guidance for three vulnerability classes that a developer could act on without security context

  • Explain how code-to-cloud context links a repository finding to a deployed workload and why that changes priority

  • Define SLAs by severity and exposure and apply them to the backlog

  • Describe how secrets detection differs from dependency scanning in detection method and remediation urgency

Your checkpoint

A prioritized application-security backlog with SLA assignments and developer-ready remediation notes for the top five items

Week 7

SOC processes & Cloud Posture Security

  • Draft an incident response runbook for a compromised cloud workload covering containment, evidence, and eradication

  • Explain how alerts flow into a SIEM or ticketing system and what fields must be preserved for investigation

  • Build a dashboard that tracks open critical findings, mean time to remediate, and coverage gaps by account

  • Distinguish posture findings, runtime detections, and application vulnerabilities in SOC triage and escalation paths

  • Write a post-incident review template with root cause, detection gap, and control improvement sections

Your checkpoint

A complete incident runbook plus a working dashboard with at least four panels and the queries behind them

Week 8

Cortex Cloud platform & Cloud Runtime Security & Application Security & Cloud Posture Security & SOC processes

  • Re-take a timed 60-question practice set across all domains and score each domain separately

  • Review every missed question and write the underlying concept in your own words

  • Recite from memory the onboarding, policy, runtime, and incident workflow sequences

  • List the five facts you are least confident about and verify each against product documentation

  • Simulate explaining the platform to a new SOC analyst in ten minutes without notes

Your checkpoint

A scored practice exam with a per-domain breakdown and a one-page personal weak-area sheet with verified corrections

Milestones

Week 2: Can build and validate an RQL policy from scratch and explain the full policy-to-alert path without notes

Week 4: Posture and runtime labs complete; you can correlate a runtime detection to its enabling misconfiguration

Week 6: Full pipeline gates working and an application-security backlog triaged with defensible priorities

Week 8: Practice exam score at or above 80 percent overall with no single domain below 70 percent