What Neo can do with Airlock Digital
Agents and policy groups
Read each computer’s agent status, last check-in and policy group, and move computers between policy groups.
Blocked files
Read what was blocked or audited, on which computer, for which user, and the file’s hash, publisher and reputation.
OTP codes
Read OTP history and what ran under a code, revoke a code, and issue one after a technician approves it.
Allow or block a file
Add a file’s hash to an allowlist or a blocklist, or remove it. Under the Helpdesk and IT Admin profiles, allowlisting waits on a technician.
Exception requests
Read the requests users raise from a blocked computer, and approve or deny them.
Policies
Read and change exclusions, trusted publishers and policy settings, with the access you choose.
One connection per client
An Airlock server’s records name no client: the server is the client. You connect each client’s server under that client on your Companies tab, and an agent working a ticket reaches only the server of the ticket’s client. A server that protects several of your clients is connected under one of them, and every call on it reaches all of it. There is no Organization Mapping tab for Airlock Digital.What Neo never does
- Read or replace an Airlock account’s API key.
- Download the enforcement agent installer, or its configuration file, which carries the agent’s TLS private key.
- Replace every setting of a policy group at once.
- Give an OTP code to a sandbox script.
Next steps
Connect Airlock Digital
Make an Airlock user for Neo, publish the REST API, and save it in Neo under the client.