Connection/Sync Status
The Integrations page shows all of your connected applications in one place, including connection status and recent sync activity. Use it to confirm everything is connected correctly and to spot issues early when a sync fails or a connection drops.
The table columns break down as follows:
Connection - The name of the integration or application chosen
Child Connections - will list the number of child connections with a link to review each and their status
Connection Status - Indicates whether the integration is currently connected to Secureframe. (Connected, Pending, Disconnected)
Sync Status - Reflects the success or failure of the latest data synchronization attempt. (Successful, Partially Successful - View error, Failed - View Errors)
Last Completed Sync - the last date, time a sync completed
Sync - options to sync an integration manually
Note: If your Sync Status provides an error, click the "View Error" button to review the raw error data and created date.
Additional Integration Settings
Some integrations like AWS, Github, JIRA, etc. will offer additional settings available after a successful connection. Click the gear icon next to each to adjust those additional settings.
Manually sync an integration
All Secureframe integrations automatically sync daily. When an integration syncs, tests are automatically refreshed and any changes that were made within the source (e.g., Secureframe Agent, AWS) will be updated within Secureframe.
If you make a change within a source (i.e., download the Secureframe Agent onto a device) and want to see those changes in Secureframe immediately, you can perform a manual sync for any integration.
How to Perform a Manual Sync
In the Secureframe application, navigate to the Integrations page on the Monitoring dashboard.
In the Native tab, find the connected integration you would like to manually sync.
Click the Sync button to the right of the integration.
Once the sync completes, the Last Completed Sync column will update accordingly.
Native Integrations
Secureframe offers over 300 native integrations for customers to connect, with the option to create custom integrations as well.
The Integrations page is split into two tabs:
Native. All native integrations you have initiated, including connected and disconnected connections. From this tab you can also add a new native integration by clicking + Add native connection in the top right.
Custom. Any custom integrations you have configured. For more information, see Create Custom Integrations.
Removing/Archiving an Integration
To archive a connection, first ensure the connection is no longer needed and all its associated resources can be archived.
Visit the Integrations page.
Open the 3 dot menu to the right of the connection.
Select “Archive”.
Note: This cannot be undone
Use the Guided Workflow After “Connect”
Each integration offers a tailored setup flow immediately after clicking Connect. If further actions are required, such as granting permissions, enabling APIs, configuring settings in the external app, or linking service accounts, that workflow will surface those steps. It’s your first line of indication that additional configuration is needed.
Understanding the View Details Panel
Before or after you connect an integration, click its View Details button. Within that panel, you’ll find two critical tabs:
Details: Overview, associated tests and controls
Permissions & Data: What permissions the integration will request and which data sets will be pulled
If the integration requires any special permissions or setup actions outside of the default path, those details are typically documented here.
Frequently Asked Questions (FAQ)
I changed a device setting (password policy, screen lock, firewall) but Secureframe still shows it failing. How do I refresh it?
This is a two step update. First, the device has to check in with the new setting, which requires the Secureframe Agent to be running and the device online for at least 5 minutes.
Then run a manual sync of the Secureframe Agent integration from the Native tab. The check reflects your latest device settings once the sync completes.
For device-specific steps and MDM options, see FAQs: Secureframe Agent: macOS profiles, password policy, and endpoint checks, the Password Policy Check, and the Screen Lock / Session Timeout Check articles.
What is the difference between the Vendors and Integrations page?
The Integrations page shows a list of all your connected services and the services available to connect. Under this page, you also have the ability to trigger a sync for each connected service to refresh the data within Secureframe. The connected services will also appear as a vendor under the Vendors page.
For example, if you created a new employee email and do not see the new employee in Secureframe yet, you can trigger a sync for GSuite which will refresh the list of employees. After the sync, the new employee email should surface under Secureframe's employee list.
The Vendors page is a master list of all your vendors where you can assign risk levels, upload security certifications, and manage your vendors. Unlike the Services page, adding a vendor to the list will not integrate the service to Secureframe.
My SimpleMDM sync failed with a 403 error. Is this a permissions problem?
Not always. If your SimpleMDM account is locked for billing (for example, an expired subscription or unpaid invoice), Secureframe now surfaces that reason directly in the sync error instead of a generic permissions message.
Sign in to your SimpleMDM admin console and confirm the account is active and in good standing, then run a manual sync from the Integrations page.
If billing is current and the sync still fails, open View Error on the integration and verify the API key and organization ID in your connection settings.
What happens when a connection is archived?
Any resources that were synced from the connection will also be archived with the exception of background checks, which will remain available.
Devices will be archived. If a new MDM provider is connected later on, Secureframe will be able to identify the device and unarchive the device with the new synced data.
Archiving connections will not archive the vendor. Even if all connections are archived, the vendor will still be on the Vendors list.
If you are no longer using the Vendor at all, archive from the Vendors page.
Where is the best place to find the most up-to-date information about Integration related permissions data?
The single source of truth for Integration permissions and Data, or Integtation Testing and Controls are located directly in the platform.
To find integration permissions & Data:
Go to the "Integration" page
Select the "Available" tab
Search for your integration
Click "View Details"
Then click the "Details" tab to see Test & Controls or "Permissions and Data" tab to see permissions related
You can view all permissions and data pulled for an integration before connecting it.
My integration shows Connected and syncs successfully, but the vendor does not appear on the Vendors page. Why?
In most cases, a successfully connected native integration should create or update a corresponding vendor on the Vendors page. If it does not:
Confirm Connection Status is Connected and Sync Status is Successful (not Partially Successful or Failed).
Run a manual sync from the Integrations page and wait for Last Completed Sync to update.
Search the Vendors page by the integration name (for example Datadog, GitHub, AWS). Check archived or filtered views.
Confirm you are looking at Vendors, not only Integrations. Integrations show connection health; Vendors is the master vendor list for risk management.
If multiple integrations of the same type exist, check for duplicate or archived connections that may affect which vendor record is active.
If the integration has been connected for more than 24 hours, syncs successfully, and the vendor still does not appear, contact Support with the integration name, connection status screenshot, and approximate date connected.
Note: Some integrations populate the Vendors page only after a successful first sync with vendor-relevant data. A Connected status alone may not be enough if the sync has not completed.
How long does a manual sync take, and when should I expect tests to update?
Most integrations complete a manual sync within a few minutes. Large cloud accounts (AWS, Azure, GCP) can take longer depending on account size.
Wait until Sync Status shows Successful and Last Completed Sync updates before checking related tests.
Tests refresh after a successful sync, but some may take additional time to re-evaluate against the latest data.
If Sync Status stays In progress for more than 2-4 hours, contact Support with the integration name and how long it has been in progress.
I fixed the issue in AWS, Azure, or GitHub but tests still fail. What should I check?
Confirm the fix was made in the in-scope account, project, or repo Secureframe monitors. Open the integration gear icon settings to verify scope.
Run a manual sync from the Integrations page and wait for Sync Status to show Successful.
Open the failing test and review whether findings reference old resources. Historical data may persist until the next evaluation cycle even after a successful sync.
For personnel-related changes (new hire, deprovisioned user, role change), sync the HRIS or IdP integration (for example Google Workspace, Okta, or Finch), not only the cloud integration.
If sync succeeded and tests still fail after 24 hours, contact Support with the integration name, sync timestamp, and failing test name.
My Azure or GCP sync has been "In progress" for hours. Is that normal?
Short delays are common during large syncs or after permission changes.
If sync stays In progress for more than 2-4 hours, or if Connection Status changes to Disconnected, avoid repeatedly re-triggering syncs. Contact Support with the integration name and how long it has been in progress.