Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

HOWTO: Verifying whether Checkpoint is using a SHA-1 or SHA-256 certificate

Expand / Collapse


This article applies to:

  • SIEM
  • Checkpoint firewalls

Question:

How can I verify whether Checkpoint is using a SHA-1 or SHA-256 certificate?

 

Procedure:

The current version of the OPSEC SDK only supports certificates generated with SHA-1. If the Checkpoint device is using a SHA-256 certificate, SIEM will not be able to retrieve logs.

To verify whether Checkpoint is using SHA 1 or SHA 256, in the Checkpoint command line interface, run the following command:

grep ":signature_hash" $FWDIR/conf/InternalCA.C

  • If the result returns no output, the Checkpoint device is using a SHA-1 certificate.
  • If the result returns any output, the Checkpoint device is using a SHA-256 certificate.
  • In this case, to retrieve logs with SIEM it is necessary to re-generate a SHA-1 certificate in Checkpoint, and then recreate the opsec application.

Notes:

  • Trustwave plans to update the OPSEC SDK to support SHA-256. For more information, contact Trustwave TAC.
  • Use of SHA-1 for this purpose does not affect compliance.

 


To contact Trustwave about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.