SaaS Policy Rule Recommendations
Table of Contents
Expand all | Collapse all
-
-
- What’s Data Security?
- Navigate To Data Security in Cloud Management Console
- Activate Data Security on the Hub
- Access Data Security for Standalone SaaS Security
-
- Allowed List of IP Addresses
-
- Begin Scanning an Amazon Web Services App
- Begin Scanning a Bitbucket Cloud App
- Begin Scanning a Box App
- Begin Scanning a Cisco Webex Teams App
- Begin Scanning a Citrix ShareFile App
- Begin Scanning a Confluence App
- Begin Scanning a Confluence Data Center App
- Begin Scanning a Dropbox App
- Begin Scanning a GitHub App
- Begin Scanning a GitHub V2 App
- Begin Scanning a Gmail App
- Begin Scanning a Google Cloud Storage App
- Begin Scanning a Google Drive App
- Begin Scanning a Jira Cloud App
- Begin Scanning a Jira Data Center App
- Begin Scanning a Microsoft Azure Storage App
- Begin Scanning a Microsoft Exchange App
- Begin Scanning Microsoft Office 365 Apps
- Begin Scanning a Microsoft Teams App
- Begin Scanning a Salesforce App
- Begin Scanning a ServiceNow App
- Begin Scanning a Slack for Enterprise Grid App
- Begin Scanning a Slack Enterprise App
- Begin Scanning a Slack for Pro and Business App
- Begin Scanning a Workday App (Beta)
- Begin Scanning a Yammer App
- Begin Scanning a Zendesk App
- Begin Scanning a Zoom App
- Reauthenticate to a Cloud App
- Verify Permissions on Cloud Apps
- Start Scanning a Cloud App
- Rescan a Managed Cloud App
- Delete Cloud Apps Managed by Data Security
- API Throttling
- Configure Classification Labels
- Microsoft Labeling for Office 365
-
-
-
- SaaS Security with Enterprise DLP
- Predefined Data Patterns on Data Security
- Proximity Keywords
- Confidence Levels
- Shared Data Profiles and Data Patterns
- Modify a Predefined Data Pattern
- Create a Custom Data Profile
- Add a File Property Data Pattern
- Create a Custom Data Pattern
- Use Exact Data Matching (EDM)
- Enable or Disable a Machine Learning Data Pattern
- Configure WildFire Analysis
- Configure Regular Expressions
- Enable or Disable a Data Pattern
- View and Filter Data Pattern Match Results
-
-
-
- What is an Incident?
- Assess New Incidents on Data Security
- View Asset Details
- Filter Incidents
- Security Controls Incident Details
- Track Down Threats with WildFire Report
- Track Down Threats with AutoFocus
- Customize the Incident Categories
- Close Incidents
- Download Assets for Incidents
- View Asset Snippets for Incidents
- Analyze Inherited Exposure
- Email Asset Owners
- Modify Incident Status
-
- What is a Data Violation?
- Assess New Data Violations on Data Security
- Configure Data Violation Alerts on Data Security
- Filter Data Violations on Data Security
- View Asset Snippets for Data Violations on Data Security
- View Data Violation Metrics on Data Security
- Modify Data Violation Status on Data Security
-
-
-
-
- What’s SaaS Security Inline?
- Navigate To SaaS Security Inline
- SaaS Visibility for NGFW
- SaaS Visibility and Controls for NGFW
- SaaS Visibility for Prisma Access
- SaaS Visibility and Controls for Panorama Managed Prisma Access
- SaaS Visibility and Controls for Cloud Managed Prisma Access
- Activate SaaS Security Inline for NGFW
- Activate SaaS Security Inline for VM-Series Firewalls with Software NGFW Credits
- Activate SaaS Security Inline for Prisma Access
- Connect SaaS Security Inline and Strata Logging Service
- Integrate with Azure Active Directory
-
-
- SaaS Policy Rule Recommendations
- App-ID Cloud Engine
- Guidelines for SaaS Policy Rule Recommendations
- Predefined SaaS Policy Rule Recommendations
- Apply Predefined SaaS Policy Rule Recommendations
- Create SaaS Policy Rule Recommendations
- Delete SaaS Policy Rule Recommendations
- Enable SaaS Policy Rule Recommendations
- Modify Active SaaS Policy Rule Recommendations
- Monitor SaaS Policy Rule Recommendations
-
- Enable Automatic Updates for SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Import New SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Update Imported SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Remove Deleted SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Manage Enforcement of Rule Recommendations on NGFW
- Manage Enforcement of Rule Recommendations on Panorama Managed Prisma Access
- Change Risk Score for Discovered SaaS Apps
-
-
-
-
- Onboarding Overview for Supported SaaS Apps
- Onboard an Aha.io App to SSPM
- Onboard an Alteryx Designer Cloud App to SSPM
- Onboard an Aptible App to SSPM
- Onboard an ArcGIS App to SSPM
- Onboard an Articulate Global App to SSPM
- Onboard an Atlassian App to SSPM
- Onboard a BambooHR App to SSPM
- Onboard a Basecamp App to SSPM
- Onboard a Bitbucket App to SSPM
- Onboard a BlueJeans App to SSPM
- Onboard a Box App to SSPM
- Onboard a Bright Security App to SSPM
- Onboard a Celonis App to SSPM
- Onboard a Cisco Meraki App to SSPM
- Onboard a ClickUp App to SSPM
- Onboard a Confluence App to SSPM
- Onboard a Contentful App to SSPM
- Onboard a Convo App to SSPM
- Onboard a Couchbase App to SSPM
- Onboard a Coveo App to SSPM
- Onboard a Crowdin Enterprise App to SSPM
- Onboard a Customer.io App to SSPM
- Onboard a Databricks App to SSPM
- Onboard a Datadog App to SSPM
- Onboard a DocHub App to SSPM
- Onboard a DocuSign App to SSPM
- Onboard a Dropbox Business App to SSPM
- Onboard an Envoy App to SSPM
- Onboard an Expiration Reminder App to SSPM
- Onboard a Gainsight PX App to SSPM
- Onboard a GitHub Enterprise App to SSPM
- Onboard a GitLab App to SSPM
- Onboard a Google Analytics App to SSPM
- Onboard a Google Workspace App to SSPM
- Onboard a GoTo Meeting App to SSPM
- Onboard a Grammarly App to SSPM
- Onboard a Harness App to SSPM
- Onboard a Hellonext App to SSPM
- Onboard an IDrive App to SSPM
- Onboard an Intercom App to SSPM
- Onboard a Jira App to SSPM
- Onboard a Kanbanize App to SSPM
- Onboard a Kanban Tool App to SSPM
- Onboard a Kustomer App to SSPM
- Onboard a Lokalise App to SSPM
- Onboard a Microsoft Azure AD App to SSPM
- Onboard a Microsoft Exchange App to SSPM
- Onboard a Microsoft OneDrive App to SSPM
- Onboard a Microsoft Outlook App to SSPM
- Onboard a Microsoft Power BI App to SSPM
- Onboard a Microsoft SharePoint App to SSPM
- Onboard a Microsoft Teams App to SSPM
- Onboard a Miro App to SSPM
- Onboard a monday.com App to SSPM
- Onboard a MongoDB Atlas App to SSPM
- Onboard a MuleSoft App to SSPM
- Onboard a Mural App to SSPM
- Onboard an Office 365 App to SSPM
- Onboard Office 365 Productivity Apps to SSPM
- Onboard an Okta App to SSPM
- Onboard a PagerDuty App to SSPM
- Onboard a RingCentral App to SSPM
- Onboard a Salesforce App to SSPM
- Onboard an SAP Ariba App to SSPM
- Onboard a ServiceNow App to SSPM
- Onboard a Slack Enterprise App to SSPM
- Onboard a Snowflake App to SSPM
- Onboard a SparkPost App to SSPM
- Onboard a Tableau Cloud App to SSPM
- Onboard a Webex App to SSPM
- Onboard a Workday App to SSPM
- Onboard a Wrike App to SSPM
- Onboard a YouTrack App to SSPM
- Onboard a Zendesk App to SSPM
- Onboard a Zoom App to SSPM
- Onboarding an App Using Azure AD Credentials
- Onboarding an App Using Okta Credentials
- Delete SaaS Apps Managed by SSPM
SaaS Policy Rule Recommendations
Learn about SaaS policy rule recommendations on SaaS
Security Inline.
The rapid proliferation of SaaS applications makes it difficult to assign all of them specific
App-IDs, gain visibility into those applications, and control them. Security policy
rules that allow SSL, web-browsing, or “any” application might allow unsanctioned SaaS
applications that can introduce security risks to your network. To gain visibility into
those applications and control them, SaaS Security administrators can recommend policy
rules for specific SaaS apps to administrators who have the authority to import and
commit (push) them to Security policy.
To import SaaS policy rule recommendations on the firewall, a SaaS Security Inline license is
required.
Security policy rules detect and take action on specific application traffic on your
network. SaaS policy rule recommendations are based on a combination of applications,
users and groups, categories, activities, device posture, and data profiles. For
example, you might create a SaaS policy rule
recommendation that blocks all HR and Finance employees from uploading assets to risky
file sharing applications such as 4Shared and WeTransfer.
After you create a policy recommendation and set the rule action, you then submit the rule
for review. The administrator with the authority to commit the rule evaluates the
recommended rule and decides whether to implement it. If that administrator chooses to
implement the rule, the administrator imports it and selects where to place the policy
rule in the rulebase, creating all the required HIP profiles, tags, and Application
Groups automatically.
The administrator with the authority to commit the rules is the same administrator that
maintains the rulebase. If you update a policy rule recommendation, that recommendation
needs to be reimported. If you delete a SaaS policy rule recommendation, the
recommendation needs to be deleted from the Security policy rulebase.
You can define policy recommendations at the application level or, for some
select applications, at the application tenant level.
- Application-level policy recommendations, if committed on the firewall, will affect all instances of the application. Application-level policy recommendations support only theBlockaction. TheBlockaction prevents network traffic for specified user activity in the application, such as upload or download activity.
- Tenant-level policy recommendations, if committed on the firewall, will affect only the application tenants that you identify. For example, you might create a SaaS policy rule recommendation toBlockdownloads from Box for one tenant only. You can select up to 30 individual tenants per policy recommendation.Tenant-level detection is supported for some applications, which all allow you to define policy recommendations toBlockuser activities on selected tenants. A subset of these applications support bothBlockandAllowactions. TheAllowaction explicitly permits network traffic for specified user activity on the tenants. Because permitting network traffic for the tenants is already the default behavior, defining a policy recommendation to explicitlyAllowuser activities on tenants is unnecessary on its own. We designed the explicitAllowaction for you to use in a policy recommendation only when you also define another policy recommendation toBlockactivities for the remaining tenants. PairingAllowandBlockpolicy recommendations in this way is a convenient way to block activities on most tenants while allowing the activities on a smaller set of tenants.When theAllowaction is supported for an application, you can also identify the affected tenants of a policy recommendation asAny. TheAnyspecification acts as a wildcard to match all current and future tenants. On the firewall, when an imported policy specifiesAnytenant, the policy will apply to all tenants unless an earlier policy in the firewall's evaluation order specifies a different action for a tenant. In this way, you can define one policy recommendation toAllowthe actions for selected tenants and another toBlockthe actions forAnyother tenants.When you create separate tenant-levelAllowandBlockpolicy recommendations to achieve particular results, your desired results will depend on the order in which the policies are evaluated on the firewall. On the firewall, when traffic matches a policy rule, the defined action is triggered and all subsequent policies are disregarded. So, if a policy toBlockuser actions forAnytenants is placed before a policy toAllowuser actions for particular tenants, theAllowpolicy will be disregarded. When the firewall administrator imports your policy recommendations, make sure that they place the more specific policy before the more generic one. In this case, the more specific policy toAllowuser actions for particular tenants must be placed before the generic policy toBlockuser actions forAnytenant.
To understand when to define application-level and tenant-level policy recommendations,
review the following table of common scenarios.
Desired Firewall Behavior | Policy Recommendations | Example |
---|---|---|
Block one or more types of user activities for an application for all
tenants. | Create an application-level policy recommendation to
Block the actions. Because this policy
recommendation is at the application level, all application tenants
will be affected. | You want to prevent access to Box on all tenants. To do this, you create an application-level policy recommendation to
Block all user activity for Box. |
Block one or more types of user activities for some of an
application's tenants, but allow the activities for all other
tenants. | Create a tenant-level policy recommendation to
Block the activities for the tenants. By
default, the activities are still allowed for all other tenants. | You want to prevent access to Box for personal tenants, but allow
access for corporate tenants. To do this, you create a tenant-level policy recommendation to
Block any user activity for the personal
tenants. By default, the user activities are still allowed for the
corporate tenants. |
Block one or more types of user activities for most of an
application's tenants, but allow the activities for some tenants.
|
| You want to prevent access to Box for most of your organization, but
allow access to box on a single tenant. To do this, you create two
tenant-level policy recommendations.
After you enable the policy recommendations, you make sure that
the firewall administrator understands that the first policy must be
evaluated on the firewall before the second policy. |