Skip to main content
The Avanan API tool gives Neo agents access to the Avanan Smart API (Check Point Harmony Email & Collaboration on the Avanan portal) for each of your client tenants. The common use is an “allowed list request” ticket: the agent finds the client’s tenant, checks the allow list, adds the sender or domain the ticket names, and notes the entry on the ticket.
Automatically enabled when you configure Avanan permissions in your agent workflow.

​
What It Does

  • Read a client’s anti-phishing allow list, spam allow list and block list
  • Add, change and remove an entry by sender address, domain, IP, subject, recipient, link domain or attachment hash
  • Search a client’s messages and Avanan’s security events, and read a message’s verdict
  • Quarantine or restore a message, and report a wrong verdict to Check Point
  • Manage the exceptions of the anti-malware, DLP, URL reputation, anomaly and click-time protection engines
  • Read your client tenants, their licenses, add-ons and usage, and your Avanan portal users

​
Client tenants

An MSP API key reaches every client tenant in its region. The agent names the client on each call by the tenant’s scope, such as mt-prod-3:contoso. Each tenant is mapped to a client in your PSA, so the agent knows which scope belongs to the ticket’s client: see Avanan overview. On a ticket, Neo checks the scope against that mapping before it sends the call. The agent can reach only the tenant mapped to the ticket’s client; Neo refuses any other scope, and a call without a scope, because that call would reach every client the key reaches. When the ticket’s client has no mapped tenant, the agent can reach no tenant on that ticket: map the client on the Avanan card’s Organization Mapping tab. Listing scopes and the MSP calls (tenants, licenses, usage, portal users) are refused on a ticket, because they name other clients. A mapping counts once it is a name match or one you confirmed. Runs with no ticket, such as a chat or a scheduled agent with no ticket, are not limited to one client.

​
Permission Groups

Each group is Disabled, Read Only or Read / Write.

​
Access Profiles

​
Safety Controls

​
How to Configure

1

Connect Avanan

Save your Smart API key’s region, Application ID and Client Secret in the Neo Dashboard under the Security integrations category. See Connecting Avanan to Neo.
2

Configure permissions

In your agent workflow’s Integrations tab, choose an access profile or set each permission group by hand.
For allowed list requests, IT Admin fits: blocks run on their own, and a technician approves each allow-list entry.