Video Screencast Help

Add/Update Known Security Risk Exceptions Entries

Created: 04 Jan 2008 • Updated: 21 May 2010 | 4 comments
Hi
 
I am having trouble in the Centralized Exceptions Section of the  SEPM Console..
The Known Security Risk Exceptions Entries seem to be missing quiet a lot of security risk entries eg HackTool.HideWindow
SecurityRisk.cmdow
 
How would i Add/Update the Known Security Risk Exceptions Entries
 
btw
I can see all or a whole lot more Known Security Risk Exceptions Entries on the Endpoint Client
Endpoint Client>Change Settings>Centralized Exceptions Configure Settings>Add >Security Risk Exceptions>Know Risks
 
Many Thanks

Comments 4 CommentsJump to latest comment

suprman's picture
i have the same problem... im trying to include the SecurityRisk.Aports.... but isnt listed on manager.... but on the client is there.... i opened a case... but without solution

case: 290-908-316

 

 

im thinking that isnt a got ideia migrate to sep 11

 

 

bhuvaneshkr's picture
Even i have the same problem..Iam not able to see any security risk exceptions in the SEP manager , but security risk exceptions  are listed in the clients... I searched in the symantec knowledge base , but nothing useful is pulling out.. Please help...Thanks in advance



Message Edited by bhuvaneshkr on 03-03-2008 12:16 PM

Message Edited by bhuvaneshkr on 03-03-2008 12:20 PM

moosae's picture
Hi Guys,
 
I have just installed MR1,and was able to add an exception using a round about way...
via using the monitor tab ,then view logs >run Risk Log. I then added the results of the risk log,  in my case Security.cmdow to Centralized Exception Policy.
Installing MR1 over does can cause other stuff to stop functioning
Now Awaiting MR2.........
Scott K's picture
Hi,
I'm having the exact same problem at 2 of my sites.  I have opened a case with Symantec support and they don't have the answer yet.  Both these were fresh installs so it appears to be a bug in the program.  If support comes up with the solution I will post it here.  Anyone else open a case on this?  My tech. says he has not seen this before.
Scott