Prisma Cloud / Cortex Cloud transition scope
Confirm the exact Prisma Cloud or Cortex Cloud offering, edition, migration terms, and licensed components. Cortex Exposure Management and Cortex XDR are not interchangeable names for this cloud scope. A broad cloud platform page does not establish every function in a base subscription.
Strengths and evaluation fit
The Prisma Cloud page now also presents Cortex Cloud. It describes cloud posture, workload and application protection, and risk prioritization across development, infrastructure, and runtime contexts.
Consider it when the requirement centers on cloud applications and workloads. Use a representative cloud account and follow one issue through its code, configuration, identity, and runtime context where those components are licensed.
Trade-offs and boundaries to verify
Confirm the exact Prisma Cloud or Cortex Cloud offering, edition, migration terms, and licensed components. Cortex Exposure Management and Cortex XDR are not interchangeable names for this cloud scope. A broad cloud platform page does not establish every function in a base subscription.
Primary Prisma Cloud page checked October 30, 2026; current quote and transition scope require confirmation.
Product evidence at a glance
Verified consolidates established base inclusion and documented product capability. Package evidence is reported separately. Module / integration / activation, Outside assessed base, and Not established preserve the boundaries. Missing evidence is not a finding that a product lacks the capability.
| Research area | Evidence | Source |
|---|---|---|
| Asset visibility | Verified | Official source ↗ |
| Existing-tool data | Not established | Official source ↗ |
| Risk prioritization | Verified | Official source ↗ |
| Attack paths | Not established | Official source ↗ |
| Attack validation | Not established | Official source ↗ |
| Control gaps | Not established | Official source ↗ |
| Remediation workflow | Not established | Official source ↗ |
| Person-level identity risk | Not established | Official source ↗ |
What to ask in a demonstration
- What evidence explains why this exposure needs attention now?
- Which component executes the change and verifies the result?
- Which functions require another module, integration, or license?
Package and implementation boundaries
Confirm the exact offering, modules, dependencies, and entitlement in the quote.
Research date and scope
The underlying source record was checked October 30, 2026; Primary product page. This summary was published October 30, 2026. Source-check dates above identify retained research and any new checks separately. The publication date is not a new verification of every vendor claim. This is documentation-based buying research, not a hands-on review.
Read our research approach · Understand product and package evidence