Safeguard Docs
Compliance ConnectorsSetup by categoryTicketing

Opsgenie Alerts

Connect Opsgenie Alerts to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Opsgenie Alerts to collect ticketing evidence with automated compliance tests, switched on per workspace.

CategoryTicketing
Connect withAPI token
What a connection producesAutomated compliance tests
Opsgenie Alerts's guidesupport.atlassian.com

Connect with an API token

  1. In Opsgenie Alerts:

    1. In Opsgenie, go to Settings › App Settings › API Key Management.
    2. Click Add New API Key.
    3. Enter a name for the key and select only the access rights Read and Configuration Access.
    4. Click Add API Key to save it, then copy the key.

    Opsgenie Alerts's public documentation does not cover every step.

    The fetched page does not say whether the key is shown once or how to tell the US from the EU region (EU accounts use an EU Opsgenie domain; not verified here).

    Source: support.atlassian.com, checked 2026-10-07.

    The permissions Safeguard needs: Read, Configuration access.

  2. On Compliance › Connectors, open Opsgenie Alerts, click Connect, choose API token and fill in:

    FieldWhat to enter
    API keyRequired. Stored encrypted and never shown again.
    RegionRequired.
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Opsgenie Alerts and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

FrameworkEvidenceControlsTests
SOC2Automated testsA1.1, CC6.2, CC7.45
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.5.24, A.6.55
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4), 164.308(a)(6)5
PCI DSSAutomated tests7.2.4, 8.2.5, 12.10.15
NIST CSF 2.0Automated testsGV.RR-02, PR.AA-01, PR.AA-05, RS.MA-015

These tests are switched on per workspace by the Safeguard team.

On this page