Safeguard Docs
Compliance ConnectorsSetup by categoryVulnerability Scanning

Edgescan

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

Record your Edgescan 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 Edgescan:

    1. Sign in to the Edgescan portal at https://live.edgescan.com and obtain your API key there (Edgescan's public pages only say the API key is obtained from https://live.edgescan.com and sent as the X-Api-Token header).

    Where to find the other values:

    Edgescan keeps the full instructions behind sign-in; this is what its public pages say.

    Edgescan's API and help documentation are inside the signed-in portal; help.edgescan.com and docs.edgescan.com did not respond and the API docs endpoint requires sign-in. The menu path to the API key and any read-only option could not be sourced publicly.

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

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

Edgescan 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