Difference between Agent and Endpoint Security Product

[Labsy 0]

Hi,

In Protect Cloud I am creating installers for end-user's PCs, Laptops and Servers. Ok, I can imagine difference between PC and Server product, but installer offers me an option to create installer for Agent only or/and for Security product. I do not understand this concept - are both needed on endpoints, or just an Agent?

[Marcos 5,085]

Agent maintains the communication between the security product and the ESET PROTECT server. You can have Endpoint installed without the agent but it won't be centrally managed and report to ESET PROTECT.

[Labsy 0]

2 hours ago, Marcos said:

Agent maintains the communication between the security product and the ESET PROTECT server. You can have Endpoint installed without the agent but it won't be centrally managed and report to ESET PROTECT.

Hi Marcos,

thank you. What I forgot to mention is that one of ESET technicians prepared some installer for me and he said, there is no need to check "Security Product" checkbox when creating installer, which broke my understanding of concept. Does in case when installer only has AGENT checked, but no Security Product checkbox, then after installation endpoint somehow automagically downloads and installs security product as well?

[Marcos 5,085]

We recommend uninstalling ESET CyberSecurity as per the instructions at https://help.eset.com/ecs_mac/7/en-US/?uninstall.html:

To remove ESET Cyber Security, follow the steps below:

1.Launch Finder

2.Open the Applications folder on your hard drive.

3.Control-click (or right-click) the ESET Cyber Security icon.

4.Select Show Package Contents from the shortcut menu.

5.Open the Contents > Helpers folder and double-click the Uninstaller icon.

If you kept the ESET Cyber Security installation file (.dmg), open it and double-click Uninstall.

After uninstallation only quarantined files may be left on the disk.

[Labsy 0]

Sorry, obviously I did not explain my question well enough. I am asking about the differnece, if you prepare installer via Protect cloud WITH versus WITHOUT "Security Product". Because I can install only "Management Agent", but as far as I understand, "Agent" does not protect from viruses, malware etc. So what's the point of making installer for endpoint, which only has Agent? Furthermore, ESET technician told me I onl need to select checkbox beside "Managment Agent" and I should not select "Security Product" not "Disk Encryption", and endpoint will be fully protected.

That's what I do not understand - does Agent offer any kind of protection? Os is Security Product a must-have for the protection of endpoint? Meaning, ESET technician taught me wrong?

Edited July 30, 2023 by Labsy

[IggyPop 20]

Hi @Labsy,

I will try to answer on the questions above. The agent allows the communication betweeen the Server and the Endpoint Machine itself you can read more on this topic here, where a diagram will showcase the communication between these components.

In the second question the agent can be used for many different approaches and one of them is to create a templates based upon the dynamic groups. Some for example if you installa agent on a new machine and the agent reports back to the server that it doesn't have a security product it will fall into a group which you have defined and from there you can automatize the installation of the product of a specific type to this machine. For more I would recommend looking through the links I have provided above which can help you understand the whole process.

The difference between having a security product with the agent and not having it is that agent is lighter to be distributed on its own while if you add the product you increase the size of the installation package. However, on the other hand distributing the agent and having the automatization after can speed up your own process as well which can be helpful in larger networks. But I'm sure @Marcos can add some more pros and cons, as I have found these to be interesting to me.

Hope this will help you out!

Kind regards,

Iggy

[Labsy 0]

Hi @IggyPop, thank you very much, your explanation puts some broken ends together in my mind. Of which main point is that (lightweight) installer with agent only, can upon deployment on client's computer afterwards - depending on policy - download and (silently, in the background, without user interventioin?) install (by policy) choosen security product, so there is no need to pack the cesurity product into installer itself. 
This makes perfect sense to me.

Maybe just a sub-question as you mentioned Dynamic Groups:
In PROTECT CLOUD console I have COMPANIES, but under those I cannot create new company, just new Dynamic Group. Only MY OWN company is there, but if I re-sell products to another company, how and where can I add NEW COMPANY?

....or should I just create TAGS for new companies?

[IggyPop 20]

Hi @Labsy,

I would recommend you create a dynamic group under the company you are managing. I have it designed this way in my environment.

Thanks,

Iggy

[Labsy 0]

Thanx, I thought it is the way.... but it is a bit annoying, because installer and endpoint product in this case say, they are licensed on MY compnay, instead to END-USER's company. I am a kind of un-official sub-reseller, aka I buy from official reseller, then I have few dozens of my customer's companies which I manage.

Wondering, how did MY COMPANY get there on the list?

[IggyPop 20]

In my case I have an MSP Account created for this purpose as I thought you might a reseller or an MSP. If this is something interesting for you surely you can read more on this topic here. But you can also create a dynamic group on top of your already existing company or you can create a new static group. 

[Labsy 0]

Well, I have access to my BUSINESS ACCOUNT where all licenses are stored, and from there I have access to PROTECT CLOUD. So I guess I do not have MSP Account, but my top resseller does. So he should create compaines for me? Will ask him.

Thanx!