GitHub
Bring in your GitHub organization's audit log or, without Enterprise, its security alerts.
It reads the organization's audit log (GitHub Enterprise Cloud). Without Enterprise, it reads the secret scanning, Dependabot and code scanning alerts.
Before you start
Administer permission on Security (SIEM).
A GitHub token with
read:audit_log(Enterprise) orsecurity_events. On github.com: your photo → Settings → Developer settings → Personal access tokens → Tokens (classic) → Generate new token. Copy it: GitHub won't show it again. The integration page repeats these steps.
Steps
Go to Settings → SIEM integrations → GitHub. The page shows what is read, the connection or token, and the minimum permission.
Click Add.
Type the Name, paste the Token and type the Organization. The token is stored in the vault and won't be shown again; when editing, leave it blank to keep it.
Click Add.
On the integration's card, click Test.
Manage the integration
Each integration has its card with the status (Waiting for the first read, Reading, With errors with the reason, or Paused), the connection, what it reads, the last read, the last event and the events brought in.
Test: authenticates and reads the last hour without storing anything. If a permission is missing, the error says which one.
Read now: reads without waiting for the next pass.
Pause or Enable.
Edit (pencil) and Delete (trash). When you delete it, ARGUNIS stops reading; the events already brought in stay in the SIEM with their retention.
What happens next
ARGUNIS reads every 5 minutes; the first time it brings in the last 24 hours. Events arrive in Security → Explore events and in the SIEM rules as one more source, which is included when the integration is created. ARGUNIS only reads: it changes nothing in your account.