Connect Grep to ECA
Give ECA governed access to Grep’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Grep to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Grep in Runlayer
Add Grep 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 Grep’s 1 tool through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Grep
Sign in the way Grep requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Grep from ECA
Grep’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
1 Grep tools in ECA
Runlayer policy decides which of these ECA users can call.
Search git hub
Find real-world code examples from over a million public GitHub repositories to help answer programming questions.
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 Grep 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