Settings

The Settings page is where you configure deployment and execution of the Developer MDM data collection script.

From this page, you can generate and download the installation script used to collect telemetry from developer machines.

Installation Script

Developer MDM does not require installing a proprietary StepSecurity agent.

Instead, StepSecurity provides a lightweight, self-contained script that you deploy using your existing MDM or EDR tooling.

The script:

• Runs on developer machines at a configured interval

• Collects metadata about IDE extensions and local npm packages

• Does not collect source code, secrets, credentials, or personal data

• Sends collected telemetry securely to the StepSecurity platform

• Embeds all required configuration (such as API endpoint, scan frequency, and enabled features) directly in the generated script

The Developer MDM script is also versioned, making it easy for customers to upgrade to the latest version. Customers can also view what changed between versions to understand exactly what updates they are adopting.

Deployment Options

The installation script can be deployed using your existing endpoint management infrastructure. The deployment model depends on whether you are evaluating Developer MDM or running it in production.

One-Time Execution (Proof of Concept)

Use this option when you want to evaluate Developer MDM or validate data collection on a limited set of devices.

Configure your MDM to run the following command once on selected developer machines:

execute stepsecurity-agent.sh

The script executes a single scan, collects telemetry, and reports the results to StepSecurity without setting up recurring execution.

This approach is recommended for:

• Proof of concept evaluations

• Initial testing on a small number of devices

• Validating visibility before broader rollout

Scheduled Execution (Production)

Under scheduled execution, you can either configure your MDM to execute stepsecurity-agent.sh periodically. In our experience, most MDM solutions do provide this option and this is the preferred way to run the script periodically.

If your MDM doesn't support periodic execution option out of the box, you can use operating system's native features to run the script periodically by running stepsecurity-agent.sh install through your MDM on developer machine.

Deploy the script once using your MDM and configure periodic execution by running:

execute stepsecurity-agent.sh install

This installs the script and sets up recurring execution using your MDM’s scheduling capabilities.