Log streaming

How log streaming works, how to connect it, where we can send data, and in which format.

This feature is not available in the UI and is connected on request. It is available only in Anti-bot mode.

What this feature is

Log streaming sends protection logs to your infrastructure in real time.

How it works. For every request to your web resource, the system creates a log with 20 parameters. It immediately sends the log to the selected receiving endpoint, such as your Kafka cluster or rsyslog receiver.

Who it is useful for. It is useful for customers who want to store logs for a long time, upload them to a SIEM or other monitoring systems, combine them with logs from other sources, or create their own dashboards and alerts.

Key characteristics

  • Secure log transfer is supported with TLS and mTLS.

  • The feature is available only in Anti-bot mode. It is not available in Anti-DDoS mode.

  • This is streaming, not an archive export. Logs are sent in real time, and buffering is not supported. If a log is not delivered at the time of sending, it is not sent later.

Where and how we can send logs

We can send logs to the following receiving endpoints:

  • Kafka in JSON format.

  • An rsyslog receiver in syslog format. Supported protocols: UDP, TCP, TCP + TLS, and TCP + mTLS.

  • A non-standard receiving endpoint. On request, we can discuss a custom arrangement, such as sending logs to S3-compatible storage on your side.

We usually send logs over the public network. If our networks directly connect to yours, we can agree to send logs over that internal network connection rather than over the internet.

Log format

We can send logs in two formats: JSON and syslog. Examples are below.

JSON:
{
  "sid": 29201,
  "datetime": 1774275547619,
  "scheme": "https",
  "host": "example.com",
  "remote_addr": "203.0.113.42",
  "request": "POST /api/example-endpoint HTTP/2.0",
  "referrer": "https://example.com/",
  "user_agent": "ExampleApp|4.103.0|Android|16|Example Device",
  "cookie": "device_id=example-device-id; classification=human; theme=dark",
  "forwarded_for": "198.51.100.24",
  "uniq_id": "8Jd0WBgEkqM3",
  "score": "human",
  "action": "pass",
  "reason": "mobile_app",
  "profile_name": "example_profile",
  "type": "script",
  "ja3": "d06ad0468c9ca5743014ff08b66bfc83",
  "geo": "DE",
  "asn": 64500,
  "subnet": "203.0.113.0/24"
}
syslog:
<134> 2026-03-23T13:55:33Z cdm2 strictera-test[1748630]: 29201,1774275547619,https,example.com,203.0.113.42,POST /api/example-endpoint HTTP/2.0,https://example.com/,ExampleApp|4.103.0|Android|16|Example Device,device_id=example-device-id; classification=human; theme=dark,198.51.100.24,8Jd0WBgEkqM3,human,pass,mobile_app,example_profile,script,d06ad0468c9ca5743014ff08b66bfc83,DE,64500,203.0.113.0/24

These examples contain all possible log fields. When connecting the feature, you choose which fields to include in the export.

Field descriptions

Field Description JSON example syslog example

sid

The ID of the resource to which the request was sent.

"sid": 29201

29201

datetime

The exact time when protection received the request, as a Unix timestamp in milliseconds.

"datetime":
1774275547619

1774275547619

scheme

The URL scheme, or the protocol that the client used to access the resource.

Open the list of possible values

Https

Http

"scheme":
"https"

https

host

The hostname to which the request was sent.

"host":
"example.com"

example.com

remote_addr

The request source IP address.

"remote_addr":
"203.0.113.42"

203.0.113.42

request

The HTTP request start line: method, path, and HTTP version.

"request": "POST
/api/example-
endpoint HTTP/2.0"

POST /api/example-
endpoint HTTP/2.0

referrer

The value of the HTTP Referer header.

"referrer":
"https://example.com/"

https://example.com/

user_agent

The value of the HTTP User-Agent header.

"user_agent":
"ExampleApp|4.
103.0|Android|16
|Example Device"

ExampleApp|4.
103.0|Android|16
|Example Device

cookie

The value of the HTTP Cookie header.

"cookie":
"device_id=example-
device-id; classification=
human; theme=dark"

device_id=example-
device-id; classification=
human; theme=dark

forwarded_for

The value of the X-Forwarded-For header.

"forwarded_for":
"198.51.100.24"

198.51.100.24

uniq_id

A unique request ID assigned by the system.

"uniq_id": "8Jd0WBgEkqM3"

8Jd0WBgEkqM3

score

The class assigned to the request source after analysis.

Open the list of possible classes

Bot—bot.

Likely bot—most likely a bot.

Likely human—most likely a person.

Human—person.

"score": "human"

human

action

The action protection applied to the request.

Open the list of possible actions

Pass—passed.

Block—blocked.

CAPTCHA—the client received a CAPTCHA.

JS-challenge—the client received a JS challenge.

Cookie-challenge—the client received a cookie challenge.

Redirect—the client received a redirect.

"action": "pass"

pass

reason

Why protection applied the action.

Open the list of possible reasons

mobile_app—traffic classified as traffic from a legitimate mobile application.

local_white—a request from an IP address that you added to the white list.

user_blocked_by_score—analysis of the user’s actions and characteristics identified the user as not legitimate. The user’s requests are blocked starting with this one.

local_whdr—a request with an allowed HTTP header. Requests with this header are passed without checks.

protection_disabled—protection is disabled. This applies both when protection is disabled for the specific location that received the request and when it is disabled for the whole resource.

white—a request from an officially verified bot that performs a useful task on the internet, such as a search engine crawler or uptime monitoring service. Protection continuously checks and updates the list of such bots. Their requests are passed without checks by default.

conn_blocked_by_hosting—the subnet has a poor reputation and often sends bot requests.

local_whdrl—a request with an allowed HTTP header with limited trust. Protection passes such requests without checks until their number exceeds the set limit, for example 2,000 requests per minute. The filtering policy configured for your resource checks all requests above the limit.

conn_blocked_by_no_cookie—the request had to contain a Strictera cookie but did not.

user_blocked—the request came from a blocked user. The decision to block the user was made during one of their previous requests.

check_force—according to the current security policy, this request requires an additional challenge.

captcha_pass—the user completed a CAPTCHA successfully recently and confirmed that they are legitimate.

captcha_set_cookie_redirect—the user has already completed a CAPTCHA successfully. Strictera is now setting a cookie that lets the user access your resource without challenges for some time.

behavior_pass—behavioral analysis identified the user as legitimate.

user_blocked_by_behavior—behavioral analysis detected anomalous activity. The user’s requests are blocked starting with this one.

custom_white_bot—we allowlisted this type of traffic at your request.

set_cookie_redirect—a cookie is being set as part of a cookie challenge.

local_bgeo—the request came from a country that you blocked in Geo restrictions.

captcha_invalid—the user did not complete the CAPTCHA correctly.

invalid_uid—protection detected changes to the cookie, so the traffic is suspicious.

white_corp—the request came from a subnet that we allowlisted at your request.

user_blocked_by_no_correct_cookie—the user sent a request without the required cookie, which indicates that the user is not legitimate. The user’s requests are blocked starting with this one.

ip_blocked_by_spec—a per-IP rate limit was exceeded.

ip_blocked—this IP address recently sent suspicious requests and is temporarily blocked. To find out why it was first blocked, open the logs of previous requests from this IP address.

invalid_method—the client used an HTTP request method that is incompatible with the location that received the request.

local_black—the request came from an IP address that you added to the black list.

cookie_disabled—the client cannot set the required cookie.

user_blocked_by_spec—the user exceeded one of the rate limits set by the protection policy for your resource. The user’s requests are blocked starting with this one.

user_blocked_by_rate—the user exceeded the system rate limit for dynamic content. The user’s requests are blocked starting with this one.

"reason": "mobile_app"

mobile_app

profile_name

If a custom rule was applied to the request, this field contains its ID.

If no custom rule was applied, this field contains the name of the triggered profile. A profile is a set of filtering settings. It is an internal service variable: we group protection settings for your resource into separate profiles and assign names to them.

"profile_name":
"example_profile"

example_profile

type

The requested content type, either static or dynamic.

Open the list of possible values

script—a dynamic-content request sent to a non-AJAX location.

script_ajax—a dynamic-content request sent to an AJAX location.

static—a static-content request.

"type": "script"

script

ja3

The JA3 fingerprint hash.

"ja3": "d06ad0468c9ca
5743014ff08b66
bfc83"

d06ad0468c9ca5
743014ff08b66b
fc83

geo

The request source country identified from the IP address.

"geo": "DE"

DE

asn

The number of the autonomous system that owns the source IP address.

"asn": 64500

64500

subnet

The subnet that contains the source IP address.

"subnet": "203.0.113.0/24"

203.0.113.0/24

Connect log streaming

1. Contact support.

Tell support that you want to connect log streaming.

2. Send us connection details.

To write to Kafka, send us:

  • Broker addresses and ports.

  • The name of the topic to which logs must be written.

  • For a TLS connection, the CA certificate in PEM format that we use to connect to you.

  • For an mTLS connection, the CA certificate and certificate-key pair in PEM format that we use to connect to you.

  • If authorization is enabled, create an account for us and send its username and password.

If access to Kafka is limited by a firewall, ask support for the current Strictera IP addresses that you need to allow.

To write to rsyslog, send us:

  • The address.

  • The port.

  • The tag.

  • The protocol: TCP, UDP, TCP + TLS, or TCP + mTLS.

  • For TCP with TLS, the CA certificate in PEM format that we use to connect to you.

  • For TCP with mTLS, the CA certificate and certificate-key pair in PEM format that we use to connect to you.

We can also discuss custom options, such as exporting logs to S3-compatible storage. Contact support if this is relevant to you.

3. Send the list of fields you need.

Specify which fields you want to receive in the logs. See the complete list in Field descriptions above.

If storage space is important, we recommend excluding the cookie field unless you need it. It can increase the log volume unpredictably.

4. Wait for the configuration to be ready.

We need some time to configure log streaming. Configuration is performed during business hours. We will notify you as soon as it is ready.

5. Confirm that you want to connect the service.

After you confirm, we start sending logs.