FortiClient 6.4.3 detects remote.cmd.shell during SMB file copy to NAS
During a file copy of a vhdx file (Hyper-V VM HDD) to a NAS FortiClient suddenly terminates the connection, complaining about remote.cmd.shell detected. During the copy the FortiClient Firewall Service is actively checking the copy with high CPU usage. After the connection has been terminated, the drivemapping to the NAS is no longer accessible.
Why would the application firewall of FortiClient detect a remote.cmd.shell action during a regular file copy over SMB?
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.