Google Chronicle
Detections from Chronicle’s rule engine, normalised alongside every other source so one incident view spans your whole estate.
What CMDash reads
- Incidents & alerts
Syncs only read from Google Chronicle. Some integrations also support write-back actions on Command and Enterprise plans, such as opening a ticket or deactivating a user.
How you connect
An API key or token you create in the vendor console and enter in CMDash.
Once connected, CMDash syncs it every 4 hours by default. What it finds maps to your controls through rules you install or write.
Where this fits in your frameworks
- NIST Cybersecurity Framework (1.1, legacy) — Incidents & alerts feeds Detect (DE)
- TISAX (VDA ISA v6) — Incidents & alerts feeds IT Security
This is where Google Chronicle’s data is documented as relevant on our framework pages — not a pre-built, automatic control mapping. You configure which controls it maps to inside CMDash.
Also in SIEM & Detection
Ready to see your posture?
Start a 30-day free trial of any paid plan — a card is required, and it converts unless you cancel — or sign up for Free with no card at all.