Posted on: April 14, 2022 | By: Guy Logan | Microsoft Dynamics AX/365, Microsoft Dynamics Manufacturing
It is imperative for healthcare and life science businesses to have strong security architecture in order to protect sensitive healthcare information and patient data. By strengthening your security architecture, you can drastically reduce the risk of an attacker succeeding in breaching your systems.
Because of the rapid digitization of consumers’ lives it was estimated that the cost of data breachs would increase to about $2.1 trillion globally by 2019, increasing to almost four times the estimated cost of breaches in 2015. This means that in 2022 and the impending future, the value of protected healthcare information and patient data will only continue to increase.
This blog covers an overview of the security architecture of Finance and Supply Chain Management in Microsoft Dynamics 365.
When you understand the security architecture, you can more easily customize security to fit the requirements of your business. The following diagram provides a high-level overview of the security architecture.
By default, only authenticated users who have user rights can establish a connection.
Microsoft Azure Active Directory (AAD) is a primary identity provider. To access the system, users must be provisioned into a Finance and Operations instance and should have a valid AAD account in an authorized tenant.
Authorization is the control of access to Finance and Operations applications. Security permissions are used to control access to individual elements of the program: menus, menu items, action and command buttons, reports, service operations, web URL menu items, web controls, and fields in the Finance and Operations client.
Individual security permissions are combined into privileges, and privileges are combined into duties. The administrator grants security roles access to the program by assigning duties and privileges to those roles.
Context-based security controls access to securable objects. When a privilege is associated with an entry point (such as a menu item or a service operation), a level of access, such as Read or Delete, is specified. The authorization subsystem detects the access at run time, when that entry point is accessed, and applies the specified level of access to the securable object that the entry point leads to. This functionality helps to ensure that there is no over-permissioning, and the developer gets the access that was intended.
Authorization is used to grant access to elements of the program. By contrast, data security is used to deny access to tables, fields, and rows in the database.
Use the extensible data security framework to supplement role-based security by restricting access to table records based on security policies. A security permission, as part of a user role, increases the access a user has to data, while a security policy decreases access to data.
Additionally, the Table Permissions Framework helps protect some data. Data security for specific tables is enforced by Application Object Server (AOS).
Auditing of user sign in and sign out is enabled, which means that the system logs when a user signs in or out of the application. A sign out is logged even if the user’s session expires or ends.
A system administrator or security administrator can access the audit logs by going to the User log page (System administration > Inquiries > User log).
Don’t worry about defending against attacks, focus on producing the next life-saving drug. Let Logan Consulting help you with security architecture.
If you are interested in learning more about security architecture using Microsoft Dynamics 365 for Finance and Supply Chain Management, contact us here to find out how we can help you grow your business. You can also email us at info@loganconsulting.com or call (312) 345-8817.