Problem Description
Today the DMG install/enrollment script is generated with a fixed set of scanning features (AI agent detection, MCP inventory, browser extensions, package inventory, etc.) baked in. There's no way to choose which features to enable before generating the script for a fleet, and no visibility afterward into how many enrolled devices actually have each feature active.
Proposed Solution
- Add a feature-selection step in the UI, before the DMG install script is generated, allowing admins to toggle which scanning features should be included/enabled for the devices that run that script.
- Add dashboard tracking/reporting showing, per feature, how many (or what percentage of) devices currently have that feature enabled, giving admins visibility into feature adoption/coverage across their fleet.
Alternatives Considered
Feature toggling could instead be exposed only via a config file or CLI flags post-install, but surfacing it in the UI at script-generation time is more discoverable and avoids requiring admins to hand-edit per-device configs.
Additional Context
The device-tracking piece (2) is called out as a required part of this feature, since it depends on the agent/dashboard knowing which features are active per device.
Problem Description
Today the DMG install/enrollment script is generated with a fixed set of scanning features (AI agent detection, MCP inventory, browser extensions, package inventory, etc.) baked in. There's no way to choose which features to enable before generating the script for a fleet, and no visibility afterward into how many enrolled devices actually have each feature active.
Proposed Solution
Alternatives Considered
Feature toggling could instead be exposed only via a config file or CLI flags post-install, but surfacing it in the UI at script-generation time is more discoverable and avoids requiring admins to hand-edit per-device configs.
Additional Context
The device-tracking piece (2) is called out as a required part of this feature, since it depends on the agent/dashboard knowing which features are active per device.