MALWARE AND CONTENT SCANNING

the course is saying that its recommended to use "Malware and content scanning" instead of "Filtering common web ports" So ive done some testing to check if malware will be blocked if i'll set only "malware and content scanning" unfortunately, files sended with no  problem. Ive attached screens from policy of FW rule and ssl/tls rule. Also ive added via Console non-standard port for https and ftp <- but ftp is a different story. 

 

 

BUT if im setting options below(screenshot) it does working. Tested malware are blocked and i can see it in the LOGS.

  • Roman,

    I tried with eicar, and in my case, XG stops the files with both DPI or Proxy mode.

    Were yours an update from beta or a new installation?

  • In reply to lferrara:

    I was upgrading it from SFOS 17.5.9 MR-9 to 18 ;)

    I assume that DPI - you have toggled only thoe options as below ? 

    I have done some testing and Malware is blocked only if the security settings are as below, ive try different options but no luck... Im not sure if it must working as is below. Regarding to courses - i think that not ;)

  • In reply to Roman klisiewicz:

    Roman,

    the configuration are fine. On my box, malwares are stopped. Can you check that the IPS service is on inside System Services menu?

  • In reply to lferrara:

    Yes. IPS service is up and running. ;) I 'll reboot today the fw - you know sometimes it helps :D

  • In reply to Roman klisiewicz:

    Can you determine if malware is allowed through on HTTP and HTTPS?  Or if it is blocked on HTTP but not HTTPS.  

  • In reply to Badrobot:

    Well, i dont really understand what are you asking for. If im undertstanding you correctly then - My service is working on non-standard HTTPS port(8443) Im not using unencrypted traffic to my server. How i did my testing ? From my PHONE(WAN - PublicIP_LTE) ive lunched an up (QFILE) and uploading a tested malware file, THATS ALL ;) all the rest as metnioned above ^^

  • In reply to Roman klisiewicz:

    The Proxy is only used for Internal to external communication.

    You cannot rely on the Proxy for external to internal communication.

    For such services, you need a reverse proxy (WAF).

    So you need to configure the WAF. 

  • In reply to LuCar Toni:

    Really a WAF ? 8443 is used for various services in this case im using for a file transfer. Im using DDNS service example: "somename.ddns.myqnapcloud.com" or "somename.ddns.net" all is on port 8443. this port is also used for managment,  server is a QNAP DEVICE. ;) If should using WAF can you point for some "hot to" ? ;)

  • In reply to Roman klisiewicz:

    Roman, Luca is correct. Traffic from lan to wan is filtered by proxy. From wan to lan by reverse proxy. This is not a Sophos limitation but how the protocol works.

    You can filter and apply Ips filter from lan to wan and viceversa but ips can stop only certain malware.

  • In reply to lferrara:

    Really. So you are tring to say im not able to bloc or scan a traffic from WAN to LAN on a specific port ?? I dont wanna to advertised other solution but on FORTIGATE devices it works excelent so "limitations is not cuzed by a protocol" beside that. So why malware is blocked when im not using DPI but only Webproxy and im uploading  a file from WAN. ? Cant it be done by WAF ? Sophos XG which im using is for HOME USAGE. So im ok if ssl traffic from will inspected via cert from sophos appliance_CA

  • In reply to Roman klisiewicz:

    Roman on Fortigate you can scan: http, imap,pop3, smtp,smb,ftp and nntp.

  • In reply to lferrara:

    Vote the feature request I opened a couple of years ago:

  • In reply to lferrara:

    I can ensure you that not only. ^^ but other then that. Can you also help me with FTPS that isnt scanned by any of sophos engine ? very appreciate fo your spended time for my help :) FTP is setup on FTPS port 990 and im getting error SSL handshake timed out.. for both scanners dpi and webproxy

  • In reply to Roman klisiewicz:

    If it is SFTP, you will need to decrypt the traffic first with XG in order to scan it.

    Also if you want FTP traffic to be scanned by XG, you will need to run the FTP server over the default port (21). XG is only port agnostic for HTTP traffic, if you run FTP over a non-standard port, It will not detect it as FTP, hence it will not scan it.

     

    Thanks!

  • In reply to Prism:

    So if im using ftps on 21 xg will not scan it?