Device Agent lineage and extension reference
Technical reference for the ZebraByte Device Agent lineage, supported extension points, custom-agent API integration and the security review principles applied to endpoint posture software.
The ZebraByte Device Agent is part of the ZebraByte Cloud product and is not offered as an ZebraByte project. This page is preserved because the earlier agent lineage contains useful implementation, portability and security-review context for teams integrating endpoint posture data.
Historical source layout
Section titled “Historical source layout”The earlier agent implementation lived in the upstream platform repository and separated the service/installer layer from the device-posture client logic:
| Historical path | Role |
|---|---|
cmd/probo-agent | CLI, installers and service integration |
pkg/deviceagent | Enrollment client, heartbeat and posture-check logic |
That separation remains useful when reviewing the security model: installer/service behavior and the posture-reporting protocol have different privilege and threat boundaries.
Current extension path
Section titled “Current extension path”For ZebraByte Cloud, integrations should use supported product interfaces rather than modifying or redistributing the platform source code.
Good extension scenarios include:
- connecting additional endpoint or asset-management systems;
- mapping posture information from an existing security stack into ZebraByte workflows;
- using the Device Agent API for a supported custom collector or integration;
- building automation around enrollment, inventory, evidence and remediation workflows;
- requesting ZebraByte support for additional operating systems or architectures.
If the standard ZebraByte Device Agent does not cover an environment you need, use the Device Agent API or contact ZebraByte to discuss a supported integration path.
Security review principles
Section titled “Security review principles”A review should cover:
- privilege boundaries and least privilege;
- whether the agent remains a posture reporter rather than remote-control software;
- enrollment and authentication flows;
- dependency and supply-chain exposure;
- update and package integrity;
- data minimization and transport security;
- test coverage across supported platforms.
Platform coverage reference
Section titled “Platform coverage reference”The inherited end-to-end test matrix covered:
- FreeBSD;
- Linux;
- Windows on AMD64;
- macOS on Apple silicon.
Historical documentation also identified Windows on ARM as a future coverage area. Current production support should be confirmed against the ZebraByte Device Agent release made available through ZebraByte Cloud rather than inferred solely from this lineage note.