Cortex XDR: minimal exceptions for a dev team (Visual Studio / IntelliSense slow in POC)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Cortex XDR: minimal exceptions for a dev team (Visual Studio / IntelliSense slow in POC)

L0 Member

Hi all,

We’re running a POC of Cortex XDR (tenant v6.0, Windows agent 9.3.0.231). One dev team is included, and they report that Visual Studio is slow. IntelliSense autocompletion can take up to 10 seconds.

We want to fix this while keeping security coverage as high as possible, so we only want to exclude what is necessary.
So, which exception type is recommended for developers team? Which processes and folder needs to be excluded? 

Thanks in advance. 

1 REPLY 1

L7 Applicator

Hello @D.Antic ,

 

Greetings for the day.

 

To address Visual Studio performance issues, such as IntelliSense latency and file-locking overhead, we recommend using targeted Agent Exceptions rather than Alert Exclusions.

 

Recommended Exceptions:

  1. Process-Based Exceptions: Consider targeted exceptions for the following development processes:
    • devenv.exe
    • MSBuild.exe
    • msvsmon.exe
    • VsDebugConsole.exe
    • git.exe (if required).

  2. Behavioral and Exploit Protection: Apply process-level exceptions only where necessary and after validating the performance impact. Avoid broadly disabling protection modules.

  3. Further Investigation: If performance issues persist after applying targeted exceptions, engage Palo Alto Networks Support to evaluate a Support Exception (SUEX) for event collection or process-trust optimization.

Important Recommendations:

  • Prefer targeted, absolute-path exclusions over broad drive-level exclusions.
  • Avoid excluding entire Visual Studio installation or repository trees unless justified by testing.
  • Retain core security protections wherever possible.
  • Restart Visual Studio or the endpoint after policy changes, if required.

Conclusion: We recommend starting with narrowly scoped folder and process exceptions, monitoring IntelliSense performance, and expanding exclusions only when necessary to maintain the right balance between developer productivity and endpoint security.

 

If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution".

 

Thanks & Regards,
S. Subashkar Sekar

  • 92 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!