What Neo can do with Field Effect
- Find the ARO behind a ticket, and add its type, severity, details and mitigation steps to the ticket
- Read the endpoint the ARO names: its risk level, its antivirus status, and any active response action Field Effect took, such as an isolation
- Comment on an ARO, and resolve it in Field Effect when the ticket is done
- Ask Field Effect’s analysts for help on an ARO (Help Requested), for example to isolate an endpoint
- Dismiss an ARO, in its own permission group: off in Read Only and Helpdesk, after a technician’s approval in IT Admin, and without approval in Full Automation
- Read your client organizations, their service tier and active response policy, and who Field Effect calls when it escalates
Resolve or dismiss
Field Effect treats the two differently. Resolved means the issue is fixed, and Field Effect keeps monitoring and raises a new ARO if it recurs. Dismissed means a false positive or an accepted risk, and can stop Field Effect raising AROs of that kind. So dismissals have their own permission group, ARO Dismissal: it is off in Read Only and Helpdesk, and asks a technician in IT Admin.Your organizations are mapped to companies
Neo matches your Field Effect organizations to the companies in your PSA and keeps the mapping on the Field Effect card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the organization name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail. A name match, or one you confirm, is handed straight to your agents. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. See Field Effect API for the permission groups.Next steps
Connect Field Effect
Create an API key and save it in Neo.