Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Stacy Black]

We are constantly hearing about security breaches in mega companies, and now many states now requiring Social Security number protection, my question is how are you securing your employees/vendors social security numbers? 

Do you have a custom code?  Are you using Employee groups with XDS?  Please share what has worked for you.

——————————
Stacy Black
Senior Application Consultant
MCA Connect
Denver CO
——————————

[Corey Vantilborg]

We are in Canada which changes the legal requirements,  and further we do not keep our SINs(equal to Social Security Number) in AX.  This is more due to policy then it is due to a technology limitation. 

During our security audit we identified several areas where we would need to improve to secure sensitive information.

1. Using XDS to ensure that only authorized users could access the information via AX.
2. Implement encryption in  SQL to ensure the information could only be accessed via the AX, and only with the XDS queries applied.   See: https://technet.microsoft.com/en-us/library/dd362064(v=ax.50).aspx
3. Modify our data refresh scripts / process to strip out sensitive information during the refresh process.
4. Ensure that database back-ups where secured and encrypted.

We have not implemented most of this as it is not yet a business requirement to store this information in AX.

——————————
Corey Vantilborg
ERP Analyst
Tigercat International Inc.
Brantford ON
——————————
——————————————-

[Sherry Moran]

?While we don’t SSN in AX, we do have bank accounts and we needed to do the same thing.  Through security in the AOT I made the field NOT display for all and then I created a privilege/duty that I assigned to a role that would have access to view and edit.  We’re AX2012 R2.

Sherry

——————————
Sherry Moran
SR Business Systems Analyst
Key Technology, Inc
Walla Walla WA
——————————
——————————————-