Activate SaaS Security Inline for NGFW
Table of Contents
Expand all | Collapse all
-
-
- Allowed List of IP Addresses
-
- Begin Scanning a Bitbucket App
- Begin Scanning a Box App
- Begin Scanning ChatGPT Enterprise App
- Begin Scanning a Cisco Webex Teams 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 Gmail App
- Begin Scanning a Google Drive App
- Begin Scanning a Jira App
- Begin Scanning a Jira Data Center App
- Begin Scanning a Microsoft Exchange App
- Begin Scanning Office 365 Apps
- Begin Scanning a Microsoft Teams App
- Begin Scanning a Salesforce App
- Begin Scanning a ServiceNow App
- Begin Scanning a ShareFile 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 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
- Google Drive Labeling
- Configure Phishing Analysis
- Configure WildFire Analysis
-
-
-
- What is an Incident?
- Assess New Incidents on Data Security
- Filter Incidents
- Configure Slack Notification Alerts on Data Security
- Security Controls Incident Details
- Track Down Threats with WildFire Report
- 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’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 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 Outlook App to SSPM
- Onboard a Microsoft Power BI 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 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
- Register an Azure AD Client Application
- View the Health Status of Application Scans
- Delete SaaS Apps Managed by SSPM
Activate SaaS Security Inline for NGFW
Learn how to activate SaaS Security Inline on your Palo
Alto Networks firewalls.
To
unlock the SaaS Security Inline capabilities—SaaS
visibility, SaaS policy rule recommendations, and App-ID Cloud Engine (ACE),
simply activate SaaS Security Inline using one of the following
activation types, depending on whether you have an Enterprise Level
Activation (ELA) license type or non-ELA:
- (non-ELA) Activation email that you received.
- (ELA) Hub ELA Activations menu.
- (ELA) Customer Support Portal (CSP) Enterprise Agreements page.
If you are enabling
SaaS Security Inline for Next-Generation CASB, activate in SASE Cloud
Management Console using the activation email you received.
After
activation, your firewalls contact the cloud service and begin to
download any SaaS policy rule recommendations that you created.
SaaS
Security Inline activation:
- Creates a URL for SaaS Security Inline login.
- Pushes the SaaS Security Inline license to the firewalls that you select. Panorama does not require a license.
- Enables a secure and encrypted connection and successful, mutual authentication between SaaS Security Inline, Palo Alto Networks firewalls, Panorama, and Strata Logging Service.
Before
you activate:
- Ensure that your environment meets all the activation requirements for the SaaS Security Inline
features you want to enable. (SaaS administrator)
Requirement SaaS VisibilitySaaS Policy Recommendations and ACEOne or more firewalls running PAN-OS 10.1 or later with or without Panorama.N/AYesOne new or existing Strata Logging Service license per SaaS tenant.YesYesSame Support Account (CSP ID) for SaaS tenant, Strata Logging Service, Enterprise DLP, and firewalls.YesYesOne SaaS Security Inline license per firewall.YesYesEnterprise DLP license on NGFW and in the same CSP account as the SaaS tenant.Only required if you want to use the Data Profiles option for SaaS policy rule recommendationsN/AYesBecause SaaS Security Inline requires network traffic data for analysis, you must enable firewalls to forward logs with that data to Strata Logging Service. Your SaaS Security Inline subscription requires that you also have an active Strata Logging Service instance, which stores the data logs from firewalls and streams them to SaaS Security Inline. - Start the ACE deployment. (Firewall
administrator / SaaS Policy Rule Recommendations)ACE deployment is required if you want ACE and SaaS policy rule recommendations. ACE deployment is not required for displaying SaaS application visibility data, though you must still configure log forwarding. Without logs for all firewalls, SaaS Security Inline cannot display SaaS application visibility data and might not be able to enforce policy rule recommendations.
- Bring the firewall and Panorama (if using) online.
- Install the device certificate.
After
you activate:
- Complete
your ACE deployment. (Firewall
administrator / SaaS Policy Rule Recommendations)Again, ACE deployment is required if you want ACE and SaaS policy rule recommendations. ACE deployment is not required for displaying SaaS application visibility data.
- Retrieve and verify SaaS Security Inline license, which the SaaS Security Inline activation pushed to your firewalls. Panorama doesn’t need a license. If you forget to do so, an error displays.
- Configure service route for data services.
- Create and verify connections to edge services and cloud service.
- Enable ACE on Panorama (if using)
- Configure log forwarding. (Firewall
administrator / SaaS Visibility)You’re instructed to do so during your ACE deployment. If you only want SaaS visibility features, ACE deployment is optional, but log forwarding is required with or without ACE and SaaS policy rule recommendations enabled.
- Initiate the SaaS Security Inline activation process based on your license type.An ELA (Enterprise Level Activation) license activates all your firewalls. A non-ELA license activates a fixed numbers of firewalls.
- (non‑ELA license) Open your SaaS Security
Inline activation email and click Activate,
then log in with your Palo Alto Networks Customer Support Portal
account credentials. The number of Activate buttons in the email you received depends on what you purchased. Each Activate button launches the same onboarding workflow that lets you activate all your purchased products together. Click any Activate button to begin. Additionally, your activation email depends on the type of activation: purchase, trial, or evaluation.It is important to keep the SaaS Security Inline activation email you received from Palo Alto Networks. In addition to containing confidential activation-related data, you will need this email to activate more firewalls later if you still have unused SaaS Security Inline licenses after completing the onboarding process.
- (ELA license) Log in to the hub with your Palo Alto Networks Customer Support Portal account credentials, then select SaaS Security from the ELA Activations menu on the hub.
- Log on to Customer Support Portal (CSP) with Super User, Domain Administrator, and ELA Administrator permissions, then navigate to Assets > Enterprise Agreements and click ELA-SaaS Inline Activation.
Select the products to activate, then Start Activation.If you have multiple items to activate, leave them all selected when you Start Activation.(non-ELA) Select a Customer Support Account, then NextIf you have more than one Support account, select the one with firewalls to subscribe to SaaS Security Inline.This step is not included in the ELA activation process because you begin the process in the Hub and, therefore, your Support account is already known.In SaaS Security Inline Setup, configure SaaS Security Inline.- Data Lake and Data Lake Region—You must have an
active Strata Logging Service or activate a new one now. Do one
of the following:
- New Strata Logging Service—Select Activate New if you are activating a new Strata Logging Service subscription, then choose its region.
- Existing Strata Logging Service—Select an existing Strata Logging Service instance to use if you did not purchase a new Strata Logging Service. If you have more than one Strata Logging Service instance, choose the one to which firewalls will forward logs with network traffic metadata.
- SaaS Tenant, SaaS Region,
and SaaS Subdomain—Do one of the following:
- New Tenant—Select Activate New to create a new SaaS Security Inline tenant, then type a subdomain name, which completes the URL for your SaaS Security Inline app and becomes the URL where you log in to the SaaS Security web interface. SaaS Subdomain is prepopulated with the domain name from your email address, but you can change it if you want.
- Existing Tenant—Select an existing tenant if you did not purchase a new Strata Logging Service or you don’t want to activate a newly purchased Strata Logging Service. Each SaaS tenant requires a unique Strata Logging Service. You cannot reuse Strata Logging Services. The onboarding process enforces this requirement and automatically populates SaaS Tenant with the SaaS tenant that is mapped to the existing Strata Logging Service. SaaS Region defaults to Strata Logging Service region.
Choose the Firewalls to enable for this SaaS Security Inline subscription, then Next.- (non-ELA) Select a firewall Model on the left and then select subscriptions for the Serial Number(s) of individual device(s) belonging to that model on the right. Observe how many SaaS Security Inline subscriptions are assigned and still available for the selected model near the top of the page. Track the number of licenses each model will use and how many are still available in the middle of the page.
- (ELA) Select Serial Number column to select all firewalls up to 200. For each activation session, you can activate a maximum of 200 firewalls. To activate more, repeat the activation process.
The following tables lists each firewall type that the SaaS Security Inline license types support:Firewall typesSaaS Security Inline license typesProdEvalTrialLabProd (Production)YesNoYesNoEval (Evaluation)NoYesNoNoLabNoNoYesYesWhen you purchase SaaS Security Inline production subscriptions, the licenses are specific to firewall models. It’s not possible to use licenses created for one model with a different model. On the other hand, when evaluating SaaS Security Inline, Palo Alto Networks provides temporary eval and trial licenses that can be used on any firewall.A firewall type—prod, eval, and lab—is defined by the firewall SKU. To see the SKU for a firewall, log in to your Customer Support Portal account and navigate to AssetsDevices and check the entry for the serial number of your firewall in the Model Name column. This is the SKU, which indicates the firewall type as follows:- prod SKU—ends with the firewall model name; for example, PAN-PA-200
- eval SKU—ends with -E30, which stands for Eval + 30 days; for example, PAN-PA-200-E30
- lab SKU—ends with -LAB; for example, PAN-PA-200-LAB
Verify your activation selections, read and agree to the terms and conditions, then Activate Subscription.(non‑ELA) To check how many subscriptions will be used and how many remain, hover your cursor over the information icon next to Activate Subscriptions on <number> firewalls. A pop-up panel displays the total number of purchased SaaS Security Inline subscriptions you have, how many will be activated in this session, how many were previously activated, and how many have not yet been chosen for activation.Depending upon what you onboard, the activation process creates a URL for your SaaS Security web interface and applies SaaS Security Inline licenses to the selected firewalls and links them to your SaaS Security account. During ACE deployment, your firewall administrator retrieves the license keys from the license server. - (non‑ELA license) Open your SaaS Security
Inline activation email and click Activate,
then log in with your Palo Alto Networks Customer Support Portal
account credentials.