Feature Request

Most logos are designed with transparency and to have good visibility on a light background. With the dark theme they often disappear. In my case I didn't even notice the logo in the preview and wondered where the logo was supposed to be showing.

From what I understood with the new feature you will be able to monitor where company employees are using their corporate email to register in different sites. This is great to give us visibility which we do not have today. It would be great to enhance with an option to not allow them to register at those sites with corporate email. This would entail somehow blocking the ability to submit the reigistration. We would need to have an option to whitelist domains that users can use the corporate email.

Similar to a zero-trust credential policy, the Identity DLP feature would allow an org to specify the domain(s) they use and wish to protect sign-ins for. These would be used in the system to monitor login activity for cases where the protected domain is used in a login username field. If the user is not on a page in the allowed URL group for the Identity DLP policy, they could get a block page and not be able to proceed without contacting IT.

Since there are currently no bulk customer import options, it would be nice if there were settings to control the default subscription and default security level/template that are preselected as you step through the customer creation wizard. This would allow you to just type/paste the customer name and hit next 4 times and be done if your clients are all using the same options.

So, as we have customers becoming more interested in CoPilot AI protections, Most of our deployments are based on logon user and the users are all domain users. CoPilot AI Protections require the Entra integration be set up and the users be signed into their DefensX via IAM user. We do LogonUser deployments because it is the least invasive for the customers and doesn't just block all access until auth can be had, that being said. There does not seem to be a way in the platform that you can based on the user have it require specific authentication methods, we can have different deployments or on individual devices override auth options, but we cannot have DefensX based on the AD user signing into a machine require them to sign in using IAM so it follows them to any machine they use in the event they use other devices Sounds silly perhaps but it's not worth it to the customer to have the disruption of requiring 200+ devices to have to authenticate via IAM instead of logon user. Allowing the entire organization to auth to IAM is one thing but just because it's an option doesn't mean they'll do it, thinking with a zero trust mindset, don't ask people not to do it, take away their ability to do it and force them to be required to do IAM auth so you can ensure things are being done the way you want/need.

It'd be nice to see an option within the user requests when reviewing requests to submit the URL from that request for classification or risk score review (ideally it would allow for you to select specific things you want it reviewed for) and specify notes when submitting that request. Additional, may be useful to have an option to report as well from the logs if we're reviewing blocked log entries and feel review is needed. Not important, just a nice to have quality of life thing.

Facebook, Google+, Linkedin, Twitter, Wordpresss, Ask.fm , Pinterest, Tumblr, Youtube, etc that have subcategories should show act like they're nested items (and be indented in the UI). If you select block on the top level it should select block on all the subcategories and if I want to allow certain ones I change them back.

Using DUO SSO for admin access to backend.

Hello! On the external user request management page that comes up from interacting with a request a user has made to allow something via webhook (such as via teams), It would be nice if the page had a function that allowed for the request to merely be closed, right now there is only actions that allow you to add it to a policy but if we wanted to just do nothing and close out the request, we'd need to go into the portal. Would just be a good quality of life add. Thanks!

On the Message Template page the 'preview' link and 'light' or 'dark' under theme are not capitalized like similar items in the rest of the UI.