Onboard a PagerDuty App to SSPM
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 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
Onboard a PagerDuty App to SSPM
Connect a PagerDuty instance to SSPM to detect posture risks.
For SSPM to detect posture risks in your PagerDuty instance, you must onboard your
PagerDuty instance to SSPM. Through the onboarding process, SSPM logs in to a
PagerDuty account. SSPM uses this account to scan your PagerDuty instance for
misconfigured settings. If there are misconfigured settings, SSPM suggests a
remediation action based on best practices.
SSPM gets access to your PagerDuty instance through account credentials that you
provide. SSPM can access the account directly or through the Okta or Microsoft Azure
identity providers. Having SSPM access the account through one of these identity
providers requires MFA, which adds an extra layer of security.
To onboard your PagerDuty instance, you complete the following actions:
Collect Information for Connecting to Your PagerDuty Instance
To access your PagerDuty instance, SSPM requires the following information, which you
will specify during the onboarding process.
Item | Description |
---|---|
User | The username or email address of the
administrator account. The format that you use can depend on
whether SSPM will be logging in directly to your account or
through an identity provider. Required Permissions:
The user must be the PagerDuty Account Owner. |
Password | The password for the administrator account. |
PageDuty Subdomain | If your account has a personalized PagerDuty subdomain, the name of the subdomain. |
Region | PagerDuty manages data centers in different geographical regions. You must specify your service region. |
If you are using Okta as your identity provider, you must provide SSPM with the
following additional information:
Item | Description |
---|---|
Okta subdomain | The Okta subdomain for your organization. The subdomain was included in the login URL that Okta assigned to your organization. |
Okta 2FA secret | A key that is used to generate one-time passcodes for MFA. |
If you are using Azure Active Directory (AD) as your identity provider, you must
provide SSPM with the following additional information:
Item | Description |
---|---|
Azure 2FA secret | A key that is used to generate one-time passcodes for MFA. |
As you complete the following steps, make note of the values of the items
described in the preceding tables. You will need to enter these values during
onboarding to access your PagerDuty instance from SSPM.
- Identify the administrator account that SSPM will use to access your PagerDuty instance. The administrator must be the PagerDuty Account Owner. SSPM needs Account Owner permissions to monitor your PagerDuty instance.Determine whether you want SSPM to log in to the administrator account directly, or through an identity provider.Using an identity provider adds an extra layer of security by requiring MFA using one-time passcodes. You can use Okta or Microsoft Azure as the identity provider for accessing the administrator account. However, if you use an identity provider, SSPM requires more information for MFA.
- (For Okta log in) To access the administrator account through Okta:
- (For Microsoft Azure log in) To access the administrator account through Microsoft Azure:
Determine if your organization has a personalized PagerDuty subdomain. For example, your organization might have a personalized subdomain that is set to your company's name. You can determine if you have a personalized subdomain from your PagerDuty URL. If you have a personalized subdomain, it is prepended to your PagerDuty URL. For example, <subdomain>.pagerduty.com.If you have a personalized subdomain, make note of it before you continue to the next step. You must provide this information to SSPM during the onboarding process. If you do not have a personalized subdomain, you will leave the associated field blank during the onbaording process.Make note of your PagerDuty service region, which you can determine from your PagerDuty URL after you log in to your account. If the URL contains the string eu, then your region is the European Union (EU). If the URL does not contain a region code, then your region is the United States (US).Connect SSPM to Your PagerDuty Instance
By adding a PagerDuty app in SSPM, you enable SSPM to connect to your PagerDuty instance.- From the Add Application page (Posture SecurityApplicationsAdd Application ), click the PagerDuty tile.Under posture security instances, Add Instance or, if there is already an instance configured, Add New instance.Specify how you want SSPM to connect to your PagerDuty instance. SSPM can Log in with Credentials, Log in with Okta, or Log in with Azure.When prompted, provide SSPM with the administrator credentials, PagerDuty subdomain, and PagerDuty service region. If you do not have a personalized subdomain, leave the PagerDuty subdomain field blank. If SSPM is connecting to the account through an identity provider, specify the information that SSPM needs for MFA.Connect.