Safeguard Docs
Compliance ConnectorsSetup by categoryMDM

IBM MaaS360

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

Record your IBM MaaS360 connection as mdm evidence. Automated collection is not available for this provider yet.

CategoryMDM
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In IBM MaaS360:

    1. MaaS360 web services credentials (App ID, App Version, Platform ID and App Access Key) are provisioned by IBM: contact IBM MaaS360 Support to provision an app authorized to use MaaS360 web services.
    2. Each call first authenticates with those values plus your Billing ID and an administrator username and password to get an authentication token valid for 60 minutes.

    IBM MaaS360 issues this credential through its API or its support team, not through its admin screens.

    Record-only connector. The fetched IBM page says to contact IBM MaaS360 Support for provisioning and gives no portal path; where to find the Billing ID and which admin role rights are needed were not confirmed on a fetched page.

    Source: ibm.com, checked 2026-10-07.

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

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. Click Connect with token.

Frameworks

IBM MaaS360 publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

FrameworkEvidenceControlsTests
SOC2AttestationCC6.8, CC7.11
ISO/IEC 27001AttestationA.8.11
HIPAA Security RuleAttestation164.310(d)(1)1
PCI DSSAttestation12.5.11
NIST CSF 2.0AttestationID.AM-01, PR.PS-021

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

On this page