Connect pg-aiguide to ECA
Give ECA governed access to pg-aiguide through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add pg-aiguide to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve pg-aiguide in Runlayer
Add pg-aiguide from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches pg-aiguide’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to pg-aiguide
Sign in the way pg-aiguide requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use pg-aiguide from ECA
pg-aiguide’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
pg-aiguide tools in ECA
pg-aiguide reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every pg-aiguide call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more