Quick; think of a business that provides excellent service each time you interact with them. Are you likely to remain loyal to their brand? Have you raved about them to your friends and family?
See how (not) to mess up your Dynamics NAV upgrade, on-premises or in the cloud. With real-life examples – incidents we helped fix in PaaS. Warning: NAV partners, don’t do this at home (nor at work).
Aliases: Masking out Context: In the user interface (UI) of a software system, the user enters protected information such as a password, an access key, a credit card number etc.
Context: Protected data needs to be used. There are many types of entities which might attempt to use the data. Problem: If no standard way of accessing data exists, then each entity might attempt to build its own system for handing the sensitive data.
Context: After applying Sensitive Data Encapsulation, all sensitive data is gathered in a known place in the database. This makes it possible to apply further protection best practices. Problem: If any non-authorized actor manages to get access to a copy of the database, the sensitive data is immediately available in clear-text.
Aliases: Encapsulation, Separation of Concerns [1] Context: As a C/AL developer, you want to protect sensitive data which already exists in a system, but it is not clear which data needs protection and how to store it.
Context: The security of data transmission is just as important as the security of data storage. When data is transmitted over the web, Secure Sockets Layer (SSL) is available to be used with the web client in Dynamics NAV. Microsoft’s NAV cloud solution has SSL enabled by default.
For many records, such as Items, Customers, and Vendors, users have to enter the same sets of data again and again. This is tedious, error-prone (users forget to enter a field or they choose the wrong group), and difficult to learn for some users.
This pattern implements a generic mechanism for dynamically restricting and allowing usage of a record by the business process administrator. Problem A Dynamics NAV record can be used in a number of functionalities across the application.
By Bogdana Botez at Microsoft Development Center Copenhagen This pattern is supported starting from Microsoft Dynamics NAV version 2016. Abstract Protect data like passwords, social security numbers, credit card numbers etc by encrypting it and by placing it in a single table with restricted access.