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?
How to prevent such (false?) warnings?
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
From the logs...
msg="Traffic log" sessionid=12345 srcip=x.x.x.x srcport=58664 direction=outbound dstip=y.y.y.ydstport=445 proto=6 rcvdbyte=0 sentbyte=0 utmaction=blocked utmevent=appfirewall
threat=Remote.CMD.Shell service=microsoft-ds userinitiated=0 browsetime=0
Hi
same behavior here with FortiClient 7.0.8. Did you found any solution? I wan't to copy a virtual machine.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1692 | |
1087 | |
752 | |
446 | |
228 |
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.
Copyright 2024 Fortinet, Inc. All Rights Reserved.