Script Scan benefits

[HugsNotDrugs]

Can someone please explain to me what benefits is script scan providing to the IE users? I have read the user guide description but I'm still a bit puzzled on how should I understand it. Is ENS scanning more files when user is browsing internet with IE then  Chrome for example or is it just that in IE the scripts are scanned earlier? Are those same scripts scanned when a web page is opened in Chrome? What if I run Profiler and open a webpage in IE and later in Chrome - will the result be the same if the web page is using scripts? Thank you in advance for any explanation provided on this matter.

[Former Member · Accepted solution]

Script scanner is used for intercepting/ scanning of scripts run by Internet Explorer before they are executed on the endpoint.

When using any other browser, our script scanner isn't embedded so any website which have a script embedded won't be scanned. Whereas with IE the script scanner would first examine the nature of the script and check it's not malicious prior to executing it.

It is also important to note that it doesn't look at scripts system-wide and doesn't examine scripts run by wscript.exe or cscript.exe.

Profiler should only be used for OAS scanning - script scanning is a separate component.

[HugsNotDrugs]

Can you think of an explenation why Profiler is registering more js. files being scanned when opening the same web page in IE in comparesing to Chrome? If the Script Scan is not involved, what else could it be? I dont know much about web page design. Is it possible a web page uses different js. files for IE and Chrome and thus we recieve different OAS scanning results with Profiler?