HTTP requests
Overview
Cloudflare is a global network designed to make everything you connect to the Internet secure, private, fast, and reliable.
In this documentation, you will learn how to collect and send Cloudflare HTTP requests to Sekoia.io.
Related Built-in Rules
Benefit from SEKOIA.IO built-in rules and upgrade Cloudflare HTTP requests with the following detection capabilities out-of-the-box.
SEKOIA.IO x Cloudflare HTTP requests on ATT&CK Navigator
Nimbo-C2 User Agent
Nimbo-C2 Uses an unusual User-Agent format in its implants.
- Effort: intermediate
Potential Azure AD Phishing Page (Adversary-in-the-Middle)
Detects an HTTP request to an URL typical of the Azure AD authentication flow, but towards a domain that is not one the legitimate Microsoft domains used for Azure AD authentication.
- Effort: intermediate
Potential Bazar Loader User-Agents
Detects potential Bazar loader communications through the user-agent
- Effort: elementary
Potential Lemon Duck User-Agent
Detects LemonDuck user agent. The format used two sets of alphabetical characters separated by dashes, for example "User-Agent: Lemon-Duck-[A-Z]-[A-Z]".
- Effort: elementary
SEKOIA.IO Intelligence Feed
Detect threats based on indicators of compromise (IOCs) collected by SEKOIA's Threat and Detection Research team.
- Effort: elementary
Event Categories
The following table lists the data source offered by this integration.
Data Source | Description |
---|---|
Web logs |
Cloudflare act as a proxy and provide associated traffic logs |
Web application firewall logs |
Cloudflare protect web application with its web application firewall and provide associated traffic logs |
In details, the following table denotes the type of events produced by this integration.
Name | Values |
---|---|
Kind | event |
Category | web |
Type | access |
Event Samples
Find below few samples of events and how they are normalized by Sekoia.io.
{
"message": "{\"ClientIP\":\"34.142.121.18\",\"ClientRequestHost\":\"foo-bar-baz.xyz\",\"ClientRequestMethod\":\"GET\",\"ClientRequestURI\":\"/wp1/wp-includes/wlwmanifest.xml\",\"EdgeEndTimestamp\":1658281702371000000,\"EdgeResponseBytes\":279,\"EdgeResponseStatus\":522,\"EdgeStartTimestamp\":1658281671671000000,\"RayID\":\"72d807ffeba5753d\"}",
"event": {
"kind": "event",
"category": [
"web"
],
"type": [
"access"
],
"dataset": "http_requests",
"start": "2022-07-20T01:47:51.671000Z",
"end": "2022-07-20T01:48:22.371000Z"
},
"source": {
"ip": "34.142.121.18",
"address": "34.142.121.18"
},
"destination": {
"address": "foo-bar-baz.xyz"
},
"http": {
"request": {
"method": "GET"
},
"response": {
"bytes": 279,
"status_code": 522
}
},
"url": {
"path": "/wp1/wp-includes/wlwmanifest.xml"
},
"observer": {
"vendor": "Cloudflare",
"type": "proxy"
},
"cloudflare": {
"ClientIP": "34.142.121.18",
"ClientRequestHost": "foo-bar-baz.xyz",
"ClientRequestMethod": "GET",
"ClientRequestURI": "/wp1/wp-includes/wlwmanifest.xml",
"EdgeEndTimestamp": "1658281702371000000",
"EdgeResponseBytes": 279,
"EdgeResponseStatus": 522,
"EdgeStartTimestamp": "1658281671671000000",
"RayID": "72d807ffeba5753d"
},
"related": {
"ip": [
"34.142.121.18"
]
}
}
{
"message": "{\"WAFMatchedVar\":\"\",\"WAFProfile\":\"unknown\",\"WAFRuleID\":\"\",\"WAFRuleMessage\":\"\",\"WorkerCPUTime\":0,\"WorkerStatus\":\"unknown\",\"WorkerSubrequest\":false,\"WorkerSubrequestCount\":0,\"ZoneID\":545468107,\"ZoneName\":\"foo-bar-baz.xyz\"}\n\n",
"event": {
"kind": "event",
"category": [
"web"
],
"type": [
"access"
],
"dataset": "http_requests"
},
"observer": {
"vendor": "Cloudflare",
"type": "proxy"
},
"cloudflare": {
"WAFMatchedVar": "",
"WAFProfile": "unknown",
"WAFRuleID": "",
"WAFRuleMessage": "",
"WorkerCPUTime": 0,
"WorkerStatus": "unknown",
"WorkerSubrequest": false,
"WorkerSubrequestCount": 0,
"ZoneID": 545468107,
"ZoneName": "foo-bar-baz.xyz"
}
}
Extracted Fields
The following table lists the fields that are extracted, normalized under the ECS format, analyzed and indexed by the parser. It should be noted that infered fields are not listed.
Name | Type | Description |
---|---|---|
@timestamp |
date |
Date/time when the event originated. |
destination.address |
keyword |
Destination network address. |
event.action |
keyword |
The action captured by the event. |
event.category |
keyword |
Event category. The second categorization field in the hierarchy. |
event.dataset |
keyword |
Name of the dataset. |
event.end |
date |
event.end contains the date when the event ended or when the activity was last observed. |
event.kind |
keyword |
The kind of the event. The highest categorization field in the hierarchy. |
event.start |
date |
event.start contains the date when the event started or when the activity was first observed. |
event.type |
keyword |
Event type. The third categorization field in the hierarchy. |
http.request.bytes |
long |
Total size in bytes of the request (body and headers). |
http.request.method |
keyword |
HTTP request method. |
http.request.referrer |
keyword |
Referrer for this HTTP request. |
http.response.bytes |
long |
Total size in bytes of the response (body and headers). |
http.response.status_code |
long |
HTTP response status code. |
network.protocol |
keyword |
Application protocol name. |
observer.type |
keyword |
The type of the observer the data is coming from. |
observer.vendor |
keyword |
Vendor name of the observer. |
rule.id |
keyword |
Rule ID |
rule.ruleset |
keyword |
Rule ruleset |
source.as.number |
long |
Unique number allocated to the autonomous system. |
source.geo.country_name |
keyword |
Country name. |
source.ip |
ip |
IP address of the source. |
source.port |
long |
Port of the source. |
tls.cipher |
keyword |
String indicating the cipher used during the current connection. |
tls.version_protocol |
keyword |
Normalized lowercase protocol name parsed from original string. |
url.path |
wildcard |
Path of the request, such as "/search". |
user_agent.original |
keyword |
Unparsed user_agent string. |
Configure
Create the intake on Sekoia.io
Go to the intake page and create a new intake from the format Cloudflare.
Configure events forwarding on Cloudflare
Retrieve necessary information
First, you will have to retrieve configuration information. Connect to Cloudflare Console to collect the following :
-
Cloudflare API Token
- Go to
My Profile
, then on the left panel, click onAPI Tokens
. - Click on the
Create Token
button and select theCreate Custom Token
entry. - Give a name to your token and set the following permissions:
Scope Group Level Account Account Analytics Read Account Logs Read Account Logs Edit Zone Logs Read Zone Logs Edit - If you want zerotrust logs you should also add:
Scope Group Level Account Zero Trust Read - Go to
-
Cloudflare Zone ID :
- This information is specific to a Website.
- On the left panel, click on
Websites
and select the Website you want. - On the right panel, there is an
API
section where you can retrieve theZone ID
.
Create a Logpush job
Configure a Logpush job with the following destination:
https://intake.sekoia.io/plain/batch?header_X-SEKOIAIO-INTAKE-KEY=<YOUR_INTAKE_KEY>
To do so, you can manage Logpush with cURL:
$ curl -X POST https://api.cloudflare.com/client/v4/zones/<CLOUDFLARE_ZONE_ID>/logpush/jobs \
-H "Authorization: Bearer <CLOUDFLARE_API_TOKEN>" \
-H "Content-Type: application/json" \
--data '{
"dataset": "http_requests",
"enabled": true,
"max_upload_bytes": 5000000,
"max_upload_records": 1000,
"logpull_options":"fields=ClientIP,ClientRequestHost,ClientRequestMethod,ClientRequestURI,EdgeEndTimestamp,EdgeResponseBytes,EdgeResponseStatus,EdgeStartTimestamp,RayID×tamps=unix",
"destination_conf": "https://intake.sekoia.io/plain/batch?header_X-SEKOIAIO-INTAKE-KEY=<YOUR_INTAKE_KEY>"
}' # (1)
- will return
{ "errors": [], "messages": [], "result": { "id": 146, "dataset": "http_requests", "enabled": false, "name": "<DOMAIN_NAME>", "logpull_options": "fields=<LIST_OF_FIELDS>×tamps=rfc3339", "destination_conf": "https://intake.sekoia.io/plain/batch?header_X-SEKOIAIO-INTAKE-KEY=<YOUR_INTAKE_KEY>", "last_complete": null, "last_error": null, "error_message": null }, "success": true }
Important
Replace :
<YOUR_INTAKE_KEY>
with the Intake key you generated in the Create the intake on Sekoia.io step.<CLOUDFLARE_API_TOKEN>
with the API Token you generated<CLOUDFLARE_ZONE_ID>
with the Zone ID you grabbed
Useful Cloudflare API endpoints
On their documentation, Cloudflare provides a list API endpoints you can use. Find below some useful endpoints:
https://api.cloudflare.com/client/v4/zones/<ZONE_ID>/logpush/jobs/<JOB_ID>
to verify the job you previously created is correct (you need to specify theJOB_ID
)https://api.cloudflare.com/client/v4/zones/<ZONE_ID>/logpush/datasets/<DATASET>/jobs
to get all the jobs for a specific dataset (dns_log
,firewalls_events
orhttp_requests
in our case)https://api.cloudflare.com/client/v4/zones/<ZONE_ID>/logpush/jobs/<JOB_ID>
to update a job if you noticed a mistake after the creation of the job (wrong fields, wrong SEKOIA API Key...)