Skip to content

The 25 PagerDuty security checks Black Cat runs

Black Cat SSPM evaluates 25 security policies against your PagerDuty configuration on every scan, classifies each finding by risk, and provides remediation steps. Browse them by topic below.

How to connect PagerDuty — what access Black Cat needs, and why.

Access control & privilege (6)

Logging & audit (7)

Configuration hardening (7)

Third-party & OAuth apps (3)

Other checks (2)

severity: high SSO Disabled fix difficulty: medium #

Enable SSO in PagerDuty account settings to enforce centralized identity authentication

  1. Sign in to PagerDuty as an Account Owner or Global Admin
  2. Navigate to Account > Account Settings > Single Sign-On
  3. Click "Set Up SSO" and choose your identity provider (Okta, Azure AD, etc.)
  4. Enter the SSO configuration details (Entity ID, SSO URL, certificate)
  5. Save the configuration and test SSO login before enforcing it
  6. Optionally enable "Require SSO" to block password-based logins

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.5 SOC 2 Type II CC6.1 CIS Controls v8 CIS-06.5 NIST CSF 2.0 PR.AA-03 GDPR (SaaS Security) GDPR-25.1 HIPAA (SaaS Security) HIPAA-312.d NIS2 Directive NIS2-21.j DORA (SaaS Security) DORA-9.4

severity: medium Advanced Permissions Disabled fix difficulty: medium #

Enable Advanced Permissions in PagerDuty to enforce granular role-based access control

  1. Sign in to PagerDuty as an Account Owner
  2. Navigate to Account > Account Settings
  3. Locate the "Advanced Permissions" section
  4. Click "Enable Advanced Permissions"
  5. Review the role assignments for all users and adjust as needed
  6. Save the changes

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.5 SOC 2 Type II CC6.1 CIS Controls v8 CIS-06.5 NIST CSF 2.0 PR.AA-03 GDPR (SaaS Security) GDPR-32.1b.i HIPAA (SaaS Security) HIPAA-312.d NIS2 Directive NIS2-21.j DORA (SaaS Security) DORA-9.4

The information on this page is provided for general informational purposes and is believed to be accurate as of its most recent update. Product names, logos, and trademarks are the property of their respective owners and are used for identification purposes only; their use does not imply any affiliation with or endorsement by those owners. Descriptions of third-party applications and of compliance frameworks are based on publicly available documentation and may change over time.

See these checks run on your stack

Start a free 14-day trial — no credit card required.

Start Free Trial