Deployment Architecture

OPSEC LEA Forwarder prerequisites

nickstone
Path Finder

What is the requirement for having a Light or Heavy Forwarder for the Checkpoint OPSEC LEA add-on?
Is it just so the the WebUI can be used to configure it?

If so, is there a way to bypass the WebUI configuration step and just use a regualar Universal Forwarder?

Tags (1)
0 Karma
1 Solution

araitz
Splunk Employee
Splunk Employee

No, we require heavy or light forwarder. There are several reasons for this, the main one being that in the future we intend to facilitate remote management and this would not be possible with the universal forwarder.

View solution in original post

0 Karma

araitz
Splunk Employee
Splunk Employee

No, we require heavy or light forwarder. There are several reasons for this, the main one being that in the future we intend to facilitate remote management and this would not be possible with the universal forwarder.

0 Karma

hassanali
Explorer

I can not find any documentation specifically addressing the install on a HF. I have gathered from reading answers by the community to not index on the HF (common sense but documentation does not address what to add in the inputs.conf), assuming the outputs.conf is straight forward but then the app configuration on the indexer is also not clear.

Get Updates on the Splunk Community!

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...