Testing enclave and not logging to threat-log

Reply
Highlighted
L0 Member

Testing enclave and not logging to threat-log

My question is in regards to testing our enclave.  I have an entity that probes/tests/scans our enclave for thousands of vulnerabilities per IP.  I stopped the entries in the traffic-log by creating duplicate security rules with logging disabled.  However, threat matches from Vulnerability Protection naturally write to the threat-log every time a rule match is made.  I want the defined vulnerability protection actions to occur without the log entry being written to the threat log.  

 

On the Vulnerability Protection Security Profile, if a wildcard existed or it was possible to be used for a blanket exception, the exceptio would change the scan results, so I do not want an exception there.   I just want to provide the protection in the profile without the log bloat reaching my threat-log from all the scanning.   Is there a way to do so?   

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 Live Community as a whole!

The Live Community thanks you for your participation!