Sandstorm testing

Haven't been able to get it trigger. Just had a system download 50 samples via Malshare over HTTP and not one got blocked by AV, or submitted to Sandstorm.... I just checked the the websites/sample downloads are all logged in the web access logs and logs looks like this sandbox="-"

Yeah but did those 'samples' from Malshare get picked up by the Anti Virus scan conducted by the proxy? And, what are the size of those samples? Do you have your Web Filter policies set to NOT SCAN files that are above a certain size? A full web filter log excerpt would be good.

So in the log snippet above, I see that the site is Malicious in reputation and that it falls into the URL category of Malicious Sites; which by default would be blocked based purely on this, even without Sandstorm. So testing with content from this site won't trigger SandStorm, as it doesn't even have a chance to trigger!

What we need is a site that's not classified as above, nor carries an already established reputation with Sophos and that the content downloaded if of type that SandStorm would want to hook into and detonate.

@Shai, this is going to fall back onto SophosLABS to provide a test site and/or file.

As if we (the community) find a good resource to test with, within 5 minutes of that test Sophos Reputation services will have marked it as bad and not need to send it o SandStorm for tssting purposes.

Then explain this one please. Only changes to the log were dstip, and the url for privacy.

2016:02:16-22:12:34 vpn httpproxy[8725]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="GET" srcip="10.1.0.133" dstip="MYCloudServersIP" user="" group="" ad_domain="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="6188032" request="0xe2bb8c00" url="MyCloudServerDomain/Sample1.exe" referer="" error="" authtime="0" dnstime="4194" cattime="737" avscantime="3002258" fullreqtime="10528753" device="0" auth="0" ua="Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0" exceptions="" category="9998" reputation="unverified" categoryname="Uncategorized" country="United States" content-type="application/octet-stream" sandbox="-"

You got me! This is where sgelbaum could comment best, we'd most likely require a sample of the file. I suspect due to the fact the AV scan yielded no local suspicious elements, and was clean then was not referred to SandStorm... but I'm not 100% sure this is the the workflow.

I believe that the u2d channels do not currently have the web definitions for sandboxing.
I believe that this should be resolved in next 24 hours.

Some people are finding that Sandstorm in web is working. It may be that those people have manually installed the definitions for Mail (see pinned thread). YMMV.

So the functionality is there - it is just that the scheduling of the the required data update did not match the beta start.

Michael Dunn: and you are telling us NOW? 1 week later after spending hours to try and test sandstorm? ...

What does it take for the AV engine to decide a file is a candidate for sandboxing? Personally I would hope that all EXE's downloaded from unrated sites would be submitted.....

With the current detection data, downloading an EXE from all but a few known, trusted providers will trigger the sandboxing process. Office documents and PDFs with active content such as macros or javascript will also.

The exact criteria will change as the threat landscape changes, which is why the detection is provided through the malware scanning engine and can be updated along with malware detection updates.

So, is it correct to say that sandboxing will not work for Web Filtering if AV Scanning is set to "Single" and "Avira" is selected as the 'Single scan engine' on the 'Scan Settings' tab?

Cheers - Bob

Then's there's an issue with this.... If you look at the Web log I pasted earlier, it was an EXE and from a "Uncatagorized" URL. For scanning, I am set to Single Engine: Sophos.......

Then's there's an issue with this.... If you look at the Web log I pasted earlier, it was an EXE and from a "Uncatagorized" URL. For scanning, I am set to Single Engine: Sophos.......

EricShulze - the answer to this is either a.) you still do not have the right 'Sophos Identities' loaded to perform Sandboxing, these will be released very soon. or; b.) Sophos Engine did not determine anything suspicious of the file and decided to not send it to sandbox.

I think A is the more likely answer here based on comments from Rich.

So for clarity, I need to follow the directions to copy/install that file that is mentioned to be needed for MAIL to get sandstorm to work for WEB? If that is the case, you may want to update the pinned post.

No. The Sophos Identities to trigger Sandstorm scanning in WEB have YET to be released! This was mentioned up the thread. Michael Dunn mentioned this and if all goes well, these should be published within 24 hours...