You are viewing docs on Elastic's new documentation system, currently in technical preview. For all other Elastic docs, visit elastic.co/guide.

Imperva

Collect logs from Imperva devices with Elastic Agent.

Version
1.0.1 (View all)
Compatible Kibana version(s)
8.10.1 or higher
Supported Serverless project types

Security
Observability
Subscription level
Basic
Level of support
Elastic

This integration is for Imperva device logs. It includes the datasets for receiving logs over syslog or read from a file:

  • securesphere dataset: supports Imperva SecureSphere logs.

Data streams

The Imperva integration collects one type of data: securesphere.

Securesphere consists of alerts, violations, and system events. See more details about alerts, violations, and events

Requirements

Elastic Agent must be installed. For more information, refer to the link here.

Installing and managing an Elastic Agent:

You have a few options for installing and managing an Elastic Agent:

With this approach, you install Elastic Agent and use Fleet in Kibana to define, configure, and manage your agents in a central location. We recommend using fleet management because it makes the management and upgrade of your agents considerably easier.

Install Elastic Agent in standalone mode (advanced users):

With this approach, you install Elastic Agent and manually configure the agent locally on the system where it’s installed. You are responsible for managing and upgrading the agents. This approach is reserved for advanced users only.

Install Elastic Agent in a containerized environment:

You can run Elastic Agent inside a container, either with Fleet Server or standalone. Docker images for all versions of Elastic Agent are available from the Elastic Docker registry, and we provide deployment manifests for running on Kubernetes.

There are some minimum requirements for running Elastic Agent, and for more information, refer to the link here.

The minimum kibana.version required is 8.10.1.

Setup

To collect data from Imperva, follow the required steps:

  1. The gateway and management server (MX) should have the relevant connectivity for sending logs using the Syslog server.

  2. To send all security violations from the gateway to Elastic:

  • Create a custom action set:

    • From a 'security violation–all', type and add the gateway security system log > gateway log security event to system log (syslog) using the CEF standard.
    • Configure the relevant name and parameters for the action set.
  • Assign a followed action to a security - > policy rule.

  1. To send all security alerts (aggregated violations) from the gateway to Elastic:
  • Create a custom action set:

    • From an 'any event type', type and add the server system log > log security event to system log (syslog) using the CEF standard.
    • Configure the relevant name and parameters for the action set.
  • Assign a followed action to a security - > policy rule.

  1. To send all system events from the gateway to Elastic:
  • Create a custom action set:

    • From an 'any event type', type and add the server system log > log system event to system log (syslog) using the CEF standard.
    • Configure the relevant name and parameters for the action set.
  • Create system events policy.

  • Assign a followed action to a system event policy.

For more information on working with action sets and followed actions, refer to the Imperva relevant documentation.

Enabling the integration in Elastic:

  1. In Kibana, go to Management > Integrations
  2. In the "Search for integrations" search bar, type Imperva.
  3. Click on the "Imperva" integration from the search results.
  4. Click on the "Add Imperva" button to add the integration.
  5. Enable the data collection mode from the following: Filestream, TCP, or UDP.
  6. Add all the required configuration parameters, such as paths for the filestream or listen address and listen port for the TCP and UDP.

Logs Reference

SecureSphere

This is the Securesphere dataset.

Example

An example event for securesphere looks as following:

{
    "@timestamp": "2023-10-05T18:33:02.000Z",
    "agent": {
        "ephemeral_id": "94608df6-6778-4ec4-99dc-d0cd37d583d8",
        "id": "0412638f-dd94-4c0e-b349-e99a0886d9f0",
        "name": "docker-fleet-agent",
        "type": "filebeat",
        "version": "8.10.1"
    },
    "data_stream": {
        "dataset": "imperva.securesphere",
        "namespace": "ep",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "0412638f-dd94-4c0e-b349-e99a0886d9f0",
        "snapshot": false,
        "version": "8.10.1"
    },
    "event": {
        "agent_id_status": "verified",
        "code": "User logged in",
        "dataset": "imperva.securesphere",
        "ingested": "2023-12-01T09:10:18Z",
        "kind": "event",
        "original": "\u003c14\u003eCEF:0|Imperva Inc.|SecureSphere|15.1.0|User logged in|User admin logged in from 81.2.69.142.|High|suser=admin rt=Oct 05 2023 18:33:02 cat=SystemEvent",
        "severity": 7
    },
    "imperva": {
        "securesphere": {
            "device": {
                "event": {
                    "category": "SystemEvent",
                    "class_id": "User logged in"
                },
                "product": "SecureSphere",
                "receipt_time": "2023-10-05T18:33:02.000Z",
                "vendor": "Imperva Inc.",
                "version": "15.1.0"
            },
            "name": "User admin logged in from 81.2.69.142.",
            "severity": "High",
            "source": {
                "user_name": "admin"
            },
            "version": "0"
        }
    },
    "input": {
        "type": "udp"
    },
    "log": {
        "source": {
            "address": "192.168.249.7:48857"
        }
    },
    "message": "User admin logged in from 81.2.69.142.",
    "observer": {
        "product": "SecureSphere",
        "vendor": "Imperva Inc.",
        "version": "15.1.0"
    },
    "related": {
        "user": [
            "admin"
        ]
    },
    "source": {
        "user": {
            "name": "admin"
        }
    },
    "tags": [
        "preserve_original_event",
        "preserve_duplicate_custom_fields",
        "forwarded",
        "imperva.securesphere"
    ]
}

Exported fields

FieldDescriptionType
@timestamp
Event timestamp.
date
data_stream.dataset
Data stream dataset.
constant_keyword
data_stream.namespace
Data stream namespace.
constant_keyword
data_stream.type
Data stream type.
constant_keyword
event.dataset
Event dataset.
constant_keyword
event.module
Event module.
constant_keyword
imperva.securesphere.destination.address
ip
imperva.securesphere.destination.port
long
imperva.securesphere.destination.user_name
keyword
imperva.securesphere.device.action
keyword
imperva.securesphere.device.custom_string1.label
keyword
imperva.securesphere.device.custom_string1.value
keyword
imperva.securesphere.device.custom_string2.label
keyword
imperva.securesphere.device.custom_string2.value
keyword
imperva.securesphere.device.custom_string3.label
keyword
imperva.securesphere.device.custom_string3.value
keyword
imperva.securesphere.device.custom_string4.label
keyword
imperva.securesphere.device.custom_string4.value
keyword
imperva.securesphere.device.custom_string5.label
keyword
imperva.securesphere.device.custom_string5.value
keyword
imperva.securesphere.device.event.category
keyword
imperva.securesphere.device.event.class_id
keyword
imperva.securesphere.device.product
keyword
imperva.securesphere.device.receipt_time
date
imperva.securesphere.device.vendor
keyword
imperva.securesphere.device.version
keyword
imperva.securesphere.name
keyword
imperva.securesphere.severity
keyword
imperva.securesphere.source.address
ip
imperva.securesphere.source.port
long
imperva.securesphere.source.user_name
keyword
imperva.securesphere.transport_protocol
keyword
imperva.securesphere.version
keyword
input.type
Type of filebeat input.
keyword
log.file.device_id
ID of the device containing the filesystem where the file resides.
keyword
log.file.fingerprint
The sha256 fingerprint identity of the file when fingerprinting is enabled.
keyword
log.file.idxhi
The high-order part of a unique identifier that is associated with a file. (Windows-only)
keyword
log.file.idxlo
The low-order part of a unique identifier that is associated with a file. (Windows-only)
keyword
log.file.inode
Inode number of the log file.
keyword
log.file.vol
The serial number of the volume that contains a file. (Windows-only)
keyword
log.offset
Log offset.
long
log.source.address
Source address from which the log event was read / sent from.
keyword
tags
User defined tags.
keyword

Changelog

VersionDetailsKibana version(s)

1.0.1

Enhancement View pull request
Changed owners

8.10.1 or higher

1.0.0

Enhancement View pull request
Release package as GA.

8.10.1 or higher

0.20.2

Bug fix View pull request
Fix exclude_files pattern.

0.20.1

Bug fix View pull request
Adapt fields for changes in file system info.

0.20.0

Enhancement View pull request
ECS version updated to 8.11.0.

0.19.0

Enhancement View pull request
Replace RSA2ELK with Syslog integration.

0.18.0

Enhancement View pull request
ECS version updated to 8.10.0.

0.17.0

Enhancement View pull request
Update package to ECS 8.9.0.

0.16.0

Enhancement View pull request
Ensure event.kind is correctly set for pipeline errors.

0.15.0

Enhancement View pull request
Update package to ECS 8.8.0.

0.14.0

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

0.13.0

Enhancement View pull request
Update package to ECS 8.7.0.

0.12.0

Enhancement View pull request
Update package to ECS 8.6.0.

0.11.2

Bug fix View pull request
Update docs to match field definitions.

0.11.1

Bug fix View pull request
Remove duplicate fields.

0.11.0

Enhancement View pull request
Update package to ECS 8.5.0.

0.10.1

Enhancement View pull request
Use ECS geo.location definition.

0.10.0

Enhancement View pull request
Update package to ECS 8.4.0

0.9.0

Enhancement View pull request
Update package to ECS 8.3.0.

0.8.0

Enhancement View pull request
Update to ECS 8.2.0

0.7.0

Enhancement View pull request
Update to ECS 8.0.0

0.6.1

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

0.6.0

Enhancement View pull request
Add 8.0.0 version constraint

0.5.4

Enhancement View pull request
Uniform with guidelines

0.5.3

Enhancement View pull request
Update Title and Description.

0.5.2

Bug fix View pull request
Fixed a bug that prevents the package from working in 7.16.

0.5.1

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

0.5.0

Enhancement View pull request
Update to ECS 1.12.0

0.4.3

Bug fix View pull request
Requires version 7.14.1 of the stack

0.4.2

Enhancement View pull request
Convert to generated ECS fields

0.4.1

Enhancement View pull request
update to ECS 1.11.0

0.4.0

Enhancement View pull request
Update integration description

0.3.0

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

0.2.0

Enhancement View pull request
update to ECS 1.10.0 and adding event.original options

0.1.4

Enhancement View pull request
update to ECS 1.9.0

0.1.0

Enhancement View pull request
initial release

On this page