McAfee (Trellix) · Authentication Profile

Mcafee Authentication

Authentication

McAfee (Trellix) secures its APIs with apiKey and http across 4 declared security schemes, as derived from its OpenAPI definitions.

AntivirusCybersecurityEndpoint ProtectionSecurityThreat Intelligence
Methods: apiKey, http Schemes: 4 OAuth flows: API key in: cookie

Security Schemes

basicAuth http
scheme: basic
sessionAuth apiKey
· in: cookie (JWTToken)
bearerAuth http
scheme: bearer
cookieAuth apiKey
· in: cookie (JSESSIONID)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/mcafee-epo-openapi.yml, openapi/mcafee-esm-openapi.yml, openapi/mcafee-mvision-openapi.yml,
  openapi/mcafee-web-gateway-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - cookie
schemes:
- name: basicAuth
  type: http
  scheme: basic
  description: HTTP Basic authentication using ePO administrator credentials. Credentials are
    transmitted as a Base64-encoded username:password pair.
  sources:
  - openapi/mcafee-epo-openapi.yml
- name: sessionAuth
  type: apiKey
  in: cookie
  parameter: JWTToken
  description: Session token obtained from the login endpoint
  sources:
  - openapi/mcafee-esm-openapi.yml
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: OAuth 2.0 bearer token from client credentials grant
  sources:
  - openapi/mcafee-mvision-openapi.yml
- name: cookieAuth
  type: apiKey
  in: cookie
  parameter: JSESSIONID
  description: Session cookie obtained from the login endpoint
  sources:
  - openapi/mcafee-web-gateway-openapi.yml