Feature Request

Ability to create a customer via the API in a trial state that automatically transitions to a billable one after the trial period.

Transitioning from loopback DNS to a System Extension would allow for better integration with macOS, allowing users to set static IPs/DNS while still enabling management to capture and manage DNS traffic. Currently, setting a static IP address on a macOS device breaks DNS-based filtering.

Want the ability to see when another admin adds a new URL to a custom URL.

We are developing a built-in Dynamic DNS provider service exclusively for DefensX customers. This will eliminate the need for external DDNS accounts, simplify configuration, and allow customers to manage everything directly within DefensX.

Description: Currently, the Basic, Standard, and Strict Policy Templates do not include predefined rules for Credential Filtering and File Filtering. To provide a more consistent and secure out-of-the-box experience, these templates should include baseline configurations for both modules. Adding predefined rules would help partners deploy comprehensive protection faster — especially for new customers who rely on the default templates. Suggestions: • Add recommended Credential Filtering rules (e.g., block login form submissions for risky or unknown categories). • Add recommended File Filtering rules (e.g., block uploads to untrusted domains or downloads of risky file types). • Provide short tooltips or documentation links explaining the default behaviors in each template. • Make it possible for partners to clone and customize these templates easily. Call for Feedback: Partners — please share your suggestions or preferred rule sets for Credential and File Filtering, so we can ensure the defaults align with real-world use cases.

When external notifications are configured, a specific URL is included in the notification. This URL contains a 2-day valid token that allows adding the hostname to a custom URL Group without requiring a backend login. It would be useful to introduce an option to disable this behavior on a per-notification-mechanism basis.

Searching in logs like *. example.com

It would be nice to use categories for the File Transfer or Credential block sections. For example, allow access but limit file uploads/downloads for all email portals. Currently having these two features url only makes them a bit too cumbersome if you want to block more than specific sites.

The Create Ticket form is great but it doesn't give confirmation of a ticket number and no automated email response is provided. Sometimes, people aren't sure that the form was successful and that the support request was received. It would be very helpful if a ticket number or automated email response could be provided either immediately after the Create Ticket form has been submitted or shortly after within 5 minutes.

In some Active Directory installations, the displayName attribute follows the "LastName, FirstName" schema instead of the "FirstName LastName" format. To ensure accurate user attribute management in DefensX, it would be beneficial to detect which schema is in use and automatically create and populate the FirstName and LastName attributes accordingly. This approach will streamline the integration process and maintain consistency in user data across systems.