Connect Scanner to GitHub Copilot
Give GitHub Copilot governed access to Scanner’s 3 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Scanner to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Scanner in Runlayer
Add Scanner from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
Install the Runlayer CLI so GitHub Copilot can reach Scanner, which runs on the user’s machine.
GitHub Copilot setup guide - 3
Sign in to Scanner
An admin adds Scanner credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Scanner from GitHub Copilot
Scanner’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
3 Scanner tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call. 3 read data only.
Get Scanner context
Get context about available Scanner indexes and data sources for investigation
Execute query
Execute a search query against Scanner security data lake indexes
Fetch query results
Fetch results from a previously executed Scanner query
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every Scanner call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more