Insider threat hunting
How an AI SOC hunts insider risk: compare downloads and repository clones with each user's baseline, add role context, and hand a dossier to the review board.
The short answer
Insider threat hunting looks for people misusing access they already have, such as bulk downloads from document stores or code repositories. Cotool's example Insider Risk Responder starts from Jira security issues and attaches a dossier for the review board.[1]
The problem
How an AI SOC handles it
Add context
The agent checks the person's role and dates, such as whether a contractor's downloads came just before the engagement ended.[1]
Example
Hypothesis: a stolen GitHub token is used to clone private repositories
from an unmanaged device.
1. Pull the GitHub audit log for 14 days (queried via API, not centralized)
2. Join Okta sessions and device posture (Cotool logs)
3. Flag clone bursts from unmanaged devices
Detection generated: Mass repo clone from unmanaged device (T1213)The hunt shown on Cotool's Hunt page. When a hunt returns findings, the agent backtests and ships a detection so the pattern is covered next time.[4]
What people approve
How Cotool handles it
- Cotool threat models your environment, forms hypotheses about attacker behavior, and runs hunts continuously. A hunt with findings ends in a new detection.[4]
Integrations used
Sources
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Triggering agents (Cotool docs) · accessed November 16, 2026
- Changelog (Cotool docs) · accessed November 16, 2026
- Threat hunting (Cotool Hunt) · accessed November 16, 2026
- Jira integration (Cotool docs) · accessed November 16, 2026
- Alerts (Cotool docs) · accessed November 16, 2026
- Data from Information Repositories, T1213 (MITRE ATT&CK) · accessed November 16, 2026
- Reviewing the audit log for your organization (GitHub Docs) · accessed November 16, 2026



