SaaS Security Inline protects against cloud‑based threats by blocking traffic for
unsanctioned SaaS apps and risky user activity using Security policy. Use the
following workflow if you want to use all the features of
SaaS Security Inline, including
App-ID Cloud Engine (ACE), SaaS policy
rule
recommendations, and SaaS visibility.
Step
1: Activation
ACE is enabled by default on Prisma Access (Managed by Panorama).
Perform the prerequisites outlined in
Prisma Access Administrator’s
Guide, including log forwarding. Without data logs,
SaaS Security Inline cannot display SaaS app visibility data and might
not be able to enforce policy rule recommendations.
Activate the
SaaS Security Inline license. (SaaS administrator)
Step 2: System Configuration
Integrate with Azure
Active Directory so that
SaaS Security Inline can identify your AD
groups. (SaaS administrator)
Add administrators to manage
SaaS Security. (SaaS administrator)
Step 3: Security Policy Configuration
Review the guidelines for
effective collaboration and rulebase management. (SaaS administrator and
Prisma Access administrator)
Author and submit SaaS policy rule
recommendations to your
Prisma Access administrator. (SaaS administrator)
Import new SaaS policy rule
recommendations. (
Prisma Access administrator)
Step 4: Security Policy Maintenance
Continuously monitor the SaaS policy rule recommendations to ensure they’re in sync. (SaaS
administrator)
Continuously monitor the SaaS policy rule recommendations for changes. (Prisma Access
administrator)
- For updates, reimport changes to
active SaaS policy rule recommendations.
- For deletions, remove
recommendation mapping, then delete the policy rule.
