My name is Jason Sheffield, and I've been a Sr. Sales Engineer with
Netskope for about 7 and a half years now. I've been a Security SE for
over 20 years, focused on SIEM and DLP. I cover accounts in Houston and
Louisiana, but I'm happy to help anyone...
Patrik, Apologies for the delay in my response. I got Entity Modifiers
enabled in my tenant and realized that you can't use an inclusive RegEx
as a second validator. We do have "begins with", "does not begin with",
"ends with", "does not end with", a...
Apologies. I didn't check for a negative. I believe that the only way to
do this, since we don't support forward and reverse lookups, would be to
leverage a new feature called Entity Modifiers. It's only available
currently via a backend flag. You ca...
Short answer is (.*[!£@#$%^&+=])(.{10,}).* will work. Netskope doesn't
support anything with (? in it. Also, it's not good practice to use ^ or
$ in our RegEx as it's typically designed for form validation.
That will tell you connectivity. Without checking the certificate, you
can't be sure that the traffic is steered correctly. If the cert isn't
goskope.com, you may have connectivity, but it's not being steered, and
therefore SSL decrypted by Netskope.
