I would suggest to find the sample which is being blocked by the signature and check the verdict (you can upload it to the WildFire cloud to see the verdict). If it's benign, you can set an exception to allow the file temporarily as needed. It is called 'signature collision'.

The signature was created for a bunch of malware samples. We should keep the signature enabled instead of disabling it.
https://threatvault.paloaltonetworks.com/?query=479496371&type=

References:
- Manually Upload Files to the WildFire Portal
https://docs.paloaltonetworks.com/wildfire/9-1/wildfire-admin/submit-files-for-wildfire-analysis/man...

- What is an Antivirus collision in the case of a False Positive, and how can we deal with it?
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClWICA0

- How to Use Anti-Spyware, Vulnerability and Antivirus Exceptions to Block or Allow Threats
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClcrCAC

Thanks for replying! 

The issue we are facing is that in the Logs we are seeing it does not supply a file Hash or any other indication to which files are actively causing these alerts to occur, It only shows the application as MS-DS-SMBv3 which does not really sound correct. 

I will look into the AV collision to check if this is applicable.

Thanks, Matt.

Thanks @ymiyashita, After checking that last link you posted it explains why a lot of the information within the logs is missing and why it would be picked up as a virus within the firewall. 

There were no wildfire submissions related to the threat logs either so I suspect that a false positive is the case

Thanks again, Matt

Thanks for the solution, you made my day 🙂

Thanks for the link, you made my day.