Best practices for MVISION EDR policy data collection
I am trying to figure out a good way to streamline my EDR collection policies. I can't decide what elements to collect and which to disable for systems that are in "normal state". I of course have a policy with all collection enabled (trace, netflows, process history, file hashing, etc.) for a situation in which a system is behaving suspiciously, but which of those are the most resource intensive and maybe recommended to keep turned off when outside an investigation?
I tried to find documentation about best practices, or ways to reduce MVISION EDR processing power on endpoints and servers, but have failed to do so. Can you share any insight on this? (or better yet, other community topics or KBs on the matter?)
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.