Overview
Automate your compliance monitoring by connecting Swif MDM with Secureframe. This integration allows you to seamlessly sync device inventory and security evidence—such as encryption status, antivirus presence, and screen lock settings—directly into your Secureframe dashboard.
Prerequisites
Before you begin, ensure you have:
Administrator access to your Secureframe account.
Administrator access to your Swif MDM dashboard.
Step 1: Generate Secureframe API Credentials
To allow Swif MDM to communicate with Secureframe, you need to generate an API Key and API Secret.
Sign in to the Secureframe Console.
Navigate to Settings (or Your Profile -> Company Settings).
Select API Keys.
Click Create API Key.
Give the key a descriptive name (e.g., "Swif MDM Integration").
Copy and save both the API Key and the API Secret.
Note: The secret will only be shown once.
Step 2: Create a Custom Connection in Secureframe
Secureframe uses "Custom Connections" to route data from external tools like Swif.
In the Secureframe Console, go to Monitoring -> Integrations.
Select the Custom tab.
Click Create custom integration.
Fill in the details:
Name: Swif MDM
Description: Device and compliance evidence sync from Swif.
Once created, open the Swif MDM custom integration.
Copy the Connection ID (found in the integration details or the browser URL: `/custom-connections/<connection-id>`).
Step 3: Configure the Integration in Swif MDM
Now, link the two platforms using the credentials you gathered.
Log in to your Swif MDM Dashboard.
Navigate to Settings -> Integrations.
Find Secureframe.
Enter the following fields:
API Key: The key generated in Step 1.
API Secret: The secret generated in Step 1.
Custom Connection ID: The ID copied in Step 2.
Vendor Slug: Enter
swif(unless instructed otherwise by Secureframe).Region: Leave as Non EU unless your Secureframe account is hosted in the EU/UK.
Click Connect.
Swif will immediately trigger an organization-level sync to push your device data to Secureframe.
What Data is Synced?
Swif MDM pushes the following information to Secureframe to satisfy compliance controls:
Device Inventory: Serial Number, Model, OS Version, CPU, Memory, and MAC Address.
Security Evidence:
Antivirus: Verification that AV software (e.g., Falcon, XProtect) is active.
Hard Drive Encryption: Status of FileVault (macOS) or BitLocker (Windows).
Password Manager: Confirmation that the Swif Password Manager is installed.
Screen Lock: Verification that session timeouts and lock screens are enabled.
Auto Updates: Status of operating system automatic updates.
Firewall: Confirmation that the local firewall is enabled.
Troubleshooting
"Custom Connection not found": Double-check that the Connection ID in Swif matches the ID in the Secureframe Custom Integrations tab.
Authentication Failure: Ensure there are no extra spaces in the API Key or Secret. If the error persists, try generating a new API Key in Secureframe.
Data Not Appearing: After the first sync, you may need to use Secureframe's "Define Schema" workflow within the custom integration page to map Swif's data fields to your Secureframe asset fields.