Trellix ePO
Collect managed-system and policy-assignment inventory as read-only endpoint-security compliance evidence through the Trellix (McAfee) ePolicy Orchestrator remote API (self-hosted). ePO's remote commands return plain text by convention; append `?:output=json` to request JSON where supported by the deployment.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Read-only API inventory endpoint checks
- Evidence assets generated through the generic HTTP connector
Endpoints this template queries
The exact Trellix ePO API endpoints called once connected. All read-only GET requests unless noted.
- GET/system.find?searchText=&:output=json
- GET/policy.find?:output=json
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://<your-epo-host>:8443/remote)
- Endpoints (JSON)(prefilled: [ { "id": "system-find", "name": "Managed systems", "path": "/system.find?searchText=&:output=json" }, { "id": "policy-find", "name": "Policy assignments", "path": "/policy.find?:output=json" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Trellix ePO evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Trellix ePO evidence
Get a guided demo, or start by scanning any domain for free.