cancel
Showing results for 
Search instead for 
Did you mean: 
Active Contributor

McAfee Core Protection Triggered by LogMeIn

We get between 100 and 200 McAfee "Self Protection" events per 48 hours. It appears LogMeIn tries to access McAfee core files.

 

Event : Access Protection rule violation detected and blocked.

 

Source File Paths:

/Library/Application Support/LogMeIn/bin/LogMeIn.app/Contents/MacOS/

 

Target File Paths:

/usr/local/McAfee/fmp/var/

 

Target File:

FMP.db

 

Has anyone experienced this before? Does anyone know why LogMeIn would try to access Antivirus file locations? Does anyone know where within LogMeIn we can make exclusions to prevent having hundreds of these alerts per day?

4 REPLIES 4
LogMeIn Contributor

Re: McAfee Core Protection Triggered by LogMeIn

Hi Victor,

While I haven't heard of this issue previously, could you possibly exclude the "LogMeIn" folder completely from the scans?

Active Contributor

Re: McAfee Core Protection Triggered by LogMeIn

The issues isn't McAfee scanning LogMeIn, that would be a trivial exclusion as you suggested. It's actually LogMeIn that is trying to access a McAfee .db file.

 

Is there a way to exclude things from LogMeIn's side?

Active Contributor

Re: McAfee Core Protection Triggered by LogMeIn

Anyone from LogMeIn have any advice? 

LogMeIn Contributor

Re: McAfee Core Protection Triggered by LogMeIn

Were you also using the LMI Antivirus features there?  If so then that would explain the scans and conflicting messages you see.