What is a one sentence summary of your feature request?
As an engineer, I need more flexibility in the regex engine so that I can account for human error in our targeted data.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
We rely heavily on regex because: differences in user behavior. While the current regex engine allows us to account for differences in spacing and punctuation, the work around for case insensitivity is cumbersome. I would like to see the (?i) function added so that I can create simple regex patterns to help us isolate and protect targeted data.
How do you currently solve the challenges you have by not having this feature?
we would have to use the lengthy [U][l] format for each letter of each word in the regex pattern.
Hello Bree,
Thank you for submitting your request — we greatly value your feedback and the time you’ve taken to share your ideas with us.
We fully understand the scenario you’d like to achieve here but at this moment, due to current design and technical limitations, we’re unable to move forward with this particular request. That said, we will certainly keep it in mind for the future should the opportunity arise. For now, we’ll need to respectfully decline.
We truly encourage you to stay engaged with our community and continue sharing your thoughts. Every suggestion helps us shape our products and services in ways that bring more value to our customers.
Thank you for your understanding.
Kind Regards,
Simona
Hello Bree,
We have some important updates regarding this topic. After conducting additional internal testing on this scenario, we’d like to share the following results:
EPP supports both standard Regex syntax and Perl-Compatible Regular Expression (PCRE) extensions and modifiers. For example, you can use the (?i) modifier at the beginning of a regex pattern to make it case-insensitive during matching.
In the following example, the pattern (?i)test will match “test,” “Test,” “TEST,” and other variations, regardless of letter case, as follows:
1. In this section, the Regex pattern is defined, added to the dictionary, and saved. Ensure that it is also included in the CAP Policy for proper application.
- The Content Aware Report confirms that the test has completed successfully and that case-insensitive matching is functioning as expected.
Note:
Please allow us a short time to update our official documentation accordingly. We will ensure that the Regex chapter is revised to include the information outlined above for reference.
Please do not hesitate to reach out to us if needed.
Kind Regards,
Simona
1 Like
This is the (current) official page: Denylists | Netwrix Product Documentation
We’ll get it updated and post here when complete which could take a little bit. Thanks for being patient. But hopefully “the screenshots above tell the tale.”
2 Likes
