Safeguard Docs
Compliance ConnectorsSetup by categoryDigital Signature

Ironclad

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

Connect Ironclad to collect digital signature evidence with automated compliance tests, switched on per workspace.

CategoryDigital Signature
Connect withAPI token
What a connection producesAutomated compliance tests
Ironclad's guidedeveloper.ironcladapp.com

Connect with an API token

  1. In Ironclad:

    1. In Ironclad, click your user profile dropdown at the top right-hand corner and select Company Settings.
    2. Select the API tab on the left sidebar (visible only if the API add-on is enabled for your instance).
    3. Click Create new app, enter a name, and click Create app.
    4. Copy the client ID and secret; you will not be able to access the secret again.
    5. After closing the modal, set Grant Types to client credentials and, under Requested Resource Scopes, select only scim.users.readUsers; click Save Changes.
    6. Request a token: POST https://ironcladapp.com/oauth/token with grant_type=client_credentials, scope=scim.users.readUsers, client_id and client_secret; paste the returned access token into Safeguard.

    Where to find the other values:

    • Environment (optional): Use the Ironclad environment you sign in to: ironcladapp.com (most customers), eu1.ironcladapp.com (EU), or demo.ironcladapp.com (demo). Client apps only work in the environment where they were created.

    Ironclad shows the secret only once, so copy it before you leave the page.

    Source: developer.ironcladapp.com, developer.ironcladapp.com, developer.ironcladapp.com, checked 2026-10-07.

    The permissions Safeguard needs: scim.users.readUsers.

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

    FieldWhat to enter
    Access tokenRequired. Stored encrypted and never shown again.
    Environment (optional)—
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Ironclad 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 testsCC6.2, CC6.32
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.6.52
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4)2
PCI DSSAutomated tests7.2.4, 8.2.52
NIST CSF 2.0Automated testsPR.AA-01, PR.AA-052

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

On this page