Skip to main content
The common use is a ticket from a user DefensX blocked: the agent finds the site the user asked for, checks it in the client’s logs, adds it to the client’s allow list once that is allowed, and closes the ticket.
Automatically enabled when you configure DefensX permissions in your agent workflow.

What It Does

  • Read a user’s request for a blocked site from its ticket, and find what was blocked in the client’s URL and DNS logs
  • Add sites to a client’s allow and block lists (custom URL groups) and remove them, create and delete lists
  • Read a client’s policy groups, link a list to a policy, and create, change or delete policies
  • Read URL, DNS, credential, file transfer, consent and isolation logs, top blocked sites and categories, and the cyber resilience score
  • Read a client’s users, groups, installed agents, deployments and browser extensions
  • Read your DefensX customers and usage, and create a customer

Permission Groups

Neo always asks a technician before a policy change that turns a filter off, or that changes which lists a policy uses, whatever the group’s approval setting. On a ticket, the agent works only on the DefensX customer mapped to the ticket’s company.

Setup

See Connecting DefensX to Neo.