Deploying VibeSec Across the Organization

Use this method to deploy VibeSec across multiple machines using an MDM tool.

This approach allows your IT team to install, update, and enforce VibeSec across all developer machines without requiring manual setup.

VibeSec is platform-agnostic. You can apply the same principles and scripts using any MDM tool, such as Jamf, Microsoft Intune, or Kandji.

VibeSec installation can run repeatedly. When executed, it updates existing installations, reuses authentication when available, and restores configuration if it was changed or removed.

Running the installation script frequently ensures:

  • All machines run the latest version

  • The installation is restored if it is disabled or removed

Note Run the script every hour to keep VibeSec installed and up to date. Use a shorter interval for stricter enforcement.

Authentication methods

VibeSec supports two authentication methods for MDM deployment. The method you choose determines how developers are authenticated after installation and whether user setup is required in advance.

  • OAuth: Developers are prompted to authenticate in their browser when they first use VibeSec. This requires either organizational SSO to be configured in OX (so users are created automatically on first sign-in), or pre-existing OX users for each developer.

  • API token: Developers are authenticated automatically during installation. No additional sign-in is required, and there is no need to create OX users in advance.

OX provides a separate installation script for each authentication method.

Prerequisites

Prerequisite
Details

Node.js

Node.js version 22 or later must be installed on all target developer machines.

Network access

If your organization restricts outbound network traffic (for example, using a proxy or firewall), add the following domains to your allowlist: api.cloud.ox.security* ox-vibesec.s3.eu-west-1.amazonaws.com*

API token authentication

If you are using the API token authentication method, create a new VibeSec token before you begin.

OAuth authentication, auto-provisioning for new OX users

If you authenticate using OAuth and your developers do not already have OX user accounts, ensure that auto-provisioning is enabled in your OX settings. This allows OX to automatically create a user for each developer upon first login.

To enable auto-provisioning, see Sign in to OX for instructions.

Install VibeSec using MDM

Use your MDM tool to distribute and enforce VibeSec across machines.

The following example uses JumpCloud to demonstrate how to deploy VibeSec. The same principles apply to other MDM tools. Adjust the steps based on your environment.

Step 1: Create the command

  1. Go to your MDM tool.

  1. Create a new command.

Step 2: Configure execution and assign the command

  1. Set the command to run on a schedule.

  1. Set the execution interval:

  • (recommended option) Run every hour to keep VibeSec installed and up to date,

Or

  • Run every 5 minutes to enforce configuration and restore changes more quickly

  1. To assign the command, select the relevant device groups or devices.

Step 3: Verify deployment

  1. Go to a target machine.

  2. Confirm that VibeSec is installed.

  3. Verify that the script runs periodically.

  4. Check logs if installation fails.

Deployment scripts

Use the script that matches your operating system and authentication method.

Re-running the installation script does not affect the user if the installation is unchanged. If VibeSec was removed or modified, the script restores it automatically.

Last updated