Browser Extension

Swift Security Browser Extension Onboarding Guide

Welcome to Swift Security! Follow this guide to seamlessly onboard your users to the Swift Security browser extension.

Option 1: Easy Path for Small Number of Test Users

Step 1: Associate Test Users with your Tenant

• Compile the email addresses of test users and share with the Swift team. We will manually associate these users with your tenant. For larger deployments, see below which includes Directory integrations and Mobile Device Management deployments.

Step 2: Notify Test Users

• Email the test users asking them to install the Swift Security Browser extension on one or more Browsers (on Mac or Windows)

• • https://chromewebstore.google.com/detail/caagpeigabceamfbclichjenfkcnekha?utm_source=item-share-cb

  • https://addons.mozilla.org/en-US/firefox/addon/swift-security-extension/

• Provide instructions on Browser Installation (see below)

Step 3: Browser Installation

• Each Test User should download the Swift Security browser extension directly from the browser extension store(s) for the browsers they want to test. We suggest that they pin the extension in their browser, but it is not required.

• Users are then required to log in to the extension using the emails shared in Step 1. Note, if the user installs but does not login to the browser extension, they will not be able to use the browser.

• After logging into the Browser Extension, the user should confirm that they are able to use the browser as usual.

• Note, the user login is needed to associate the user with the tenant and to allow for granular policies. Note that for this deployment method, users can disable or log out of the extension at their discretion.

Step 4: Confirm Tenant Ingestion of Events

• Confirm the tenant is ingesting the user activities

  • Even prior to setting up policies, you should start to see events (for example, browse to chatgpt.com and enter a prompt).

  • After setting up policies (see Admin Guide), you will see alerts for policy violations as well as dashboards and other analytics & reporting.

Option 2: Larger, Enterprise Deployments

Step 1: Directory Integration

• The Directory integration allow you to (a) create granular and dynamic policies based on ingested directory fields such as user name, user group, etc and (b) enrich event, alerts, and dashboards with the same user metadata.

• In the Swift Security Console, navigate to integrations → Directory Sync. Then select your preferred directory. If you need support for another directory contact [e-mail]

  • https://app.gitbook.com/o/UsxSL3q0yihec5gSU9zc/s/GYBoroX54MgrUz8eIUsk/~/changes/234/onboarding/directory-sync

• Follow instructions to securely connect your Directory to Swift Security.

Step 2: Mobile Device Management (MDM) Deployment

• MDM enables you to quickly deploy the extension to large numbers of users and to enforce the extension (and other browser settings).

• In Swift Security Docs, navigate to Onboarding → MDM. Then find your preferred MDM Provider. If you need support for another MDM provider, contact support @swiftsecurity.ai.

  • https://app.gitbook.com/o/UsxSL3q0yihec5gSU9zc/s/GYBoroX54MgrUz8eIUsk/~/changes/234/onboarding/mdm

• Follow provided instructions to integrate Swift Security with your MDM solution to deploy the browser extension automatically across devices, utilizing your preferred deployment options.

Step 3: Deployment and Verification

• Navigate to Integrations → Directory Sync and then drill down to see the users synchronized.

• Navigate to Assets → Users to see the users that have generated events or alerts so far.

• Navigate to Policies and create a new policy to see the list of users and the directory metadata fields.

• Navigate to alerts and drill down on the alert to view the user metadata.

Support and Resources

• For additional assistance, contact Swift Security Support at [e-mail].