Settings

The Settings page manages organization-wide Dev Machine Guard configuration: the telemetry key that agents authenticate with, and the device-activity threshold that controls when a device is marked inactive.

These settings apply to every device in your organization.

Telemetry Key

Dev Machine Guard agents authenticate to the StepSecurity backend using a telemetry key. The key is used by all Dev Machine Guard agents on your tenant.

The backend supports two keys, Primary and Secondary, and accepts either one. This lets you rotate keys without downtime: agents keep using their baked-in key until they are redeployed.

Fields

• Key selector: switch between the Primary and Secondary key.
• Key value: masked by default. Use the reveal (eye) icon to view it and the copy icon to copy it.
• Rotate: generate a new value for the selected key.
• Last rotated: shows when the selected key was last rotated (Never if it has not been rotated).

Rotating the telemetry key

Because the backend accepts either key, rotate in this order to avoid interrupting agents:

1. Rotate the Secondary key.
2. Redeploy your fleet with the new Secondary key so agents pick it up.
3. Rotate the Primary key.

Agents continue authenticating with their baked-in key until they are redeployed, so following this order ensures no device loses connectivity mid-rotation.

Device Activity

Device Activity controls when a device is marked inactive in the device list. This applies to every device in your organization.

Current setting shows the active threshold in plain language, for example: Devices are marked inactive after 3 days without telemetry.

Inactive after (days): mark a device inactive once it has not reported telemetry for this many days. Enter a value in the Days field and select Save device activity to apply it.

This is the same threshold exposed as Inactive threshold in Step 3 of the Script wizard. Changing it in either place updates the organization-wide setting.