How to prevent virus to be copied from SMB share

[Robert_Cerny]

Hi,

I stored an eicar.txt file on the samba share (Windows 2080 R2 Server) and tried to copy it to my mac and it was copied without issues. Server and my test mac are connected using IPSec through two FGs, both ends have AV scanning on. Why wasn't the test file caught?

Thanks

Robert

[tanr]

Have you configures for CIFS/SMB/SAMBA virus scanning per https://docs.fortinet.com/document/fortigate/6.0.0/handbook/488541/windows-file-sharing-cifs?

Note that this only works for flow based.

[Robert_Cerny]

Actually it's CIFS not samba in the newest FortiOS but yes, I have it enabled and the correct AV profile assigned to firewall rule. Inspection mode is Flow based. Could the IPSec make the difference? 

[tanr]

It looks like CIFS filtering changed in 6.2.  We're not on 6.2, but the 6.2 docs have two sections:

https://docs.fortinet.com/document/fortigate/6.2.0/cookbook/186160/cifs-support

https://docs.fortinet.com/document/fortigate/6.2.0/new-features/409833/cifs-support

These imply that now CIFS filtering requires proxy mode instead of flow, a separate cifs-profile, and a domain controller if CIFS traffic is encrypted.

Be interested to hear if this works in 6.2 if you change to proxy, as we have this set up for flow in 6.0.

[Robert_Cerny]

Hi,

it works in proxy mode.

I didn't test that domain controller feature as encrypted CIFS is not used in our organization.

**EDIT**

oops, it looks like Win10 use encrypted CIFS by default.

Thanks a lot for your help

Robert

[Robert_Cerny]

Hi,

for the sake of archive... I created a domain controller for CIFS of "replication type" and it works great for all Windows users, but is a huge headache for MacOS users and FG. Every mount of shared volume from Windows server on Mac creates thousands of sessions that practically takes FG to its knees, eating up all the memory.

Currently have an open ticket with support.

Robert