All Apps and Add-ons

Problems with OPSEC LEA

Said7
Explorer

Hello.

Our team update the version in Checkpoint from R77 to R80, The update failed and they did the roll back, but after that action we are not receiving logs from the device, we have the next error.

2019-02-05 00:58:37,468 +0000 log_level=ERROR, pid=16939, tid=Thread-1444, file=ta_opseclea_data_collector.py, func_name=get_logs, code_line_no=62 | [input_name="live_checkpoint_new" connection="checkpoint_fw_new" data="non_audit"]log_level=0 file:lea_loggrabber.cpp func_name:check_session_end_reason code_line_no:2159 :Session end reason: SIC ERROR 147 - SIC Error for lea: Authentication error

Thanks for your support.

regards.

0 Karma

harsmarvania57
Ultra Champion

Error clearly indicate that it is authentication problem SIC Error for lea: Authentication error , you need to ask your Network Admin to generate new one time password in Checkpoint and use that new password in Splunk OPSEC LEA connection configuration.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...