Baramundi
Connect Baramundi to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Baramundi to collect mdm evidence with automated compliance tests, switched on per workspace.
| Category | MDM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Baramundi's guide | docs.baramundi.com |
Connect with an API token
-
In Baramundi:
- Create or choose a baramundi Management Suite user account for Safeguard to sign in to bConnect (the bMS REST interface) with a username and password. The bConnect user must have the right permissions from baramundi; give it read-only rights on endpoints and AD users.
- Publish bConnect over https on port 443, either through the baramundi Gateway (the gateway server must be reachable from the internet) or through an Azure Hybrid Connection (System Administration › Interfaces › bMS-Interface › Setup Interface Gateway), and use Test connection to check it.
Where to find the other values:
- Server URL: The https hostname under which your bConnect interface is published (port 443).
Baramundi's public documentation does not cover every step.
The fetched baramundi help pages do not name the specific permissions a bConnect user needs, nor the console path to assign them, so the read-only role setup is not sourced. Credentials are an ordinary bMS user's username and password; nothing is displayed once.
Source: bts.baramundi.com, bts.baramundi.com, checked 2026-10-07.
The permissions Safeguard needs:
read-only role on endpoints and AD users. -
On Compliance › Connectors, open Baramundi, click Connect, choose API token and fill in:
Field What to enter Server URL Required. Your own server: an https address reachable from the internet. Username Required. Password Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Baramundi 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC6.2, CC6.8, CC7.1 | 4 |
| ISO/IEC 27001 | Automated tests | A.5.9, A.8.1, A.8.8, A.8.9 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5), 164.310(d)(1) | 4 |
| PCI DSS | Automated tests | 6.3.3, 12.5.1 | 4 |
| NIST CSF 2.0 | Automated tests | ID.AM-01, PR.PS-02 | 4 |
These tests are switched on per workspace by the Safeguard team.
Related
- MDM connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks