I have the above detection rule creating false positives and when checked, all the detections are for MSTSC.EXE. The triggering processes are mostly the browsers (chrome.exe). All the endpoints are user PCs. Is there a way to tune this rule to stop the false positives?