Skip to main content
SecurAtlas supports several authentication methods depending on the provider you are connecting. This page walks you through the full connection process — from selecting a provider to verifying the connection is healthy — and explains how to configure sync schedules or remove a connection when needed.

​
Before you start

Navigate to Integrations in the left sidebar. The page shows all available providers grouped by category. Providers already connected appear in the Connected table at the top.
Providers marked Coming Soon cannot be connected yet. They are listed in the catalog so you can see which integrations are in development. Check back when the label is removed to connect them.

​
Connecting a provider

1

Select a provider

Find the provider you want to connect in the catalog. Click Connect on the provider card. A setup modal opens showing the required steps and fields for that provider.
2

Give the connection a name

Enter a display name for this connection. The default is the provider name, but you can change it — for example, to reflect the specific account or environment you are connecting (e.g., “AWS Production”).
3

Authenticate

Complete authentication using the method your provider requires. See the tabs below for OAuth and API key/credentials flows.
4

Wait for the initial sync

After authentication succeeds, SecurAtlas runs an initial sync. This may take a few minutes depending on the size of your environment. The connection status changes from Pending Setup to Connected once the first sync completes.
5

Review findings

Once synced, open the Findings tab to see what SecurAtlas detected. Findings are automatically mapped to your controls. See Integration findings for details.

​
Authentication methods

OAuth providers (such as Microsoft Entra ID and Google Workspace) redirect you to the provider’s authorization page to grant access.How it works:
  1. Open the connect modal for an OAuth provider.
  2. If the provider requires an App Registration (such as Microsoft Entra ID), the modal shows the Redirect URI and required API permissions. Configure these in your provider’s portal before proceeding.
  3. Fill in any required fields shown in the modal (for example, a Tenant ID or Admin email).
  4. Click Connect. SecurAtlas redirects you to the provider’s authorization page.
  5. Approve the requested permissions. You are redirected back to SecurAtlas automatically.
  6. SecurAtlas completes the connection and begins the initial sync.
If the OAuth token expires or is revoked later, SecurAtlas shows a Reconnect banner on the Integrations page. Click Reconnect on the banner to reauthorize without losing your existing configuration.

​
Verifying connection health

After connecting, check the Connected table on the Integrations page to confirm the connection is working.
ColumnWhat it shows
StatusConnected (green) means the last sync succeeded. Sync Failed (red) means the last sync encountered an error. Syncing (blue) means a sync is currently running. Pending Setup (amber) means the initial sync has not completed.
Last SyncRelative time of the most recent completed sync (e.g., “2h ago”).
EntitiesNumber of entities (users, devices, resources) imported from the provider.
Open FindingsNumber of findings from this connection that are still open.
If a connection shows Sync Failed, click the sync button (the circular arrow icon) to trigger a manual retry and check whether the issue resolves.

​
Manual sync vs. automated sync

By default, SecurAtlas syncs each connection on a schedule. You can also trigger a sync at any time. Manual sync: Click the sync icon on the right side of any connection row. SecurAtlas starts the sync immediately and updates the status in real time. A toast notification confirms when the sync completes, including the number of entities and findings processed. Automated sync: When you connect a provider, the sync interval defaults to every 24 hours. To change the interval, open the connect modal for that provider and expand Advanced settings. Set the sync frequency to your preferred cadence (for example, every 6 hours). A shorter interval keeps your findings fresher but increases API usage against the source provider.

​
Disconnecting a connection

To remove a connection, click the trash icon on the connection row and confirm the prompt. Disconnecting removes the active connection and stops future syncs. Synced entities and findings are retained — they remain in SecurAtlas so your historical data and any control evidence derived from them is preserved. If you want to reconnect the same provider later, you can do so at any time from the catalog.