Choose a setup path
AWS via EventBridge and SNS
The complete setup. Forward CloudTrail management events, GuardDuty findings, and Amazon Inspector vulnerability findings to Clarion in real time through EventBridge and SNS, wire up CloudWatch alarms, and create the IAM role for agent tools.
CloudTrail via existing S3 bucket
Already logging CloudTrail to S3 (or using a tool like Red Canary)? Have Clarion read each new log file from the bucket via an S3 event notification. Ideal for organization-wide, centralized logging.
How AWS data reaches Clarion
Every path delivers events to Clarion through an SNS topic that publishes to a Clarion webhook URL over HTTPS. They differ in how events get into that topic:Clarion only accepts SNS messages from topic ARNs you have saved on the matching monitor. Whichever path you choose, copy the exact SNS topic ARN into Clarion before confirming the subscription.
Detect
When Detect is enabled for your workspace, the CloudTrail events your CloudTrail monitors receive, by either path, can be queried with KQL as thecloudtrail table and are read by your CloudTrail detectors. A detector judges each window at least 20 minutes after it ends, since CloudTrail can deliver events up to 15 minutes late. Its findings open issues on your workspace’s Detect monitors, through their CloudTrail detection rule; attach the agents that should triage them to a Detect monitor. This needs no AWS setup or permission beyond what the monitor already uses. Read-only KMS calls that AWS services make on their own behalf are dropped on arrival, so they never reach Detect.