New

The executive guide to generative AI

Read more

Check Point Integration

edit

Check Point Integration

edit

Version

1.34.4 (View all)

Compatible Kibana version(s)

8.11.0 or higher

Supported Serverless project types
What’s this?

Security
Observability

Subscription level
What’s this?

Basic

Level of support
What’s this?

Elastic

The Check Point integration allows you to monitor Check Point Firewall logs from appliances running Check Point Management.

Use the Check Point integration to collect and parse firewall event logs. Then visualize that data in Kibana, create alerts to notify you if something goes wrong, and reference the firewall data stream when troubleshooting an issue.

For example, you could use the data from this integration to spot unusual network activity and malicious traffic on your network. You could also use the data to review or troubleshoot the rules that have been set up to block these activities. You can do this by looking at additional context in the logs, such as the source of the requests, and more.

Data streams

edit

The Check Point integration collects one type of data: logs.

Logs help you keep a record of events logged by your firewall device. Logs collected by the Check Point integration include all logged network events specified by the firewall’s rules. See more details in the Logs reference.

Requirements

edit

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

You will need one or more Check Point Firewall appliances to monitor.

Compatibility

edit

This integration has been tested against Check Point Log Exporter on R81.X.

Setup

edit

For step-by-step instructions on how to set up an integration, see the Getting started guide.

In some instances firewall events may have the same Checkpoint loguid and arrive during the same timestamp resulting in a fingerprint collision. To avoid this enable semi-unified logging in the Checkpoint dashboard.

TCP or UDP

edit

Elastic Agent can receive log messages directly via TCP or UDP syslog messages. The Elastic Agent will be used to receive syslog data from your Check Point firewalls and ship the events to Elasticsearch.

  1. For each firewall device you wish to monitor, create a new Log Exporter/SIEM object in Check Point SmartConsole. Set the target server and target port to the Elastic Agent IP address and port number. Set the protocol to UDP or TCP, the Check Point integration supports both. Set the format to syslog.
  2. Configure the Management Server or Dedicated Log Server object in SmartConsole.
  3. Install the database within SmartConsole (steps included in the Checkpoint docs linked above).
  4. Within Kibana, browse to Integrations and locate the Check Point integration, and Add Check Point.
  5. Add Elastic Agent to host with Fleet, or install Elastic Agent manually after configuring the integration.
  6. Configure the TCP or UDP input, depending on the protocol you configured Check Point to use.
  7. Add a certificate if using Secure Syslog over TCP with TLS (optional)
  8. Add integration to a New/Existing policy.
  9. Browse to dashboard/discover to validate data is flowing from Check Point.

Logfile

edit

Elastic Agent can process log messages by monitoring a log file on a host receiving syslog messages. The syslog server will receive messages from Check Point, write to a logfile, and Elastic Agent will watch the log file to send to the Elastic Cluster.

  1. Install a syslog server on a host between your Check Point Log Exporter instance and Elastic Cluster.
  2. Configure the syslog server to write logs to a logfile.
  3. For each firewall device you wish to monitor, create a new Log Exporter/SIEM object in Check Point SmartConsole. Set the target server and target port to the syslog server. Set the protocol to UDP or TCP, the Check Point integration supports both. Set the format to syslog.
  4. Configure the Management Server or Dedicated Log Server object in SmartConsole.
  5. Install the database within SmartConsole (steps included in the Checkpoint docs linked above).
  6. Within Kibana, navigate to the Integrations section and locate the Check Point integration. Click on the "Add Check Point" button to initiate the integration process.
  7. Add Elastic Agent to host with Fleet, or install Elastic Agent manually after configuring the integration.
  8. Configure the logfile input, to monitor the logfile pattern that the syslog server will write to.
  9. Add integration to a New/Existing policy.
  10. Browse to dashboard/discover to validate data is flowing from Check Point.

Logs reference

edit

Firewall

edit

The Check Point integration collects data in a single data stream, the firewall data set. This consists of log entries from the Log Exporter in the Syslog format.

Example

An example event for firewall looks as following:

{
    "@timestamp": "2020-03-29T13:19:20.000Z",
    "agent": {
        "ephemeral_id": "81d2d360-6c18-4a7e-8eef-cb77b6566cec",
        "id": "ecc82406-78ce-41c1-b1e2-7c12ce01f525",
        "name": "docker-fleet-agent",
        "type": "filebeat",
        "version": "8.5.1"
    },
    "checkpoint": {
        "sys_message": "The eth0 interface is not protected by the anti-spoofing feature. Your network may be at risk"
    },
    "data_stream": {
        "dataset": "checkpoint.firewall",
        "namespace": "ep",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "ecc82406-78ce-41c1-b1e2-7c12ce01f525",
        "snapshot": false,
        "version": "8.5.1"
    },
    "event": {
        "agent_id_status": "verified",
        "category": [
            "network"
        ],
        "created": "2023-02-09T03:09:35.057Z",
        "dataset": "checkpoint.firewall",
        "id": "{0x5e80a059,0x0,0x6401a8c0,0x3c7878a}",
        "ingested": "2023-02-09T03:09:36Z",
        "kind": "event",
        "sequence": 1,
        "timezone": "UTC"
    },
    "input": {
        "type": "tcp"
    },
    "log": {
        "source": {
            "address": "192.168.32.6:58272"
        }
    },
    "network": {
        "direction": "inbound"
    },
    "observer": {
        "ingress": {
            "interface": {
                "name": "daemon"
            }
        },
        "name": "192.168.1.100",
        "product": "System Monitor",
        "type": "firewall",
        "vendor": "Checkpoint"
    },
    "tags": [
        "forwarded"
    ]
}
Exported fields
Field Description Type

@timestamp

Event timestamp.

date

checkpoint.action_reason

Connection drop reason.

integer

checkpoint.action_reason_msg

Connection drop reason message.

keyword

checkpoint.additional_info

ID of original file/mail which are sent by admin.

keyword

checkpoint.additional_ip

DNS host name.

keyword

checkpoint.additional_rdata

List of additional resource records.

keyword

checkpoint.administrator

Source administrator name.

keyword

checkpoint.advanced_changes

keyword

checkpoint.alert

Alert level of matched rule (for connection logs).

keyword

checkpoint.allocated_ports

Amount of allocated ports.

integer

checkpoint.analyzed_on

Check Point ThreatCloud / emulator name.

keyword

checkpoint.answer_rdata

List of answer resource records to the questioned domains.

keyword

checkpoint.anti_virus_type

Anti virus type.

keyword

checkpoint.app_desc

Application description.

keyword

checkpoint.app_id

Application ID.

integer

checkpoint.app_package

Unique identifier of the application on the protected mobile device.

keyword

checkpoint.app_properties

List of all found categories.

keyword

checkpoint.app_repackaged

Indicates whether the original application was repackage not by the official developer.

keyword

checkpoint.app_sid_id

Unique SHA identifier of a mobile application.

keyword

checkpoint.app_sig_id

IOC indicator description.

keyword

checkpoint.app_version

Version of the application downloaded on the protected mobile device.

keyword

checkpoint.appi_name

Name of application downloaded on the protected mobile device.

keyword

checkpoint.arrival_time

Email arrival timestamp.

keyword

checkpoint.attachments_num

Number of attachments in the mail.

integer

checkpoint.attack_status

In case of a malicious event on an endpoint computer, the status of the attack.

keyword

checkpoint.audit_status

Audit Status. Can be Success or Failure.

keyword

checkpoint.auth_method

Password authentication protocol used (PAP or EAP).

keyword

checkpoint.auth_status

The authentication status for an event.

keyword

checkpoint.authority_rdata

List of authoritative servers.

keyword

checkpoint.authorization

Authorization HTTP header value.

keyword

checkpoint.bcc

List of BCC addresses.

keyword

checkpoint.blade_name

Blade name.

keyword

checkpoint.broker_publisher

IP address of the broker publisher who shared the session information.

ip

checkpoint.browse_time

Application session browse time.

keyword

checkpoint.c_bytes

Boolean value indicates whether bytes sent from the client side are used.

integer

checkpoint.calc_desc

Log description.

keyword

checkpoint.capacity

Capacity of the ports.

integer

checkpoint.capture_uuid

UUID generated for the capture. Used when enabling the capture when logging.

keyword

checkpoint.cc

The Carbon Copy address of the email.

keyword

checkpoint.certificate_resource

HTTPS resource Possible values: SNI or domain name (DN).

keyword

checkpoint.certificate_validation

Precise error, describing HTTPS certificate failure under "HTTPS categorize websites" feature.

keyword

checkpoint.cgnet

Describes NAT allocation for specific subscriber.

keyword

checkpoint.chunk_type

Chunck of the sctp stream.

keyword

checkpoint.client_ipe

keyword

checkpoint.client_name

Client Application or Software Blade that detected the event.

keyword

checkpoint.client_type

Endpoint Connect.

keyword

checkpoint.client_type_os

Client OS detected in the HTTP request.

keyword

checkpoint.client_version

Build version of SandBlast Agent client installed on the computer.

keyword

checkpoint.cluster_info

Cluster information. Possible options: Failover reason/cluster state changes/CP cluster or 3rd party.

keyword

checkpoint.comment

keyword

checkpoint.community

Community name for the IPSec key and the use of the IKEv.

keyword

checkpoint.confidence_level

Confidence level determined by ThreatCloud.

integer

checkpoint.conn_direction

Connection direction

keyword

checkpoint.connection_uid

Calculation of md5 of the IP and user name as UID.

keyword

checkpoint.connectivity_level

Log for a new connection in wire mode.

keyword

checkpoint.conns_amount

Connections amount of aggregated log info.

integer

checkpoint.content_disposition

Indicates how the content is expected to be displayed inline in the browser.

keyword

checkpoint.content_length

Indicates the size of the entity-body of the HTTP header.

keyword

checkpoint.content_risk

File risk.

integer

checkpoint.content_type

Mail content type. Possible values: application/msword, text/html, image/gif etc.

keyword

checkpoint.context_num

Serial number of the log for a specific connection.

integer

checkpoint.contract_name

keyword

checkpoint.control_log_type

keyword

checkpoint.cookieI

Initiator cookie.

keyword

checkpoint.cookieR

Responder cookie.

keyword

checkpoint.cp_component_name

keyword

checkpoint.cp_component_version

keyword

checkpoint.cp_message

Used to log a general message.

integer

checkpoint.cvpn_category

Mobile Access application type.

keyword

checkpoint.cvpn_resource

Mobile Access application.

keyword

checkpoint.data_type_name

Data type in rulebase that was matched.

keyword

checkpoint.db_ver

Database version

keyword

checkpoint.dce-rpc_interface_uuid

Log for new RPC state - UUID values

keyword

checkpoint.default_device_message

Encapsulated log message.

keyword

checkpoint.delivery_time

Timestamp of when email was delivered (MTA finished handling the email.

keyword

checkpoint.desc

Override application description.

keyword

checkpoint.description

Additional explanation how the security gateway enforced the connection.

keyword

checkpoint.destination_object

Matched object name on destination column.

keyword

checkpoint.detected_on

System and applications version the file was emulated on.

keyword

checkpoint.developer_certificate_name

Name of the developer’s certificate that was used to sign the mobile application.

keyword

checkpoint.device_name

Name of the device.

keyword

checkpoint.device_type

Type of the device.

keyword

checkpoint.diameter_app_ID

The ID of diameter application.

integer

checkpoint.diameter_cmd_code

Diameter not allowed application command id.

integer

checkpoint.diameter_msg_type

Diameter message type.

keyword

checkpoint.dlp_action_reason

Action chosen reason.

keyword

checkpoint.dlp_additional_action

Watermark/None.

keyword

checkpoint.dlp_categories

Data type category.

keyword

checkpoint.dlp_data_type_name

Matched data type.

keyword

checkpoint.dlp_data_type_uid

Unique ID of the matched data type.

keyword

checkpoint.dlp_fingerprint_files_number

Number of successfully scanned files in repository.

integer

checkpoint.dlp_fingerprint_long_status

Scan status - long format.

keyword

checkpoint.dlp_fingerprint_short_status

Scan status - short format.

keyword

checkpoint.dlp_incident_uid

Unique ID of the matched rule.

keyword

checkpoint.dlp_recipients

Mail recipients.

keyword

checkpoint.dlp_related_incident_uid

Other ID related to this one.

keyword

checkpoint.dlp_relevant_data_types

In case of Compound/Group: the inner data types that were matched.

keyword

checkpoint.dlp_repository_directories_number

Number of directories in repository.

integer

checkpoint.dlp_repository_files_number

Number of files in repository.

integer

checkpoint.dlp_repository_id

ID of scanned repository.

keyword

checkpoint.dlp_repository_not_scanned_directories_percentage

Percentage of directories the Security Gateway was unable to read.

integer

checkpoint.dlp_repository_reached_directories_number

Number of scanned directories in repository.

integer

checkpoint.dlp_repository_root_path

Repository path.

keyword

checkpoint.dlp_repository_scan_progress

Scan percentage.

integer

checkpoint.dlp_repository_scanned_directories_number

Amount of directories scanned.

integer

checkpoint.dlp_repository_scanned_files_number

Number of scanned files in repository.

integer

checkpoint.dlp_repository_scanned_total_size

Size scanned.

integer

checkpoint.dlp_repository_skipped_files_number

Skipped number of files because of configuration.

integer

checkpoint.dlp_repository_total_size

Repository size.

integer

checkpoint.dlp_repository_unreachable_directories_number

Number of directories the Security Gateway was unable to read.

integer

checkpoint.dlp_rule_name

Matched rule name.

keyword

checkpoint.dlp_subject

Mail subject.

keyword

checkpoint.dlp_template_score

Template data type match score.

keyword

checkpoint.dlp_transint

HTTP/SMTP/FTP.

keyword

checkpoint.dlp_violation_description

Violation descriptions described in the rulebase.

keyword

checkpoint.dlp_watermark_profile

Watermark which was applied.

keyword

checkpoint.dlp_word_list

Phrases matched by data type.

keyword

checkpoint.dns_query

DNS query.

keyword

checkpoint.dport_svc

Destination port of the connection.

integer

checkpoint.drop_reason

Drop reason description.

keyword

checkpoint.dropped_file_hash

List of file hashes dropped from the original file.

keyword

checkpoint.dropped_file_name

List of names dropped from the original file.

keyword

checkpoint.dropped_file_type

List of file types dropped from the original file.

keyword

checkpoint.dropped_file_verdict

List of file verdics dropped from the original file.

keyword

checkpoint.dropped_incoming

Number of incoming bytes dropped when using UP-limit feature.

integer

checkpoint.dropped_outgoing

Number of outgoing bytes dropped when using UP-limit feature.

integer

checkpoint.dropped_total

Amount of dropped packets (both incoming and outgoing).

integer

checkpoint.drops_amount

Amount of multicast packets dropped.

integer

checkpoint.dst_country

Destination country.

keyword

checkpoint.dst_phone_number

Destination IP-Phone.

keyword

checkpoint.dst_user_dn

User distinguished name connected to the destination IP address.

keyword

checkpoint.dst_user_name

Connected user name on the destination IP.

keyword

checkpoint.dstkeyid

Responder Spi ID.

keyword

checkpoint.duplicate

Log marked as duplicated, when mail is split and the Security Gateway sees it twice.

keyword

checkpoint.duration

Scan duration.

keyword

checkpoint.elapsed

Time passed since start time.

keyword

checkpoint.email_content

Mail contents. Possible options: attachments/links & attachments/links/text only.

keyword

checkpoint.email_control

Engine name.

keyword

checkpoint.email_control_analysis

Message classification, received from spam vendor engine.

keyword

checkpoint.email_headers

String containing all the email headers.

keyword

checkpoint.email_id

Email number in smtp connection.

keyword

checkpoint.email_message_id

Email session id (uniqe ID of the mail).

keyword

checkpoint.email_queue_id

Postfix email queue id.

keyword

checkpoint.email_queue_name

Postfix email queue name.

keyword

checkpoint.email_recipients_num

Amount of recipients whom the mail was sent to.

long

checkpoint.email_session_id

Connection uuid.

keyword

checkpoint.email_spam_category

Email categories. Possible values: spam/not spam/phishing.

keyword

checkpoint.email_status

Describes the email’s state. Possible options: delivered, deferred, skipped, bounced, hold, new, scan_started, scan_ended

keyword

checkpoint.email_subject

Original email subject.

keyword

checkpoint.emulated_on

Images the files were emulated on.

keyword

checkpoint.encryption_failure

Message indicating why the encryption failed.

keyword

checkpoint.end_time

TCP connection end time.

keyword

checkpoint.end_user_firewall_type

End user firewall type.

keyword

checkpoint.esod_access_status

Access denied.

keyword

checkpoint.esod_associated_policies

Associated policies.

keyword

checkpoint.esod_noncompliance_reason

Non-compliance reason.

keyword

checkpoint.esod_rule_action

Unknown rule action.

keyword

checkpoint.esod_rule_name

Unknown rule name.

keyword

checkpoint.esod_rule_type

Unknown rule type.

keyword

checkpoint.esod_scan_status

Scan failed.

keyword

checkpoint.event_count

Number of events associated with the log.

long

checkpoint.expire_time

Connection closing time.

keyword

checkpoint.extension_version

Build version of the SandBlast Agent browser extension.

keyword

checkpoint.extracted_file_hash

Archive hash in case of extracted files.

keyword

checkpoint.extracted_file_names

Names of extracted files in case of an archive.

keyword

checkpoint.extracted_file_type

Types of extracted files in case of an archive.

keyword

checkpoint.extracted_file_uid

UID of extracted files in case of an archive.

keyword

checkpoint.extracted_file_verdict

Verdict of extracted files in case of an archive.

keyword

checkpoint.facility

keyword

checkpoint.failure_impact

The impact of update service failure.

keyword

checkpoint.failure_reason

MTA failure description.

keyword

checkpoint.fields

keyword

checkpoint.fieldschanges

keyword

checkpoint.file_direction

File direction. Possible options: upload/download.

keyword

checkpoint.file_name

Malicious file name.

keyword

checkpoint.files_names

List of files requested by FTP.

keyword

checkpoint.first_hit_time

First hit time in current interval.

integer

checkpoint.frequency

keyword

checkpoint.fs-proto

The file share protocol used in mobile acess file share application.

keyword

checkpoint.ftp_user

FTP username.

keyword

checkpoint.fw_message

Used for various firewall errors.

keyword

checkpoint.fw_subproduct

Can be vpn/non vpn.

keyword

checkpoint.hide_ip

Source IP which will be used after CGNAT.

ip

checkpoint.hit

Number of hits on a rule.

integer

checkpoint.host_time

Local time on the endpoint computer.

keyword

checkpoint.http_host

Domain name of the server that the HTTP request is sent to.

keyword

checkpoint.http_location

Response header, indicates the URL to redirect a page to.

keyword

checkpoint.http_server

Server HTTP header value, contains information about the software used by the origin server, which handles the request.

keyword

checkpoint.https_inspection_action

HTTPS inspection action (Inspect/Bypass/Error).

keyword

checkpoint.https_inspection_rule_id

ID of the matched rule.

keyword

checkpoint.https_inspection_rule_name

Name of the matched rule.

keyword

checkpoint.https_validation

Precise error, describing HTTPS inspection failure.

keyword

checkpoint.icap_more_info

Free text for verdict.

integer

checkpoint.icap_server_name

Server name.

keyword

checkpoint.icap_server_service

Service name, as given in the ICAP URI

keyword

checkpoint.icap_service_id

Service ID, can work with multiple servers, treated as services.

integer

checkpoint.icmp

Number of packets, received by the client.

keyword

checkpoint.icmp_code

In case a connection is ICMP, code info will be added to the log.

long

checkpoint.icmp_type

In case a connection is ICMP, type info will be added to the log.

long

checkpoint.id

Override application ID.

integer

checkpoint.identity_src

The source for authentication identity information.

keyword

checkpoint.identity_type

The type of identity used for authentication.

keyword

checkpoint.ike

IKEMode (PHASE1, PHASE2, etc..).

keyword

checkpoint.ike_ids

All QM ids.

keyword

checkpoint.impacted_files

In case of an infection on an endpoint computer, the list of files that the malware impacted.

keyword

checkpoint.incident_extension

Matched data type.

keyword

checkpoint.indicator_description

IOC indicator description.

keyword

checkpoint.indicator_name

IOC indicator name.

keyword

checkpoint.indicator_reference

IOC indicator reference.

keyword

checkpoint.indicator_uuid

IOC indicator uuid.

keyword

checkpoint.info

Special log message.

keyword

checkpoint.information

Policy installation status for a specific blade.

keyword

checkpoint.inspection_category

Inspection category: protocol anomaly, signature etc.

keyword

checkpoint.inspection_item

Blade element performed inspection.

keyword

checkpoint.inspection_profile

Profile which the activated protection belongs to.

keyword

checkpoint.inspection_settings_log

Indicats that the log was released by inspection settings.

keyword

checkpoint.install_policy_acceleration

Whether policy installation was accelerated. See CheckPoint R81 Security Mnagement Admin Guide (PDF).

keyword

checkpoint.installed_products

List of installed Endpoint Software Blades.

keyword

checkpoint.int_end

Subscriber end int which will be used for NAT.

integer

checkpoint.int_start

Subscriber start int which will be used for NAT.

integer

checkpoint.interface_name

Designated interface for mirror And decrypt.

keyword

checkpoint.internal_ca

keyword

checkpoint.internal_error

Internal error, for troubleshooting

keyword

checkpoint.invalid_file_size

File_size field is valid only if this field is set to 0.

integer

checkpoint.ip_address

ip

checkpoint.ip_option

IP option that was dropped.

integer

checkpoint.isp_link

Name of ISP link.

keyword

checkpoint.last_hit_time

Last hit time in current interval.

integer

checkpoint.last_rematch_time

Connection rematched time.

keyword

checkpoint.layer_name

Layer name.

keyword

checkpoint.layer_uuid

Layer UUID.

keyword

checkpoint.limit_applied

Indicates whether the session was actually date limited.

integer

checkpoint.limit_requested

Indicates whether data limit was requested for the session.

integer

checkpoint.link_probing_status_update

IP address response status.

keyword

checkpoint.links_num

Number of links in the mail.

integer

checkpoint.log_delay

Time left before deleting template.

integer

checkpoint.log_id

Unique identity for logs.

integer

checkpoint.log_sys_message

Sytem log messages.

keyword

checkpoint.logic_changes

keyword

checkpoint.logid

System messages

keyword

checkpoint.long_desc

More information on the process (usually describing error reason in failure).

keyword

checkpoint.machine

L2TP machine which triggered the log and the log refers to it.

keyword

checkpoint.malware_family

Additional information on protection.

keyword

checkpoint.match_fk

Rule number.

integer

checkpoint.match_id

Private key of the rule

integer

checkpoint.matched_file

Unique ID of the matched data type.

keyword

checkpoint.matched_file_percentage

Fingerprint: match percentage of the traffic.

integer

checkpoint.matched_file_text_segments

Fingerprint: number of text segments matched by this traffic.

integer

checkpoint.media_type

Media used (audio, video, etc.)

keyword

checkpoint.message

ISP link has failed.

keyword

checkpoint.message_info

Used for information messages, for example:NAT connection has ended.

keyword

checkpoint.message_size

Mail/post size.

integer

checkpoint.method

HTTP method.

keyword

checkpoint.methods

IPSEc methods.

keyword

checkpoint.mime_from

Sender’s address.

keyword

checkpoint.mime_to

List of receiver address.

keyword

checkpoint.mirror_and_decrypt_type

Information about decrypt and forward. Possible values: Mirror only, Decrypt and mirror, Partial mirroring (HTTPS inspection Bypass).

keyword

checkpoint.mitre_collection

The adversary is trying to collect data of interest to achieve his goal.

keyword

checkpoint.mitre_command_and_control

The adversary is trying to communicate with compromised systems in order to control them.

keyword

checkpoint.mitre_credential_access

The adversary is trying to steal account names and passwords.

keyword

checkpoint.mitre_defense_evasion

The adversary is trying to avoid being detected.

keyword

checkpoint.mitre_discovery

The adversary is trying to expose information about your environment.

keyword

checkpoint.mitre_execution

The adversary is trying to run malicious code.

keyword

checkpoint.mitre_exfiltration

The adversary is trying to steal data.

keyword

checkpoint.mitre_impact

The adversary is trying to manipulate, interrupt, or destroy your systems and data.

keyword

checkpoint.mitre_initial_access

The adversary is trying to break into your network.

keyword

checkpoint.mitre_lateral_movement

The adversary is trying to explore your environment.

keyword

checkpoint.mitre_persistence

The adversary is trying to maintain his foothold.

keyword

checkpoint.mitre_privilege_escalation

The adversary is trying to gain higher-level permissions.

keyword

checkpoint.monitor_reason

Aggregated logs of monitored packets.

keyword

checkpoint.msgid

Message ID.

keyword

checkpoint.name

Application name.

keyword

checkpoint.nat46

NAT 46 status, in most cases "enabled".

keyword

checkpoint.nat_addtnl_rulenum

When matching 2 automatic rules , second rule match will be shown otherwise field will be 0.

integer

checkpoint.nat_exhausted_pool

4-tuple of an exhausted pool.

keyword

checkpoint.nat_rule_uid

keyword

checkpoint.nat_rulenum

NAT rulebase first matched rule.

integer

checkpoint.needs_browse_time

Browse time required for the connection.

integer

checkpoint.next_hop_ip

Next hop IP address.

keyword

checkpoint.next_scheduled_scan_date

Next scan scheduled time according to time object.

keyword

checkpoint.next_update_desc

keyword

checkpoint.number_of_errors

Number of files that were not scanned due to an error.

integer

checkpoint.objecttable

Table of affected objects.

keyword

checkpoint.objecttype

The type of the affected object.

keyword

checkpoint.observable_comment

IOC observable signature description.

keyword

checkpoint.observable_id

IOC observable signature id.

keyword

checkpoint.observable_name

IOC observable signature name.

keyword

checkpoint.operation

Operation made by Threat Extraction.

keyword

checkpoint.operation_number

The operation number.

keyword

checkpoint.operation_result_description

keyword

checkpoint.operation_results

keyword

checkpoint.origin_sic_name

SIC name of the Security Gateway that generated the event.

keyword

checkpoint.original_queue_id

Original postfix email queue id.

keyword

checkpoint.outgoing_url

URL related to this log (for HTTP).

keyword

checkpoint.outzonlags

keyword

checkpoint.package_action

keyword

checkpoint.packet_amount

Amount of packets dropped.

integer

checkpoint.packet_capture_name

keyword

checkpoint.packet_capture_time

keyword

checkpoint.packet_capture_unique_id

Identifier of the packet capture files.

keyword

checkpoint.parent_file_hash

Archive’s hash in case of extracted files.

keyword

checkpoint.parent_file_name

Archive’s name in case of extracted files.

keyword

checkpoint.parent_file_uid

Archive’s UID in case of extracted files.

keyword

checkpoint.parent_process_username

Owner username of the parent process of the process that triggered the attack.

keyword

checkpoint.parent_rule

Parent rule number, in case of inline layer.

integer

checkpoint.peer_gateway

Main IP of the peer Security Gateway.

ip

checkpoint.peer_ip

IP address which the client connects to.

keyword

checkpoint.peer_ip_probing_status_update

IP address response status.

keyword

checkpoint.performance_impact

Protection performance impact.

integer

checkpoint.policy_mgmt

Name of the Management Server that manages this Security Gateway.

keyword

checkpoint.policy_name

Name of the last policy that this Security Gateway fetched.

keyword

checkpoint.policy_time

keyword

checkpoint.portal_message

keyword

checkpoint.ports_usage

Percentage of allocated ports.

integer

checkpoint.ppp

Authentication status.

keyword

checkpoint.precise_error

HTTP parser error.

keyword

checkpoint.process_username

Owner username of the process that triggered the attack.

keyword

checkpoint.properties

Application categories.

keyword

checkpoint.protection_id

Protection malware id.

keyword

checkpoint.protection_name

Specific signature name of the attack.

keyword

checkpoint.protection_type

Type of protection used to detect the attack.

keyword

checkpoint.protocol

Protocol detected on the connection.

keyword

checkpoint.proxy_machine_name

Machine name connected to proxy IP.

integer

checkpoint.proxy_src_ip

Sender source IP (even when using proxy).

ip

checkpoint.proxy_user_dn

User distinguished name connected to proxy IP.

keyword

checkpoint.proxy_user_name

User name connected to proxy IP.

keyword

checkpoint.query

DNS query.

keyword

checkpoint.question_rdata

List of question records domains.

keyword

checkpoint.referrer

Referrer HTTP request header, previous web page address.

keyword

checkpoint.referrer_parent_uid

Log UUID of the referring application.

keyword

checkpoint.referrer_self_uid

UUID of the current log.

keyword

checkpoint.registered_ip-phones

Registered IP-Phones.

keyword

checkpoint.reject_category

Authentication failure reason.

keyword

checkpoint.reject_id

A reject ID that corresponds to the one presented in the Mobile Access error page.

keyword

checkpoint.rematch_info

Information sent when old connections cannot be matched during policy installation.

keyword

checkpoint.remediated_files

In case of an infection and a successful cleaning of that infection, this is a list of remediated files on the computer.

keyword

checkpoint.reply_status

ICAP reply status code, e.g. 200 or 204.

integer

checkpoint.risk

Risk level we got from the engine.

keyword

checkpoint.roles

The role of identity.

keyword

checkpoint.row_start

keyword

checkpoint.rpc_prog

Log for new RPC state - prog values.

integer

checkpoint.rule

Matched rule number.

integer

checkpoint.rule_action

Action of the matched rule in the access policy.

keyword

checkpoint.rulebase_id

Layer number.

integer

checkpoint.scan_direction

Scan direction.

keyword

checkpoint.scan_hosts_day

Number of unique hosts during the last day.

integer

checkpoint.scan_hosts_hour

Number of unique hosts during the last hour.

integer

checkpoint.scan_hosts_week

Number of unique hosts during the last week.

integer

checkpoint.scan_id

Sequential number of scan.

keyword

checkpoint.scan_mail

Number of emails that were scanned by "AB malicious activity" engine.

integer

checkpoint.scan_results

"Infected"/description of a failure.

keyword

checkpoint.scheme

Describes the scheme used for the log.

keyword

checkpoint.scope

IP related to the attack.

keyword

checkpoint.script_value_for_one_time_scripts

keyword

checkpoint.scrub_activity

The result of the extraction

keyword

checkpoint.scrub_download_time

File download time from resource.

keyword

checkpoint.scrub_time

Extraction process duration.

keyword

checkpoint.scrub_total_time

Threat extraction total file handling time.

keyword

checkpoint.scrubbed_content

Active content that was found.

keyword

checkpoint.sctp_association_state

The bad state you were trying to update to.

keyword

checkpoint.sctp_error

Error information, what caused sctp to fail on out_of_state.

keyword

checkpoint.scv_message_info

Drop reason.

keyword

checkpoint.scv_user

Username whose packets are dropped on SCV.

keyword

checkpoint.securexl_message

Two options for a SecureXL message: 1. Missed accounting records after heavy load on logging system. 2. FW log message regarding a packet drop.

keyword

checkpoint.security_inzone

Network zone of incoming traffic as reported by the observer to categorize the source area of ingress traffic. e.g. internal, External, DMZ, HR, Legal, etc.

keyword

checkpoint.security_outzone

Network zone of outbound traffic as reported by the observer to categorize the destination area of egress traffic, e.g. Internal, External, DMZ, HR, Legal, etc.

keyword

checkpoint.sendtotrackerasadvancedauditlog

keyword

checkpoint.sent_bytes

keyword

checkpoint.server_inbound_interface

In-bound interface name as reported by the system.

keyword

checkpoint.server_outbound_interface

Out-bound interface name as reported by the system.

keyword

checkpoint.session_description

keyword

checkpoint.session_id

Log uuid.

keyword

checkpoint.session_name

keyword

checkpoint.session_uid

HTTP session-id.

keyword

checkpoint.short_desc

Short description of the process that was executed.

keyword

checkpoint.sig_id

Application’s signature ID which how it was detected by.

keyword

checkpoint.similar_communication

Network action found similar to the malicious file.

keyword

checkpoint.similar_hashes

Hashes found similar to the malicious file.

keyword

checkpoint.similar_strings

Strings found similar to the malicious file.

keyword

checkpoint.similiar_iocs

Other IoCs similar to the ones found, related to the malicious file.

keyword

checkpoint.sip_reason

Explains why source_ip isn’t allowed to redirect (handover).

keyword

checkpoint.site_name

Site name.

keyword

checkpoint.smartdefense_profile

keyword

checkpoint.snid

The Check Point session ID.

keyword

checkpoint.source_interface

External Interface name for source interface or Null if not found.

keyword

checkpoint.source_object

Matched object name on source column.

keyword

checkpoint.source_os

OS which generated the attack.

keyword

checkpoint.special_properties

If this field is set to 1 the log will not be shown (in use for monitoring scan progress).

integer

checkpoint.specific_data_type_name

Compound/Group scenario, data type that was matched.

keyword

checkpoint.speed

Current scan speed.

integer

checkpoint.sport_svc

Source port of the connection.

integer

checkpoint.spyware_name

Spyware name.

keyword

checkpoint.spyware_type

Spyware type.

keyword

checkpoint.src_country

Country name, derived from connection source IP address.

keyword

checkpoint.src_phone_number

Source IP-Phone.

keyword

checkpoint.src_user_dn

User distinguished name connected to source IP.

keyword

checkpoint.src_user_name

User name connected to source IP.

keyword

checkpoint.srckeyid

Initiator Spi ID.

keyword

checkpoint.status

Ok/Warning/Error.

keyword

checkpoint.status_update

Last time log was updated.

keyword

checkpoint.stormagentaction

keyword

checkpoint.stormagentname

keyword

checkpoint.sub_policy_name

Layer name.

keyword

checkpoint.sub_policy_uid

Layer uid.

keyword

checkpoint.subs_exp

date

checkpoint.subscriber

Source IP before CGNAT.

ip

checkpoint.subscription_stat

keyword

checkpoint.subscription_stat_desc

keyword

checkpoint.summary

Summary message of a non-compliant DNS traffic drops or detects.

keyword

checkpoint.suppressed_logs

Aggregated connections for five minutes on the same source, destination and port.

integer

checkpoint.svc

The name of the service.

keyword

checkpoint.sync

Sync status and the reason (stable, at risk).

keyword

checkpoint.sys_message

System messages

keyword

checkpoint.syslog_severity

Syslog severity level.

keyword

checkpoint.system_application

keyword

checkpoint.task

keyword

checkpoint.task_percent

keyword

checkpoint.task_progress

keyword

checkpoint.taskid

keyword

checkpoint.tasktargetid

keyword

checkpoint.tcp_end_reason

Reason for TCP connection closure.

keyword

checkpoint.tcp_flags

TCP packet flags (SYN, ACK, etc.,).

keyword

checkpoint.tcp_packet_out_of_state

State violation.

keyword

checkpoint.tcp_state

Log reinting a tcp state change.

keyword

checkpoint.te_verdict_determined_by

Emulators determined file verdict.

keyword

checkpoint.ticket_id

Unique ID per file.

keyword

checkpoint.time

If more than one time is mentioned in an event, this field will contain all of them.

date

checkpoint.tls_server_host_name

SNI/CN from encrypted TLS connection used by URLF for categorization.

keyword

checkpoint.top_archive_file_name

In case of archive file: the file that was sent/received.

keyword

checkpoint.total_attachments

The number of attachments in an email.

integer

checkpoint.triggered_by

The name of the mechanism that triggered the Software Blade to enforce a protection.

keyword

checkpoint.trusted_domain

In case of phishing event, the domain, which the attacker was impersonating.

keyword

checkpoint.unique_detected_day

Detected virus for a specific host during the last day.

integer

checkpoint.unique_detected_hour

Detected virus for a specific host during the last hour.

integer

checkpoint.unique_detected_week

Detected virus for a specific host during the last week.

integer

checkpoint.update_status

Status of database update

keyword

checkpoint.url

Translated URL.

keyword

checkpoint.user

Source user name.

keyword

checkpoint.user_agent

String identifying requesting software user agent.

keyword

checkpoint.usercheck

keyword

checkpoint.usercheck_confirmation_level

keyword

checkpoint.usercheck_interaction_name

keyword

checkpoint.vendor_list

The vendor name that provided the verdict for a malicious URL.

keyword

checkpoint.verdict

TE engine verdict Possible values: Malicious/Benign/Error.

keyword

checkpoint.via

Via header is added by proxies for tracking purposes to avoid sending reqests in loop.

keyword

checkpoint.voip_attach_action_info

Attachment action Info.

keyword

checkpoint.voip_attach_sz

Attachment size.

integer

checkpoint.voip_call_dir

Call direction: in/out.

keyword

checkpoint.voip_call_id

Call-ID.

keyword

checkpoint.voip_call_state

Call state. Possible values: in/out.

keyword

checkpoint.voip_call_term_time

Call termination time stamp.

keyword

checkpoint.voip_config

Configuration.

keyword

checkpoint.voip_duration

Call duration (seconds).

keyword

checkpoint.voip_est_codec

Estimated codec.

keyword

checkpoint.voip_exp

Expiration.

integer

checkpoint.voip_from_user_type

Source IP-Phone type.

keyword

checkpoint.voip_log_type

VoIP log types. Possible values: reject, call, registration.

keyword

checkpoint.voip_media_codec

Estimated codec.

keyword

checkpoint.voip_media_ipp

Media IP protocol.

keyword

checkpoint.voip_media_port

Media int.

keyword

checkpoint.voip_method

Registration request.

keyword

checkpoint.voip_reason_info

Information.

keyword

checkpoint.voip_reg_int

Registration port.

integer

checkpoint.voip_reg_ipp

Registration IP protocol.

integer

checkpoint.voip_reg_period

Registration period.

integer

checkpoint.voip_reg_server

Registrar server IP address.

ip

checkpoint.voip_reg_user_type

Registered IP-Phone type.

keyword

checkpoint.voip_reject_reason

Reject reason.

keyword

checkpoint.voip_to_user_type

Destination IP-Phone type.

keyword

checkpoint.vpn_feature_name

L2TP /IKE / Link Selection.

keyword

checkpoint.watermark

Reports whether watermark is added to the cleaned file.

keyword

checkpoint.web_server_type

Web server detected in the HTTP response.

keyword

checkpoint.word_list

Words matched by data type.

keyword

checkpoint.xlatedport_svc

Destination translated port for the service.

keyword

checkpoint.xlatesport_svc

Source translated port for the service.

keyword

cloud.account.id

The cloud account or organization id used to identify different entities in a multi-tenant environment. Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.

keyword

cloud.availability_zone

Availability zone in which this host is running.

keyword

cloud.image.id

Image ID for the cloud instance.

keyword

cloud.instance.id

Instance ID of the host machine.

keyword

cloud.instance.name

Instance name of the host machine.

keyword

cloud.machine.type

Machine type of the host machine.

keyword

cloud.project.id

Name of the project in Google Cloud.

keyword

cloud.provider

Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean.

keyword

cloud.region

Region in which this host is running.

keyword

container.id

Unique container id.

keyword

container.image.name

Name of the image the container was built on.

keyword

container.labels

Image labels.

object

container.name

Container name.

keyword

data_stream.dataset

Data stream dataset.

constant_keyword

data_stream.namespace

Data stream namespace.

constant_keyword

data_stream.type

Data stream type.

constant_keyword

destination.as.number

Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.

long

destination.as.organization.name

Organization name.

keyword

destination.as.organization.name.text

Multi-field of destination.as.organization.name.

match_only_text

destination.bytes

Bytes sent from the destination to the source.

long

destination.domain

The domain name of the destination system. This value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment.

keyword

destination.geo.city_name

City name.

keyword

destination.geo.continent_name

Name of the continent.

keyword

destination.geo.country_iso_code

Country ISO code.

keyword

destination.geo.country_name

Country name.

keyword

destination.geo.location

Longitude and latitude.

geo_point

destination.geo.name

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

keyword

destination.geo.region_iso_code

Region ISO code.

keyword

destination.geo.region_name

Region name.

keyword

destination.ip

IP address of the destination (IPv4 or IPv6).

ip

destination.mac

MAC address of the destination. The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen.

keyword

destination.nat.ip

Translated ip of destination based NAT sessions (e.g. internet to private DMZ) Typically used with load balancers, firewalls, or routers.

ip

destination.nat.port

Port the source session is translated to by NAT Device. Typically used with load balancers, firewalls, or routers.

long

destination.packets

Packets sent from the destination to the source.

long

destination.port

Port of the destination.

long

destination.service.name

Name of the service data is collected from.

keyword

destination.user.domain

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

keyword

destination.user.email

User email address.

keyword

destination.user.id

Unique identifier of the user.

keyword

destination.user.name

Short name or login of the user.

keyword

destination.user.name.text

Multi-field of destination.user.name.

match_only_text

dns.id

The DNS packet identifier assigned by the program that generated the query. The identifier is copied to the response.

keyword

dns.question.name

The name being queried. If the name field contains non-printable characters (below 32 or above 126), those characters should be represented as escaped base 10 integers (\DDD). Back slashes and quotes should be escaped. Tabs, carriage returns, and line feeds should be converted to \t, \r, and \n respectively.

keyword

dns.question.type

The type of record being queried.

keyword

dns.type

The type of DNS event captured, query or answer. If your source of DNS events only gives you DNS queries, you should only create dns events of type dns.type:query. If your source of DNS events gives you answers as well, you should create one event per query (optionally as soon as the query is seen). And a second event containing all query details as well as an array of answers.

keyword

ecs.version

ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices — which may conform to slightly different ECS versions — this field lets integrations adjust to the schema version of the events.

keyword

email.bcc.address

The email address of BCC recipient

keyword

email.cc.address

The email address of CC recipient

keyword

email.delivery_timestamp

The date and time when the email message was received by the service or client.

date

email.from.address

The email address of the sender, typically from the RFC 5322 From: header field.

keyword

email.local_id

Unique identifier given to the email by the source that created the event. Identifier is not persistent across hops.

keyword

email.message_id

Identifier from the RFC 5322 Message-ID: email header that refers to a particular email message.

wildcard

email.subject

A brief summary of the topic of the message.

keyword

email.subject.text

Multi-field of email.subject.

match_only_text

email.to.address

The email address of recipient

keyword

error.message

Error message.

match_only_text

event.action

The action captured by the event. This describes the information in the event. It is more specific than event.category. Examples are group-add, process-started, file-created. The value is normally defined by the implementer.

keyword

event.category

This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. event.category represents the "big buckets" of ECS categories. For example, filtering on event.category:process yields all events relating to process activity. This field is closely related to event.type, which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories.

keyword

event.created

event.created contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from @timestamp in that @timestamp typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent’s or pipeline’s ability to keep up with your event source. In case the two timestamps are identical, @timestamp should be used.

date

event.dataset

Event dataset

constant_keyword

event.end

event.end contains the date when the event ended or when the activity was last observed.

date

event.id

Unique ID to describe the event.

keyword

event.ingested

Timestamp when an event arrived in the central data store. This is different from @timestamp, which is when the event originally occurred. It’s also different from event.created, which is meant to capture the first time an agent saw the event. In normal conditions, assuming no tampering, the timestamps should chronologically look like this: @timestamp < event.created < event.ingested.

date

event.kind

This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. event.kind gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data is coming in at a regular interval or not.

keyword

event.module

Event module

constant_keyword

event.original

Raw text message of entire event. Used to demonstrate log integrity or where the full log message (before splitting it up in multiple parts) may be required, e.g. for reindex. This field is not indexed and doc_values are disabled. It cannot be searched, but it can be retrieved from _source. If users wish to override this and index this field, please see Field data types in the Elasticsearch Reference.

keyword

event.outcome

This is one of four ECS Categorization Fields, and indicates the lowest level in the ECS category hierarchy. event.outcome simply denotes whether the event represents a success or a failure from the perspective of the entity that produced the event. Note that when a single transaction is described in multiple events, each event may populate different values of event.outcome, according to their perspective. Also note that in the case of a compound event (a single event that contains multiple logical events), this field should be populated with the value that best captures the overall success or failure from the perspective of the event producer. Further note that not all events will have an associated outcome. For example, this field is generally not populated for metric events, events with event.type:info, or any events for which an outcome does not make logical sense.

keyword

event.risk_score

Risk score or priority of the event (e.g. security solutions). Use your system’s original value here.

float

event.sequence

Sequence number of the event. The sequence number is a value published by some event sources, to make the exact ordering of events unambiguous, regardless of the timestamp precision.

long

event.severity

The numeric severity of the event according to your event source. What the different severity values mean can be different between sources and use cases. It’s up to the implementer to make sure severities are consistent across events from the same source. The Syslog severity belongs in log.syslog.severity.code. event.severity is meant to represent the severity according to the event source (e.g. firewall, IDS). If the event source does not publish its own severity, you may optionally copy the log.syslog.severity.code to event.severity.

long

event.start

event.start contains the date when the event started or when the activity was first observed.

date

event.timezone

This field should be populated when the event’s timestamp does not include timezone information already (e.g. default Syslog timestamps). It’s optional otherwise. Acceptable timezone formats are: a canonical ID (e.g. "Europe/Amsterdam"), abbreviated (e.g. "EST") or an HH:mm differential (e.g. "-05:00").

keyword

event.type

This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. event.type represents a categorization "sub-bucket" that, when used along with the event.category field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types.

keyword

event.url

URL linking to an external system to continue investigation of this event. This URL links to another system where in-depth investigation of the specific occurrence of this event can take place. Alert events, indicated by event.kind:alert, are a common use case for this field.

keyword

file.hash.md5

MD5 hash.

keyword

file.hash.sha1

SHA1 hash.

keyword

file.hash.sha256

SHA256 hash.

keyword

file.inode

Inode representing the file in the filesystem.

keyword

file.name

Name of the file including the extension, without the directory.

keyword

file.size

File size in bytes. Only relevant when file.type is "file".

long

file.type

File type (file, dir, or symlink).

keyword

group.name

Name of the group.

keyword

host.architecture

Operating system architecture.

keyword

host.containerized

If the host is a container.

boolean

host.domain

Name of the domain of which the host is a member. For example, on Windows this could be the host’s Active Directory domain or NetBIOS domain name. For Linux this could be the domain of the host’s LDAP provider.

keyword

host.hostname

Hostname of the host. It normally contains what the hostname command returns on the host machine.

keyword

host.id

Unique host id. As hostname is not always unique, use values that are meaningful in your environment. Example: The current usage of beat.name.

keyword

host.ip

Host ip addresses.

ip

host.mac

Host mac addresses.

keyword

host.name

Name of the host. It can contain what hostname returns on Unix systems, the fully qualified domain name (FQDN), or a name specified by the user. The recommended value is the lowercase FQDN of the host.

keyword

host.os.build

OS build information.

keyword

host.os.codename

OS codename, if any.

keyword

host.os.family

OS family (such as redhat, debian, freebsd, windows).

keyword

host.os.kernel

Operating system kernel version as a raw string.

keyword

host.os.name

Operating system name, without the version.

keyword

host.os.name.text

Multi-field of host.os.name.

match_only_text

host.os.platform

Operating system platform (such centos, ubuntu, windows).

keyword

host.os.version

Operating system version as a raw string.

keyword

host.type

Type of host. For Cloud providers this can be the machine type like t2.medium. If vm, this could be the container, for example, or other information meaningful in your environment.

keyword

http.request.method

HTTP request method. The value should retain its casing from the original event. For example, GET, get, and GeT are all considered valid values for this field.

keyword

http.request.referrer

Referrer for this HTTP request.

keyword

input.type

Type of Filebeat input.

keyword

log.file.path

Full path to the log file this event came from, including the file name. It should include the drive letter, when appropriate. If the event wasn’t read from a log file, do not populate this field.

keyword

log.flags

Flags for the log file.

keyword

log.offset

Offset of the entry in the log file.

long

log.source.address

Source address of logs received over the network.

keyword

message

For log events the message field contains the log message, optimized for viewing in a log viewer. For structured logs without an original message field, other fields can be concatenated to form a human-readable summary of the event. If multiple messages exist, they can be combined into one message.

match_only_text

network.application

When a specific application or service is identified from network connection details (source/dest IPs, ports, certificates, or wire format), this field captures the application’s or service’s name. For example, the original event identifies the network connection being from a specific web service in a https network connection, like facebook or twitter. The field value must be normalized to lowercase for querying.

keyword

network.bytes

Total bytes transferred in both directions. If source.bytes and destination.bytes are known, network.bytes is their sum.

long

network.direction

Direction of the network traffic. When mapping events from a host-based monitoring context, populate this field from the host’s point of view, using the values "ingress" or "egress". When mapping events from a network or perimeter-based monitoring context, populate this field from the point of view of the network perimeter, using the values "inbound", "outbound", "internal" or "external". Note that "internal" is not crossing perimeter boundaries, and is meant to describe communication between two hosts within the perimeter. Note also that "external" is meant to describe traffic between two hosts that are external to the perimeter. This could for example be useful for ISPs or VPN service providers.

keyword

network.iana_number

IANA Protocol Number (https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml). Standardized list of protocols. This aligns well with NetFlow and sFlow related logs which use the IANA Protocol Number.

keyword

network.name

Name given by operators to sections of their network.

keyword

network.packets

Total packets transferred in both directions. If source.packets and destination.packets are known, network.packets is their sum.

long

network.protocol

In the OSI Model this would be the Application Layer protocol. For example, http, dns, or ssh. The field value must be normalized to lowercase for querying.

keyword

network.transport

Same as network.iana_number, but instead using the Keyword name of the transport layer (udp, tcp, ipv6-icmp, etc.) The field value must be normalized to lowercase for querying.

keyword

observer.egress.interface.name

Interface name as reported by the system.

keyword

observer.egress.zone

Network zone of outbound traffic as reported by the observer to categorize the destination area of egress traffic, e.g. Internal, External, DMZ, HR, Legal, etc.

keyword

observer.ingress.interface.name

Interface name as reported by the system.

keyword

observer.ingress.zone

Network zone of incoming traffic as reported by the observer to categorize the source area of ingress traffic. e.g. internal, External, DMZ, HR, Legal, etc.

keyword

observer.ip

IP addresses of the observer.

ip

observer.mac

MAC addresses of the observer. The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen.

keyword

observer.name

Custom name of the observer. This is a name that can be given to an observer. This can be helpful for example if multiple firewalls of the same model are used in an organization. If no custom name is needed, the field can be left empty.

keyword

observer.product

The product name of the observer.

keyword

observer.type

The type of the observer the data is coming from. There is no predefined list of observer types. Some examples are forwarder, firewall, ids, ips, proxy, poller, sensor, APM server.

keyword

observer.vendor

Vendor name of the observer.

keyword

observer.version

Observer version.

keyword

process.hash.md5

MD5 hash.

keyword

process.name

Process name. Sometimes called program name or similar.

keyword

process.name.text

Multi-field of process.name.

match_only_text

process.parent.hash.md5

MD5 hash.

keyword

process.parent.name

Process name. Sometimes called program name or similar.

keyword

process.parent.name.text

Multi-field of process.parent.name.

match_only_text

related.hash

All the hashes seen on your event. Populating this field, then using it to search for hashes can help in situations where you’re unsure what the hash algorithm is (and therefore which key name to search).

keyword

related.ip

All of the IPs seen on your event.

ip

related.user

All the user names or other user identifiers seen on the event.

keyword

rule.category

A categorization value keyword used by the entity using the rule for detection of this event.

keyword

rule.description

The description of the rule generating the event.

keyword

rule.id

A rule ID that is unique within the scope of an agent, observer, or other entity using the rule for detection of this event.

keyword

rule.name

The name of the rule or signature generating the event.

keyword

rule.ruleset

Name of the ruleset, policy, group, or parent category in which the rule used to generate this event is a member.

keyword

rule.uuid

A rule ID that is unique within the scope of a set or group of agents, observers, or other entities using the rule for detection of this event.

keyword

source.as.number

Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.

long

source.as.organization.name

Organization name.

keyword

source.as.organization.name.text

Multi-field of source.as.organization.name.

match_only_text

source.bytes

Bytes sent from the source to the destination.

long

source.domain

The domain name of the source system. This value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment.

keyword

source.geo.city_name

City name.

keyword

source.geo.continent_name

Name of the continent.

keyword

source.geo.country_iso_code

Country ISO code.

keyword

source.geo.country_name

Country name.

keyword

source.geo.location

Longitude and latitude.

geo_point

source.geo.name

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

keyword

source.geo.region_iso_code

Region ISO code.

keyword

source.geo.region_name

Region name.

keyword

source.ip

IP address of the source (IPv4 or IPv6).

ip

source.mac

MAC address of the source. The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen.

keyword

source.nat.ip

Translated ip of source based NAT sessions (e.g. internal client to internet) Typically connections traversing load balancers, firewalls, or routers.

ip

source.nat.port

Translated port of source based NAT sessions. (e.g. internal client to internet) Typically used with load balancers, firewalls, or routers.

long

source.packets

Packets sent from the source to the destination.

long

source.port

Port of the source.

long

source.user.domain

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

keyword

source.user.email

User email address.

keyword

source.user.group.name

Name of the group.

keyword

source.user.id

Unique identifier of the user.

keyword

source.user.name

Short name or login of the user.

keyword

source.user.name.text

Multi-field of source.user.name.

match_only_text

tags

List of keywords used to tag each event.

keyword

url.domain

Domain of the url, such as "http://www.elastic.co[www.elastic.co]". In some cases a URL may refer to an IP and/or port directly, without a domain name. In this case, the IP address would go to the domain field. If the URL contains a literal IPv6 address enclosed by [ and ] (IETF RFC 2732), the [ and ] characters should also be captured in the domain field.

keyword

url.original

Unmodified original url as seen in the event source. Note that in network monitoring, the observed URL may be a full URL, whereas in access logs, the URL is often just represented as a path. This field is meant to represent the URL as it was observed, complete or not.

wildcard

url.original.text

Multi-field of url.original.

match_only_text

user.domain

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

keyword

user.email

User email address.

keyword

user.group.name

Name of the group.

keyword

user.id

Unique identifier of the user.

keyword

user.name

Short name or login of the user.

keyword

user.name.text

Multi-field of user.name.

match_only_text

user_agent.name

Name of the user agent.

keyword

user_agent.original

Unparsed user_agent string.

keyword

user_agent.original.text

Multi-field of user_agent.original.

match_only_text

vulnerability.id

The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (Common[https://cve.mitre.org/about/faqs.html#what_is_cve_id)[Common Vulnerabilities and Exposure CVE ID]

keyword

Changelog

edit
Changelog
Version Details Kibana version(s)

1.34.4

Bug fix (View pull request)
Add instructions on using logfile input

8.11.0 or higher

1.34.3

Bug fix (View pull request)
Align hostname grok pattern with syslog RFC.

8.11.0 or higher

1.34.2

Bug fix (View pull request)
Use triple-brace Mustache templating when referencing variables in ingest pipelines.

8.11.0 or higher

1.34.1

Bug fix (View pull request)
Use triple-brace Mustache templating when referencing variables in ingest pipelines.

8.11.0 or higher

1.34.0

Enhancement (View pull request)
Drop support for EOL OS version R80.X

8.11.0 or higher

1.33.1

Enhancement (View pull request)
Improve normalization of user.name field

8.11.0 or higher

1.33.0

Enhancement (View pull request)
Allow @custom pipeline access to event.original without setting preserve_original_event.

8.11.0 or higher

1.32.0

Enhancement (View pull request)
Migrate log stream visualization to saved search.

8.10.1 or higher

1.31.1

Bug fix (View pull request)
Ensure event.original is always set to value of message.

8.6.0 or higher

1.31.0

Enhancement (View pull request)
Update package-spec to 3.0.3.

8.6.0 or higher

1.30.2

Enhancement (View pull request)
Changed owners

8.6.0 or higher

1.30.1

Bug fix (View pull request)
Add missing fields for audit log events.

8.6.0 or higher

1.30.0

Enhancement (View pull request)
Improve authentication logs normalization.

8.6.0 or higher

1.29.1

Bug fix (View pull request)
Fix exclude_files pattern.

8.6.0 or higher

1.29.0

Enhancement (View pull request)
ECS version updated to 8.11.0.

8.6.0 or higher

1.28.0

Enhancement (View pull request)
Improve event.original check to avoid errors if set.

8.6.0 or higher

1.27.0

Enhancement (View pull request)
ECS version updated to 8.10.0.

8.6.0 or higher

1.26.0

Enhancement (View pull request)
The format_version in the package manifest changed from 2.11.0 to 3.0.0. Removed dotted YAML keys from package manifest. Added owner.type: elastic to package manifest.

8.6.0 or higher

1.25.0

Enhancement (View pull request)
Add tags.yml file so that integration’s dashboards and saved searches are tagged with "Security Solution" and displayed in the Security Solution UI.

8.6.0 or higher

1.24.0

Enhancement (View pull request)
Ensure checkpoint.subs_exp is a date.

8.6.0 or higher

1.23.0

Enhancement (View pull request)
Update package to ECS 8.9.0.

8.6.0 or higher

1.22.0

Enhancement (View pull request)
Avoid data loss from updates with colliding loguid and timestamp.

8.6.0 or higher

1.21.0

Enhancement (View pull request)
Update package to ECS 8.8.0.

8.6.0 or higher

1.20.0

Enhancement (View pull request)
Update package-spec version to 2.7.0.

8.6.0 or higher

1.19.0

Enhancement (View pull request)
Update package to ECS 8.7.0.

8.6.0 or higher

1.18.0

Enhancement (View pull request)
Improve documentation.

8.6.0 or higher

1.17.0

Enhancement (View pull request)
Add dashboards.

8.6.0 or higher

1.16.1

Enhancement (View pull request)
Added categories and/or subcategories.

7.16.0 or higher
8.0.0 or higher

1.16.0

Enhancement (View pull request)
Add support for new R81 fields.

Enhancement (View pull request)
Enhance error handling.

Enhancement (View pull request)
Support logs with multiple time values.

Enhancement (View pull request)
Fingerprint events to prevent duplicate ingestion.

7.16.0 or higher
8.0.0 or higher

1.15.1

Bug fix (View pull request)
Fix Check Point src_user_name field mapping.

7.16.0 or higher
8.0.0 or higher

1.15.0

Enhancement (View pull request)
Enhance error handling.

7.16.0 or higher
8.0.0 or higher

1.14.0

Enhancement (View pull request)
Expose origin_sic_name field.

Enhancement (View pull request)
Improve structured data handling.

7.16.0 or higher
8.0.0 or higher

1.13.0

Enhancement (View pull request)
Improve support for Checkpoint 81.

7.16.0 or higher
8.0.0 or higher

1.12.0

Enhancement (View pull request)
Allow configuration of time zones.

7.16.0 or higher
8.0.0 or higher

1.11.0

Enhancement (View pull request)
Update package to ECS 8.6.0.

7.16.0 or higher
8.0.0 or higher

1.10.0

Enhancement (View pull request)
Add udp_options to the UDP input.

7.16.0 or higher
8.0.0 or higher

1.9.1

Bug fix (View pull request)
Support checkpoint.time field as both UNIX and UNIX_MS

7.16.0 or higher
8.0.0 or higher

1.9.0

Enhancement (View pull request)
Update package to ECS 8.5.0.

7.16.0 or higher
8.0.0 or higher

1.8.2

Enhancement (View pull request)
Remove duplicate field.

7.16.0 or higher
8.0.0 or higher

1.8.1

Enhancement (View pull request)
Use ECS geo.location definition.

7.16.0 or higher
8.0.0 or higher

1.8.0

Enhancement (View pull request)
Update package to ECS 8.4.0

7.16.0 or higher
8.0.0 or higher

1.7.1

Bug fix (View pull request)
Fix handling of R81 fields.

7.16.0 or higher
8.0.0 or higher

1.7.0

Enhancement (View pull request)
Add handling of authentication events.

7.16.0 or higher
8.0.0 or higher

1.6.1

Enhancement (View pull request)
Improve TCP, SSL config description and example.

7.16.0 or higher
8.0.0 or higher

1.6.0

Enhancement (View pull request)
Update package to ECS 8.3.0.

7.16.0 or higher
8.0.0 or higher

1.5.1

Enhancement (View pull request)
Update Checkpoint logo.

7.16.0 or higher
8.0.0 or higher

1.5.0

Enhancement (View pull request)
Add TLS and custom options support to TCP input.

7.16.0 or higher
8.0.0 or higher

1.4.0

Enhancement (View pull request)
Update to ECS 8.2 to use new email field set.

7.16.0 or higher
8.0.0 or higher

1.3.6

Bug fix (View pull request)
Fixed parsing error when logs have trailing spaces

7.16.0 or higher
8.0.0 or higher

1.3.5

Enhancement (View pull request)
Added link to check point documentation.

7.16.0 or higher
8.0.0 or higher

1.3.4

Bug fix (View pull request)
Change mapping type of checkpoint.source_object to keyword from integer.

7.16.0 or higher
8.0.0 or higher

1.3.3

Enhancement (View pull request)
Add documentation for multi-fields

1.3.2

Bug fix (View pull request)
Fix field mapping conflicts for checkpoint.icmp_type, checkpoint.icmp_code & checkpoint.email_recipients_num

1.3.1

Bug fix (View pull request)
Add Ingest Pipeline script to map IANA Protocol Numbers

7.16.0 or higher
8.0.0 or higher

1.3.0

Enhancement (View pull request)
Update to ECS 8.0

7.16.0 or higher
8.0.0 or higher

1.2.2

Bug fix (View pull request)
Regenerate test files using the new GeoIP database

7.16.0 or higher
8.0.0 or higher

1.2.1

Bug fix (View pull request)
Change test public IPs to the supported subset

1.2.0

Enhancement (View pull request)
Add 8.0.0 version constraint

7.16.0 or higher
8.0.0 or higher

1.1.2

Enhancement (View pull request)
Update Title and Description.

7.16.0 or higher

1.1.1

Bug fix (View pull request)
Fix logic that checks for the forwarded tag

1.1.0

Enhancement (View pull request)
Update to ECS 1.12.0

1.0.0

Enhancement (View pull request)
make GA

0.8.2

Enhancement (View pull request)
Convert to generated ECS fields

0.8.1

Enhancement (View pull request)
update to ECS 1.11.0

0.8.0

Enhancement (View pull request)
Update integration description

0.7.0

Enhancement (View pull request)
Set "event.module" and "event.dataset"

0.6.0

Enhancement (View pull request)
update to ECS 1.10.0 and syncing module changes

0.5.2

Enhancement (View pull request)
update to ECS 1.9.0

0.5.1

Bug fix (View pull request)
Change kibana.version constraint to be more conservative.

0.1.0

Enhancement (View pull request)
initial release