Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Simon_Moscovitz
Participant

Harmony SASE and Endpoint Security Signature Updates

Upon trialing SASE, Endpoint security will not allow signature updates at all. Even though there's a Check Point Updates - HTTPS bypass rule, it didnt seem to work, unless we added in *.checkpoint.com. 

0 Kudos
5 Replies
simonemantovani
MVP Gold
MVP Gold

The "Check Point Updates HTTPS bypass" should contains these FQDN (based on sk163595)

 

  • avupdates.checkpoint.com
  • secureupdates.checkpoint.com
  • updates.checkpoint.com

And here you should find the FQDN used by the Endpoint: So https://support.checkpoint.com/results/sk/sk83520.

So using that object seems to be not enough as reported by the Sks

 

0 Kudos
Simon_Moscovitz
Participant

Yes, but i would have thought that these exceptions should be in the bypass rules by default, not just the three. No?

0 Kudos
simonemantovani
MVP Gold
MVP Gold

Oh yes I agree with you, only Check Poinrt could give an explanation maybe.

0 Kudos
simonemantovani
MVP Gold
MVP Gold

taking a look about the threee FQDN included in the object you mentioned and the SKs I mentioned, they are used only by the security gateway and management ... so that object is not used and related to Endpoint upgrades

0 Kudos
Simon_Moscovitz
Participant

Acutally, I've just changed the rule to the destination being Checkpoint services updateable objects instead of the domain names, which seems to work, and is now dynamic!

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events