Mend

Connect Mend to collect vulnerability scanning evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Mend:

   1. Log into the Mend Platform, click the settings gear in the top right corner, then click Administration.
   2. Click Users in the left Administration list, then click + Add Service User in the top right corner of the Users table.
   3. In the Add Service User dialog, enter the service user's name in User Information, optionally pick groups under Associate Groups, and click OK. An email address is auto-generated from the user name.
   4. In the Users table, find the service user, click the three ellipses button and select Copy Token to copy its user key.
   5. Give the service user's group the Auditor role (read-only access to Mend data, for integrations (service users)): Administration › Groups › select the group › Roles tab › + Add Role, choose the role at the Organization level or for specific Application(s), and click Add.

   Where to find the other values:

   • Email: The service user's auto-generated Email shown in the Users table (for your own user: Mend Platform › My Profile › General).
   • Organization ID: Mend Platform › Administration › General Configuration › Organization UUID.
   • Base URL (optional): Your Mend environment's API 3.0 base URL, in the form https://api-<your-instance>/api/v3.0.

   Service users have no GUI access. A regular user's key is at Mend Platform › My Profile › User Keys. Mend API 3.0 logs in with email, organization UUID and user key, and issues a refresh token valid for 30 minutes. If no group is chosen, the service user joins the default Users group; check that group's roles. Verification: the fetched pages do not state which role may create service users, and do not document an Administration › Groups › Users › + Add Users path, so those parts were removed.

   Source: docs.mend.io, docs.mend.io, docs.mend.io, checked 2026-10-07.

   The permissions Safeguard needs: Auditor (service user).

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

   Field	What to enter
   Email	Required.
   User key	Required. Stored encrypted and never shown again.
   Organization ID	Required.
   Base URL (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Mend 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.

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

Related

• Vulnerability Scanning 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