I guess I should look at my Security history more often. I just noticed I am getting frequent "Unauthorized Access Logged" messages under "Notrton Product Tamper Protection". The actor is always c:\program file\logitech\setpoint\setpoint.exe. The target and frequency vary. Currently the target is mcui32.exe, and it happens every few minutes. If I look back in the history ccsvchst.exe has also been the target. Is this something I should worry about?
Richard
Richard, the setpoint.exe messages were previously discussed in this thread. If you don't like seeing the messages in your logs you may wish to read that thread.
Reese,
I also get the "unauthorized access" messages about a different software which is "safe" - sometimes 2-20 per hour. Is there a way to reduce the reporting frequency so that the History file does not grow as tall as Mount Everest? It's a bit annoying, as it slows the History load time even more than it is!
Tnx,
Airblower :-)
Reese. Thanks. I found it already. See this very recent thread:
http://community.norton.com/t5/Norton-Internet-Security-Norton/I-m-having-trouble-with-SetPoint-again/td-p/194968
It would be nice if there were a Norton setting that would stopping it from filling up my history though.
Richard
Airblower wrote:
Reese,
I also get the "unauthorized access" messages about a different software which is "safe" - sometimes 2-20 per hour. Is there a way to reduce the reporting frequency so that the History file does not grow as tall as Mount Everest? It's a bit annoying, as it slows the History load time even more than it is!
Tnx,
Airblower :-)
Airblower, I'm sorry but there is no squelching logic for this reporting.
I guess I should look at my Security history more often. I just noticed I am getting frequent "Unauthorized Access Logged" messages under "Notrton Product Tamper Protection". The actor is always c:\program file\logitech\setpoint\setpoint.exe. The target and frequency vary. Currently the target is mcui32.exe, and it happens every few minutes. If I look back in the history ccsvchst.exe has also been the target. Is this something I should worry about?
Richard