topic Why we need web-security policy while even we having same feature in normal prisma access policy? in Next-Generation CASB Discussions

Why we need web-security policy while even we having same feature in normal prisma access policy?

AkilanR — Tue, 02 Jan 2024 07:26:29 GMT

Hi Team,

Kindly clarify me why we need web-security policy while even we having same feature in normal prisma access policy?

Scenario,

SaaS security discovered several apps, we can create a policy and later import to websecurity by policy recommendation.

But the question here is even the same application can be used in normal security policy in prisma access

Note:

Referred multiple paloalto document but only configuration is mentioned couldn't get,

1.why it is required?

2.Whether it is mandatory requirement for SaaS security ?

Re: Why we need web-security policy while even we having same feature in normal prisma access policy?

reaper — Tue, 02 Jan 2024 23:52:35 GMT

you simply have the option of choosing the policy recommendation, or building your own policy

Re: Why we need web-security policy while even we having same feature in normal prisma access policy?

laurence64 — Thu, 05 Sep 2024 08:37:22 GMT

I think that web-security once enabled is evaluated first (not 100 percent on that) but is also a role that can be give to web security admins so they can alter the web security policy but not other policies.

Re: Why we need web-security policy while even we having same feature in normal prisma access policy?

nikoolayy1 — Fri, 17 Jan 2025 08:39:56 GMT

SaaS security gives you access to App-ID Cloud Engine (ACE) that has more SaaS app-id than the normal NGFW without SaaS security enabled.

App-ID Cloud Engine