Published | September 10, 2018

NexJ’s Dynamic, Flexible, and Centralized Security Model

NexJ’s Dynamic, Flexible, and Centralized Security Model

With the move towards open systems, security is more important than ever to the financial services industry – an industry where security has always been important.

The increasing popularity of internet banking and mobile access are paired with increasing regulation and scrutiny. This means both more possibility for issues and more consequences when issues arise.

NexJ enables firms to manage and protect information with a robust, centralized security model. As a centralized model, NexJ enables you to apply your security rules consistently across all channels, including the user interface, customer portals, and external consumers and APIs that will access NexJ CRM information. NexJ provides granular control of access to data and functionality using proven integration capabilities within your security ecosystem. This provides our customers with the ability to meet any security requirement and mirror how your business actually works.

Additionally, NexJ’s security model is fully customizable by our customers without compromising their long-term ability to upgrade the software. It’s built on industry standards that allow NexJ to map directly to existing security models and consume an existing entitlements model that encapsulates client preferences and regulations.

NexJ’s security model has four components:

  • Integrated User Authentication

This determines who someone is and if they’re allowed to access the system. Deployed across a range of technologies in client environments, these systems provision user roles and allow dynamic auto-assignment of privileges to NexJ users.

  • Functional Entitlements

This determines what a user can do in the system. Functional entitlements define security concepts such as user roles, groups, and privileges. This controls access to attributes, functions, and features, providing a high degree of functional decomposition and granularity by user role.

  • Data Visibility

This determines what a user can see in the system. Data level security is used to control access to object instances or records. This can include logical rules that are based on the data being viewed, attributes of the user, or even external input.

  • Encryption

This determines how data is secured both at rest, and in transit. NexJ encrypts database columns and user credentials, and uses certificate-based mutual authentication to secure integration channels over HTTPS.

NexJ’s comprehensive security modeling capability provides our customers with the flexibility to meet any security requirement. This offers you a security model that mirrors how your business actually works across roles and job functions, asset classes, regions, and lines of business. For more information on NexJ’s security model, visit

speaker_notes Post Comments
Heather Lekx

Author: Heather Lekx

Product Marketing Copywriter

As a product marketing copywriter for NexJ Systems, Heather plays a front line role in sharing NexJ’s deep domain expertise in enterprise customer management, the customer experience, and the financial services industry.

Heather has gained a unique perspective into NexJ’s products and industries from working in both the documentation and marketing departments. Most recently, as lead RFP response manager, Heather has developed a deep understanding of the business requirements of leading financial services firms. She continues to expand her knowledge through interviews with key subject matter experts at NexJ and looks forward to sharing her insights with readers of her blog.

Comments Off on NexJ’s Dynamic, Flexible, and Centralized Security Model

Comments are closed

Blogs by Date