Feature Request

So while DefensX seems to report on browser extensions present, It'd be nice if it had the means to have policies that enabled us to block all extensions except for the defined allowed extensions with the option to have it remove all additional extensions that aren't defined as allowed.

Ability to whitelist extensions.

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.

We have a customer with a unique use case where the default action is block everything and you must be part of a group that a policy applies to in order for things to be allowed. As a result, there is obviously a lot of people that think they should have access to stuff so there is a flood of reports that comes in as a result, I've checked and there seems to be no function that allows for different message templates to apply to different policies, nor is there options in the templates to remove users abilities to report via the platform. Perhaps this is a niche need but such flexibility could be nice to cut down on noise from people who they do not even intend to be able to get to anything other than what is explicitly allowed per policy.

Similar to the browser printer or screenshot protection, use OS level integrations to pick up on clipboard activity and allow for monitoring of pasting outside of the browser process, or possibly clearing the clipboard proactively. Similar to mobile MDM enforcement.

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.

We have multiple firewalls and such that we have added to our allowed URL list and would like a way to rename/add a note to the corresponding IP addresses for better "bookkeeping" purposes. That way when we are auditing our allowed list, we can easily see what the IP addresses are associated with.

I believe an API should not have gatekept features. Obviously some of the features of an API serve no purpose at lower subscription levels but preventing the ability to automate across all customers and subscriptions types is silly.

Integration between DefensX backend and Ninja RMM to transfer any useful information including tickets, usage, etc.

Deployment templates that can be created under self customer and utilized across any customer similar to the existing policy templates.