SIEM sources
Review where security events come from, decide which discovered sources are included or ignored, and detect those that stopped sending.
A source is an origin of events: a stream from a ARGUNIS agent (including its web logs), a SOC integration, a syslog received by a probe (for example from a firewall), a cloud, or the ARGUNIS audit log itself. Sources appear automatically when they start sending events. Those from a cloud or service integration (Microsoft 365, AWS, Google Cloud, GitHub, Docker Hub, or Railway) are Included when the integration is created.
Before you start
View permission in Security (SIEM) to review; Administer to include or ignore.
Steps
Go to Security (SIEM) → Sources → SIEM sources.
Review Today's usage: events against the quota, dropped events, and events from discovered sources that weren't stored.
Review the indicators: Sources, Included, Discovered, Silent, and Ignored.
In the table, for each new source, click Sample to see a few example lines (redacted).
Decide:
Include: its events are stored and run through the rules.
Ignore: its events are neither stored nor counted.
Source statuses
Status | What it means |
|---|---|
Discovered | It arrived for the first time. It's counted, but not stored until you include it |
Included | It's stored, searchable, and runs through the rules |
Ignored | It's neither stored nor counted |
The Health column tells you whether the source is Receiving events, No events, Pending decision, or Silent. A silent source was sending and stopped: check the agent or the integration.
Watch the Unmapped column: a high percentage means many fields from that source couldn't be mapped to the common format. They're still stored and shown in the event details, but you can't search by those fields.
What happens next
Included sources add to Sources included in the Summary and in the evidence report. Each status change is recorded with who made it and when.