This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

No signs of life of the Antivirus after a successful installation on Ubuntu 18.04

Edit:

eventually I do see signs of life:

However the ENDPOINT COMPLIANCE SCANNER REPORT doesn't detect anything:

-----------------------------------------------

Hi,

I've installed it by running the script, answered all questions and even saw it prints that installation is complete and my computer is protected.

however I fail to see any signs of life in running processes, even after reboot.

Also a certain endpoint (of Checkpoint company) fails to detect any Antivirus on the system.

This thread was automatically locked due to age.

Parents

0 Shweta over 3 years ago

Hi Leonid Brandes

Would you please refer to this document and see if it helps.

Shweta

Community Support Engineer | Sophos Technical Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 Leonid Brandes over 3 years ago in reply to Shweta

Thanks, I've tried and I see the expected output (version 9.16.0).

So My issue with the the local end point seciruty SW which doesn't detect it probably has to do with other system components and I'll apply to those.

Thanks you!
Cancel
Vote Up 0 Vote Down

Cancel
0 Shweta over 3 years ago in reply to Leonid Brandes

Hi There,

Sure, please let us know how it goes.

Shweta

Community Support Engineer | Sophos Technical Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 MEric over 3 years ago in reply to Leonid Brandes

I noticed that your Checkpoint endpoint compliance scanner rule is specific to Mac based on the name. This rule may have been configured specifically for macs and the check does not properly apply to Linux machines. Just something that may be causing it.
Cancel
Vote Up 0 Vote Down

Cancel
0 Leonid Brandes over 3 years ago in reply to MEric

Yes, I've noticed it too.
Officially they support only Win and Mac.

I've hoped the Mac is similar enough seeing as it suggested Linux A/V's.

Unfortunately that's not the case.

Thank you for support, appreciate it, especially as it is a free product.
Cancel
Vote Up 0 Vote Down

Cancel
0 QC over 3 years ago in reply to Leonid Brandes

Hello Leonid Brandes,

Officially they support only Win and Mac (bold emphasis mine)
well, whoever they are, they don't support Linux. And if you could get away with mimicking a Mac AV (or protection suite) then I'd not really trust this Compliance Scanner. Disquieting enough it didn't say Unsupported (or unwanted) OS in the first place.

Christian
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 QC over 3 years ago in reply to Leonid Brandes

Hello Leonid Brandes,

Officially they support only Win and Mac (bold emphasis mine)
well, whoever they are, they don't support Linux. And if you could get away with mimicking a Mac AV (or protection suite) then I'd not really trust this Compliance Scanner. Disquieting enough it didn't say Unsupported (or unwanted) OS in the first place.

Christian
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data