Skip to content
Connection Guide

Connect SecurityScorecard Attack Surface Intelligence Without Breaking the Audit Trail

Use this guide to connect SecurityScorecard Attack Surface Intelligence or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategorySecurity
Checklist3 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect SecurityScorecard Attack Surface Intelligence and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated read-only SecurityScorecard API token for the Aurora bot account.
  2. 2
    Store base_url and api_token; optionally constrain collection to portfolio_ids when the customer only wants specific portfolios onboarded.
  3. 3
    Validate by listing portfolios and retrieving one bounded company or issue page.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

api_token

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.