Wallarm
Connect Wallarm to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Wallarm connection as vulnerability scanning evidence. Automated collection is not available for this provider yet.
| Category | Vulnerability Scanning |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Wallarm:
- In Wallarm Console, go to Settings › API tokens (as an Administrator or Analyst).
- Create a token: choose a personal token (or a shared token if you are an Administrator), set the usage to Wallarm API, and set an expiration date.
- For permissions, select the predefined role Read Only.
- Save the token and copy its value.
Where to find the other values:
- Base URL (optional): The Wallarm API host for the Wallarm Cloud (US or EU) your Console account is on.
Wallarm's public documentation does not cover every step.
Wallarm's docs describe the token options (personal/shared, usage Wallarm API, expiration, permissions such as Read Only) but not the button names on the API tokens page, so the create/save button labels are not sourced. A personal token's value can only be used by its owner; if the owner's permissions are reduced or the owner is disabled, the token follows. Wallarm emails 3 days before expiry. API host names per cloud were not verified on the fetched page.
Source: docs.wallarm.com, checked 2026-10-07.
-
On Compliance › Connectors, open Wallarm, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
Wallarm 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC7.1 | 1 |
| ISO/IEC 27001 | Attestation | A.8.8 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(1) | 1 |
| PCI DSS | Attestation | 6.3.3, 11.3.1 | 1 |
| NIST CSF 2.0 | Attestation | ID.RA-01 | 1 |
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