The Atlas take.
This profile should begin with transition planning. Check Point’s published partnership material describes moving CloudGuard CNAPP customers to Wiz rather than building a single combined CNAPP product. Its cloud network-security offerings remain a different control boundary. Atlas would judge the arrangement by preservation of policies, cloud access, findings, ownership, and contractual support through the actual migration. A partnership announcement is useful lineage evidence, but it does not prove that every promised integration has shipped. Existing customers should obtain a configuration-specific migration and acceptance plan before treating an old CloudGuard screen and a current Wiz demonstration as equivalent deployments.
02 / DEFINE THE BOUNDARY
What you are actually evaluating.
Scope the existing Check Point CNAPP deployment separately from Cloud Firewall and web-application firewall products. Use the partnership FAQ for migration planning; older CNAPP marketing pages should not be treated as proof that every module remains unchanged.
03 / THE CONTROL PATH
Where it sits. How it works.
An existing CNAPP estate transitions toward a separately scoped Wiz deployment, while Check Point cloud-network controls retain their own integration and enforcement paths.
- 01
Existing CNAPP configuration
Inventory CloudGuard findings, policies, cloud roles, exceptions, and service commitments before transition.
- 02
Wiz target and integration
Validate the actual Wiz subscription and delivered integration rather than assuming roadmap statements describe the installed system.
- 03
Retained network and owner workflow
Keep Cloud Firewall or other network controls separately scoped and prove the security-team handoff in the target design.
04 / WHAT EARNS ITS PLACE
Strengths, with the evidence attached.
Atlas analysis of documented capabilities; availability and behavior depend on the edition and environment.
The relationship is documented
The partner Q&A explicitly distinguishes customer migration from construction of a combined CNAPP offering, improving the clarity of an existing-estate discussion.
Complementary control boundaries
Current integration material positions Wiz alongside Check Point capabilities, giving evaluators a concrete reason to separate risk visibility from network enforcement.
Inspect the documented capability notes
- The partnership materials describe Wiz as the forward CNAPP platform for the affected Check Point offering.
- Documented integration connects cloud exposure context with Check Point cloud network-security workflows.
- Cloud Firewall and web-application firewall remain distinct network and application controls outside the stated CNAPP transition.
05 / KNOW THE COMPROMISES
The tradeoffs to take seriously.
Architectural implications and procurement questions from Atlas; these are not independently measured product failures.
Transition terms are material
The published Q&A states CloudGuard CNAPP is end-of-sale for new purchases; existing customers must confirm applicable renewal, support, and migration terms.
06 / FROM PURCHASE TO PRACTICE
Make it work in your environment.
A proposed implementation sequence. Confirm supported versions, permissions, and rollback with the current documentation.
- 01
Inventory what must survive
List findings, policy intent, exceptions, role grants, exports, downstream integrations, and evidence-retention requirements.
- 02
Agree the target boundary
Obtain the current order form, cloud support matrix, migration responsibility, and the list of delivered integrations.
- 03
Accept the migrated workflow
Repeat a representative finding-to-owner and approved remediation path, then compare retained evidence before retiring the original dependency.
07 / THE OPERATING COMMITMENT
The bill is only part of the cost.
Commercial shape
Obtain written terms for the existing CNAPP support period, target Wiz subscription, migration assistance, and separately retained Check Point products. A partnership does not establish one universal license.
- Existing support and transition commitments
- Wiz CNAPP subscription and any separately contracted network controls
- Migration services, temporary overlap, and evidence-retention work
08 / COMPARE THE JOB
Put these beside it.
Alternatives worth examining for the same problem. Check each offering’s scope before treating it as a substitute.
Wiz
Examine the target CNAPP directly to understand its current platform scope and the subscription required by the migration.
Palo Alto NetworksPalo Alto Networks Cortex Cloud
Compare a different converged cloud-security architecture if the transition is also an opportunity to reconsider the operating model.
09 / MAKE THE DECISION OBSERVABLE
Earn confidence through a real evaluation.
Suggested by Atlas. Agree acceptance criteria, use synthetic fixtures in an authorized environment, and capture both useful work and failed controls.
- TEST 01
Account for historical evidence
Acceptance evidence: Export representative open findings, exceptions, and ownership records and show where each remains available after transition.
- TEST 02
Validate the target control
Acceptance evidence: Reproduce a benign cloud exposure in the target environment and confirm scope, owner assignment, and reassessment after remediation.
- TEST 03
Separate network enforcement
Acceptance evidence: Test one approved network policy independently of CNAPP risk visibility; preserve which product actually made the enforcement decision.
START WITH ONE EXERCISE
Export a representative synthetic CNAPP finding and map its owner, policy and downstream ticket workflow to the proposed Wiz deployment.
Evidence to look for: The replacement demonstration preserves the required investigation context and ticket ownership, while the inventory explicitly separates unaffected firewall functions.
Questions to bring to the vendor
- Which existing CNAPP functions have a demonstrated replacement rather than only a similarly named feature?
- Who owns the post-transition contract, support and data-processing responsibilities?
- Which firewall or web-application-firewall policies remain separately managed and outside the CNAPP migration?
10 / SHOW THE WORK
Evidence, and what is still unknown.
What this research cannot establish
- Historical partnership material is not proof that every planned integration is currently delivered; obtain current release and migration documentation.
- No independent migration, coverage-equivalence, or network-enforcement test was conducted for this profile.
Dossier research reviewed October 18, 2026. Earlier profile references are retained for traceability; products and commercial terms change.
- Check Point CloudGuard and Wiz CNAPP: official product documentation ↗Earlier profile reference
- Check Point CloudGuard and Wiz CNAPP: official supporting source ↗Earlier profile reference
- Check Point and Wiz partnership migration Q&A ↗Lifecycle
- Current Check Point and Wiz integration scope ↗Product information
- Check Point and Wiz strategic partnership announcement ↗Product information
KEEP BUILDING YOUR JUDGMENT