Introducing Endpoint Security Manager 3.2

Hi Guys n Gals,

So here it is Endpoint Security Manager version 3.2 with Comodo Endpoint Security version 8

FIRST THINGS FIRST -yes, this in bold caps for a reason

ESM 3.2 does not manage CES 6.4. If you upgrade to ESM 3.2 all your CES 6.4 installs will turn to ‘Unsupported’ in your management console.

ESM 3.1 does not manage CES 8 If you upgrade your CES 6.4 installs to CES 8 your endpoints will turn to ‘Unsupported’ in your management console.

Deployments of CES 8 can not be governed by CES 6.4 policies If you upgrade all your endpoints to CES 8 all of your legacy policies will be not be usable and you will have to recreate your policies.

Please consider carefully before upgrading and please only do so outside of production hours.

So, whats new (and why should I upgrade despite all of the above warnings)?

  • Selective CES component deployment - you can now choose to deploy only certain components of CES, such as Sandbox only, to run alongside an existing AV ‘solution’
  • Granular, rule-based Sandbox settings management via policies
  • Viruscope - application behavior analytics (launched from the Unrecognized Files manager)
  • File Groups - allowing Sandbox rules to be applied to groups of files
  • Registry Groups - allowing Sandbox rules to be applied to groups of registry object
  • CES Logging to 3rd party destinations - you can choose where the CES logs should be written for collection by your SIEM product or poush thelogs directly to a Syslog-style server
  • Unrecognized Files - you now have a new management console for reviewing any files detected in your environment which are ‘Unknown’
  • Observing Antivirus Events with Application activities - right from the Computer Properties screen you can see what AV events have taken place on the endpoint

These are all the major changes, as usual there are also a whole bunch of minor enhancements and bug-fixes. Release notes attached.

Go grab a copy of ESM from the 60-day/600-user trial here https://www.comodo.com/business-enterprise/cesm3/index_v2.php. If you are an existing ESM 3.x user you will get an on-screen notification of the upgrade’s availability and just follow the prompts …

Great chatting with you again and if you want to come and have a look at ESM 3.2 before committing to an upgrade, come and register here Comodo Business Security | Register today for Free Webinar

Quick question, if I may…are you using Comodo Antispam Gateway (Anti-spam | Cloud Based Spam Email Filter Security from Comodo - 2019) as a method to filter out infections coming in via email? Please let me know…

Chat more later :slight_smile:

All the best,
Michél

[attachment deleted by admin]

Congratulations…
Comodo ESM is best endpoint security manager products.

Br,
AhmetC

Hi Michel

Many congrats on new release. Just to say that there has been no update notification here in the UK…

In the black bar in your ESM 3.x console…? Nothing?

Ta Michel - no nothing apart from Silverlight logo. I went to Help ~ About too

BTW were you aware that intRAnet zone based Autosandbox rules seem have no effect?

Because of the way intranet is detected, I don’t think they actually can…

I’ve been trying to get this bug 1261 processed.

Maybe your QA guys could process it? The devs need to understand that they cannot (as far as I can see) pick up Zone 1 from alternate data streams.

Can you still deploy your 6.4 policies via the new interface?

Hi Silveringfox,

That would be a ‘no’. ESM 3.2 manages CES 8 and is unable to manage CES 6.4.

Kind regards,

Michel.

[at]mouse1 - please post the version of ESM 3 you are running…

<Edit 1>…also please let me know if you can get to https://downloads.comodo.com/cesm/download/updates/updates-pe.xml from your ESM server

<Edit 2> from the devs…"Actually this forum user is right, existing browsers (IE, Chrome, FF, Opera) and mail clients (Outlook, Thunderbird) doesn’t write this IntRAnet Zone ID to the files downloaded from Intranet. We verified this case here by manually set this Zone ID.

So we can call this behavior “known limitation”. We’re tried to overcame this limitation but didn’t find robust solution."

Is it possible to export my existing 3.1 policies to xml and then re-import into 3.2?

Hey Michael,

No, it isn’t. We are working on/testing a policy import tool. Watch this space for breaking news…

M.

OK I understand, though I think there is a way to do this, I give a procdump outline of the algorithm in the Bugzilla bug report 1261

Yes that was the problem sorry. I was running a slightly pre-release version of immediately previous public version. I resolved with Denis…

Congratulations!

In ESM 3.2, is this reported bug solved?
And any of this requests under this wishlist?

Hi w-e-v,

Ubuntu 14 is in testing and will be supported in the next release.

Due to the upcoming features we are doing for the above-mentioned next release (as exposed in the MSP board), we will not have the resource to do the other requests. We have put them in the dev queue for next year’s Q1 release though.

Kind regards,
Michél

Hi w-e-v

If I’m right these (the wishes at least) are still not in the tracker. Please would you report these and your bug above urgently in the tracker please? As a Star Group member that is part of the deal I’m afraid, you must report in the tracker!

That way you should also get automatic status updates.

If you have lost your tracker password please PM me.

Best wishes

Mike

Best wishes