CyberQP API

The CyberQP API tool gives Neo agents access to CyberQP (formerly Quickpass), your privileged access platform. The common uses are verifying a caller before a password reset, giving a technician temporary admin rights at a customer for one ticket, and handing the CyberQP install token and customer GUID to an RMM deployment script.

​

What It Does

• Find a customer in CyberQP, with its agent GUID, and read its user, admin, service and JIT accounts
• Send an end user an identity verification push; CyberQP adds the result to the PSA ticket
• Create a just-in-time (JIT) admin account under one of your JIT policies, enable it for a duration, disable it, or delete it
• Read a customer account’s or a JIT account’s password and a JIT account’s OTP codes, for a technician who asks
• Read the agent install token, so your RMM can deploy the CyberQP agent
• Read CyberQP’s audit events from the last three months

Neo never refreshes or revokes CyberQP tokens on request, never downloads the agent installer, and never saves an OTP secret on a JIT account: that secret would sit in the agent’s run log.

​

Permission Groups

​

Calls that always ask a technician

These calls wait for a technician’s approval under every profile, whatever you set on the group:

• Creating a JIT admin account, and enabling one
• Reading a customer account’s password, a JIT account’s password or a JIT account’s OTP codes
• Removing a JIT account’s OTP secret

Each gives a person admin rights at a customer, hands over a live credential, or weakens an account’s sign-in, so no setting runs them unattended. The agent sends the approval request with the customer, the account and the ticket. Turn Passwords & OTP on only for agents that hand credentials to your team, such as an internal chat agent.

​

Setup

See Connecting CyberQP to Neo.