GET /api/runtime-security/events with an API key
that has the Read endpoint events permission, filtered by verdict and date.
What is sent
Each message says what happened and where: the time, the workspace, the device, the person, the AI service, the verdict, the detection categories, the reason code and the severity. How the device and the person are named follows your workspace’s identity setting:
The setting in force when a message is sent decides how it names people. This
includes a message that was waiting to be retried when the setting changed.
What was typed is off by default
By default, no prompt, excerpt, file content or topic wording leaves Blindsight in a syslog message. To send the text, turn on Include what was typed for a destination. This needs the Send prompt text to a SIEM permission, which administrators have, and a destination that uses TLS. Each blocked, redacted or flagged prompt then carries its text, exactly as the console shows it.- Only what your policy redacts is removed. A redacted prompt arrives with those values replaced. On a blocked or flagged prompt, values your policy does not redact, such as names, companies and addresses, can still be readable. The original text, as the device sent it before redaction, is never sent.
- Pseudonymized workspaces stay pseudonymized. Email addresses, device names, account names and the names of people in the workspace are replaced in the text by the same codes the console shows.
- Counts only sends no text. Single prompts are not sent at all. If the setting was on, it stays on but paused, and resumes when the workspace names people again.
- The text is read when the message is sent. A prompt deleted by retention or an erasure request before then is sent without text.
- A long prompt is shortened to fit a collector’s line, and marked as shortened.
Before you start
1
Have a collector on a public address
You need a syslog collector your SIEM reads from, reachable from the internet.
TLS on port
6514 is recommended.2
Allow the Blindsight address
Allow this address in the collector’s firewall:
If the address changes, you are told in advance. A self-hosted installation
connects from its own network.
3
Have your CA certificate ready
If the collector’s TLS certificate is signed by a private certificate authority,
have that CA certificate ready in PEM form.
Set up a destination
You need the Manage alerts permission, which administrators have.1
Open Alerts
Go to Endpoint → Configurations → Alerts and select Send to a SIEM.
2
Where is your collector?
Enter a name, the collector’s host name and port, and the transport. Paste your
CA certificate if it is a private one. Select Next.
3
What should it receive?
Choose the format and tick what to send:
- Blocked, redacted and flagged prompts
- Policy changes
- Device protection lost, and device protection resumed
4
Test it, then start
Select Send test event. The result appears on the spot: delivered, or the
reason it was not, such as a refused connection, no answer, an untrusted
certificate or no TLS on that port. Then select Start sending.
Delivery health
The destination’s row shows its health: when it last delivered, the last error, and how many events were dropped, if any. Messages are sent in the background, never on the path that inspects prompts. A slow or unreachable collector does not slow anyone down. A failed send is retried several times over the following hours. The first message given up during an outage is written to the audit trail. During a long outage, a destination drops new messages instead of building an endless backlog, and counts what it dropped on the destination’s row. Delivery is at least once, so a message can arrive twice after a retry. Every message carries a delivery ID that you can use to remove duplicates.Transports
TLS is version 1.2 or later. The collector’s certificate and its host name are
always verified, and verification cannot be turned off. Messages are framed one per
line (RFC 6587, non-transparent framing), which every common collector accepts on
TCP and TLS.
Formats
All four formats carry the same facts. Choose the one your SIEM parses best. Every message starts with an RFC 5424 header:PRIis the facility (16,local0, by default) times 8, plus the syslog severity: 6 for low, 4 for medium, 3 for high and 2 for critical.TIMESTAMPis when the message was sent, in UTC. The event’s own time is in the fields.MSGIDis the event family for both RFC 5424 forms and JSON, and-for CEF.
Event families
- CEF
- RFC 5424 (key=value)
- RFC 5424 (structured data)
- JSON
Recommended for Splunk, Microsoft Sentinel, IBM QRadar and ArcSight. The CEF
record is the syslog message.
Values are escaped as the CEF specification requires (
\=, \\, and line
breaks as \n), so any text in a value reads back exactly.Field reference for RFC 5424 and JSON
The same names are used in the key=value form, as structured data parameters and as JSON keys.SIEM examples
Splunk
Splunk
With Splunk Connect for Syslog (SC4S), listen with TLS on Without SC4S, a TCP or TLS data input with source type
6514 and choose
CEF in Blindsight. SC4S recognizes the records by their vendor and product.syslog also works. With
JSON chosen, use | spath input=message, or extract the JSON after the
header, to read the fields.Microsoft Sentinel
Microsoft Sentinel
Use the Common Event Format (CEF) via AMA data connector with a Linux log
forwarder, and choose CEF in Blindsight. Events land in the
CommonSecurityLog table.DeviceCustomString2 is the workspace and FlexString1 holds the detection
categories.IBM QRadar
IBM QRadar
Add a log source with these settings:
- Log source type: Universal CEF
- Protocol: TLS Syslog on port
6514, or Syslog - Log source identifier:
blindsight
endpoint_block, endpoint_redact and
endpoint_flag to QRadar events in the Universal CEF event mapping, so you can
use them in rules and offenses.Troubleshooting
Nothing arrives
Nothing arrives
Send a test event from the destination’s dialog. It names the problem. A
refused connection is usually the port or the transport. No answer is usually a
firewall that does not allow
34.246.156.194. An untrusted certificate needs the
CA certificate added to the destination.The test arrives but no events do
The test arrives but no events do
Check under Rules that the rules for this destination are on. Check that
your workspace does not show counts only, because single prompts are not sent
then.
You want the prompt text in the SIEM
You want the prompt text in the SIEM
Edit the destination, tick Include what was typed on the second step, and
save. Messages sent from then on carry the text.
You changed the collector
You changed the collector
Edit the destination and send a test event before you save.

