cancel
Showing results for 
Search instead for 
Did you mean: 

EPO 4.6.4 (build 202) -> SCRIPTSCAN exclusion not working

Jump to solution

EPO: 4.6.4

VIRUSSCAN: 8.8.0 (8.8.0.1128)-patch3

MCAFEE AGENT: 4.6.0.3122

In our internal network we are testing a webapplication.

https://testsite.company.com/web-site/frames.jsp

We recieve an SCRIPTING alert (see the attachment bellow).

Under EPO-VirusScan Enterprise 8.8.0 > On-Access General Policies > My Default/SCRIPTSCAN

We have added: https://testsite.company.com/web-site/frames.jsp.

Woke up agents for complete task/policy update.

Alert is still appearing

QUESTIONS:

* Any other proper suggestion?

* What's with the wildcards? Under scriptscan it saids:

with best regards,

Message was edited by: bostjanc on 6/10/13 2:02:18 PM GMT+01:00

Message was edited by: bostjanc on 6/10/13 2:02:34 PM GMT+01:00
1 Solution

Accepted Solutions

Re: EPO 4.6.4 (build 202) -> SCRIPTSCAN exclusion not working

Jump to solution

changes in the code of webbapplication did the trick.

4 Replies

Re: EPO 4.6.4 (build 202) -> SCRIPTSCAN exclusion not working

Jump to solution

Ok guys, anyone?

With best regards,

Tristan
Level 15
Report Inappropriate Content
Message 3 of 5

Re: EPO 4.6.4 (build 202) -> SCRIPTSCAN exclusion not working

Jump to solution

I would be more worried that your own code is being detected as an actual known exploit rather than generic script blocking but that's another question for another time.

A couple of thoughts

1. What are you testing it on? Don't forget that there are two places to put the exclusion one for workstations and one for servers

2. Aren't exclusions supposed to be just the domain name? https://kc.mcafee.com/corporate/index?page=content&id=KB65382

Re: EPO 4.6.4 (build 202) -> SCRIPTSCAN exclusion not working

Jump to solution

Our research department is developing some web applications.

I think they have solved it in the code, but I need to get info from a reasearcher whos is currently away.

i have excluded on workstations because currently then don't test it on servers.

Re: EPO 4.6.4 (build 202) -> SCRIPTSCAN exclusion not working

Jump to solution

changes in the code of webbapplication did the trick.