{"id":435,"date":"2010-05-05T08:50:17","date_gmt":"2010-05-05T08:50:17","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2010\/05\/05\/a-quick-guide-to-checkpoints-opsec-lea\/"},"modified":"2021-07-24T18:46:08","modified_gmt":"2021-07-24T18:46:08","slug":"a-quick-guide-to-checkpoints-opsec-lea","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Firewalls\/Check-Point\/a-quick-guide-to-checkpoints-opsec-lea.html","title":{"rendered":"A Quick Guide to Check Points OPSEC LEA"},"content":{"rendered":"

This guide will outline OPSEC LEA and how it works within a Check Point Infrastructure.<\/p>\n

What is OPSEC LEA ?
<\/strong><\/p>\n

The OPSEC LEA (Log Export API) provides the ability to pull logs from a Check Point device based on the OPSEC SDK. OPSEC LEA listens on port tcp\/18184 on the device (OPSEC LEA Server) which will contain your logs. Your OPSEC LEA Client will then connect into 18184 and pull the logs.<\/p>\n

Check Point Terms and Components<\/strong><\/p>\n

When configuring your software to pull logs using OPSEC LEA there are a few terms that you will need to know.<\/p>\n

The Check Point foundations<\/span><\/p>\n

The main components required for Check Point are:<\/p>\n