Reference
Compatibility and versions
A reference for checking connection paths, protocols, and release alignment.
Compatibility depends on checking the connection path, protocol, and deployment responsibilities together. This page defines the checks; it does not declare an unpublished version or an untested combination supported.
Check matrix
| Connection path | Example targets | Panel signal | Deployment verification |
|---|---|---|---|
| Windows Agent | Windows machine, RDP, or local-preparation resource | Agent version, last heartbeat, ready state | OS, service installation, HTTPS egress, and selected protocol |
| Gateway / private network | Linux, terminal, Kubernetes, or gateway-reached target | Gateway/reachability and resource readiness | Gateway path, target service, network policy, and credential preparation |
| Existing agentless reachability | Reachable RDP, SSH, VNC, or terminal target | Resource, assignment, session, and closure state | Target reachability, firewall/allowlist, and protocol configuration |
For each row, keep the release version, target protocol, deployment owner, and expected ready signal together. If those fields are missing, do not mark the combination as verified.
Check order
- Verify the product and Agent/gateway versions named by the deployment release notes.
- Check the connection path, protocol, and target operating system.
- Review Agent or gateway readiness, last-seen information, and the panel resource identity.
- Identify the owner of target networking and credential preparation; do not assume CerberusD performs it automatically.
- If they do not align, use the visible checks in connection troubleshooting.
This reference does not declare an unverified version or protocol supported. Do not infer compatibility where the deployment source does not provide it.