Skip to content
05

Managed targets

Agentless

Managed targets are the systems under review — reached agentlessly over SSH, WinRM, and network protocols without installing a fleet agent.

Agentless SSH, WinRM, and network protocols connect to Linux, Windows, and network devices

Where it sits in the stack

  1. 01
    Access layer
  2. 02
    Control plane
  3. 03
    Data and messaging
  4. 04
    Execution layer
  5. 05
    Managed targets Focus
SSHWinRMNetworkLinuxWindows

How requests move

  1. 01

    Job selects hosts or a discovered range

  2. 02

    Matching credential set is resolved

  3. 03

    Worker connects over SSH, WinRM, or network protocol

  4. 04

    Evidence returns without a resident agent

What this layer does

  • Agentless SSH for Linux and Unix-like systems

  • WinRM paths for Windows workstations and servers

  • Network protocol checks for switches, routers, and firewalls

  • Credential binding with encrypted storage and RBAC scope

Linux hosts are assessed over SSH, Windows endpoints over WinRM, and network devices through protocol-aware connectors that fit inventory tags and credentials.

Because the model is agentless, onboarding a CIDR or host list does not require packaging, push agents, or long change windows.

Credentials stay encrypted in the platform and are bound to objects through RBAC, so target access remains auditable and scoped.

Other layers

Back to Technology
01

Access layer

Operators work in a single PatternFly interface with Keycloak OIDC or local authentication and object-level RBAC

 02

Control plane

FastAPI provides REST and WebSocket APIs. secaudit_core manages profiles, AuditFlow, jobs, and reports

 03

Data and messaging

PostgreSQL stores platform state. Redis Sentinel provides highly available queues, distributed locks, and scheduling

 04

Execution layer

Celery workers execute checks, remediation jobs, discovery scans, and scheduled tasks while streaming logs in real time