Design Pattern: Security - Sensitive Data Encapsulation

September 5, 2016 <1 min read

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.

Problem: Sensitive data is scattered and mixed with other data in various parts of the system (passwords residing in the same table with non-sensitive data, part of the private information might be stored in files, hardcoded text constants, hardcoded info as part of the code etc.).

By Bogdana Botez at Microsoft Development Center Copenhagen

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!

Design Pattern: Security – Sensitive Data Encapsulation

Tags