Safeguard Docs
Compliance ConnectorsSetup by categoryVulnerability Scanning

Arnica

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

Record your Arnica connection as vulnerability scanning evidence. Automated collection is not available for this provider yet.

CategoryVulnerability Scanning
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In Arnica:

    1. Sign in to Arnica with an admin account.
    2. Navigate to Admin › API.
    3. Create an Arnica API key with read scopes only (the documented example scope is sbom-api:read), and copy the key.

    Where to find the other values:

    Arnica's public documentation does not cover every step.

    The only public Arnica doc found that describes API key creation is the SBOM API page (Admin → API, scopes such as sbom-api:read). The full list of read scopes for findings and the exact button labels on the API page are not in the public docs; check the scope list on the page or the swagger reference. Docs do not say whether the key is shown only once.

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

  2. On Compliance › Connectors, open Arnica, 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

Arnica 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
SOC2AttestationCC7.11
ISO/IEC 27001AttestationA.8.81
HIPAA Security RuleAttestation164.308(a)(1)1
PCI DSSAttestation6.3.3, 11.3.11
NIST CSF 2.0AttestationID.RA-011

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

On this page