esetusersomethingorother

Is there something I missed in the config to force my ERA server to grab updates from ESET over an encrypted connection? Right now, all the communication appears to be happening over port 80. If this is normal behavior, doesn't anyone have any concerns regarding the integrity of their signatures being delivered in this manner? I'm really surprised a security product like this doesn't force all traffic over TLS (1.2, at that).

The answer to that question baffles me, as it appears they've eliminated the syslog option in 6.x. I'm honestly surprised it isn't asked more frequently. Anyone who has to deal with compliance and requires enterprise-level SIEM knows that lack of being able to send the logs somewhere or ingest them from a readable file creates a bit of a liability and does nothing more than make life more difficult for security professionals. The only thing I can tell you is that the product isn't designed for enterprise deployment. ...and if someone from ESET replies to this and says you need to back-rev to 5.x to get syslog support, I'm going to flip my lid.