Linux is reached over SSH. Windows is reached over WinRM. A network device is reached with Netmiko, or checked from an uploaded configuration without a live session. Ansible playbooks cover Linux, Windows, and network platforms.
05
Managed targets
AgentlessA target is a system under review. The platform connects for the job. It does not install an agent.
Agentless SSH, WinRM, Ansible, and Netmiko reach Linux, Windows, and network devices. Credentials stay encrypted.
Where it sits in the stack
- 01 Access layer
- 02 Control plane
- 03 Data and messaging
- 04 Execution layer
- 05Managed targets Focus
SSHWinRMAnsiblePythonSNMP
How requests move
- 01
A job selects hosts or a discovered range
- 02
The worker decrypts the matching credential
- 03
The worker connects, or reads an uploaded configuration
- 04
Evidence returns without an agent on the target
What this layer does
-
Agentless SSH, WinRM, Ansible, and Netmiko
-
An offline check from an uploaded device configuration
-
Inventory from nmap, SNMP, or an AD or LDAP import
-
Encrypted credentials, with SSH host-key and WinRM certificate checks
Inventory comes from an nmap or SNMP scan, from an AD or LDAP import, or from a host added by hand. A single IPv6 address is a valid target. An IPv6 prefix is not.
A credential is encrypted with Fernet, Vault Transit, or AWS KMS. The API does not return the secret. In production, SSH checks the host key and WinRM checks the server certificate. Access to the credential follows the same object ownership as the host.