Connect read-only
An organization owner in GitHub Enterprise Cloud will authorize read-only access. Organization OAuth restrictions and SSO policy may require separate approval. Flare verifies the organization name and immutable ID.
Organization security activity
GitHub audit log monitoring for organization security
Coming to Flare: on-demand review of GitHub Enterprise Cloud membership, repository-setting and permission changes, with ranked findings and selected audit-log evidence.
Coming soon. GitHub audit log connections are not available yet.
Planned coverage
What to expect from GitHub Enterprise Cloud audit analysis
Planned coverage includes organization web audit events from GitHub Enterprise Cloud. Git operations, repository contents, personal security logs, enterprise-wide audit streams and GitHub Enterprise Server are excluded. This is separate from Flare’s available GitHub Actions integrations.
Review ranked findings
Flare assesses current-window evidence with available historical context, then ranks noteworthy activity by severity and explains why it matters.
Investigate the evidence
See which streams were fetched, any truncation and selected event excerpts. Ask follow-up questions against the retained result. Findings are investigative leads, not proof that all activity is safe.
Built for small teams
Useful audit-log answers without a SIEM project
Bounded access and retention
Flare uses read-only access and retains analysis results with selected supporting evidence—not a complete copy of your logs.
How to investigate GitHub organization audit logs →Review GitHub Enterprise Cloud access requirements →Using another source?
Explore Google Workspace audit coverage, access requirements and availability.
Explore Google Workspace anomaly detection →Coming soon
Start with an available source.
GitHub audit logs are on the way. You can analyze Google Cloud, AWS and Google Workspace audit activity today. Existing GitHub Actions integrations remain available.
Explore available sources