The headline news is currently focused on the coronavirus pandemic. But let us not forget that in addition to protecting ourselves and staying safe, we also need to safeguard the security of our ERP application. While we are holed up, safe, and secure in our homes, hackers may be exploiting the vulnerabilities of our ERP systems.
Keeping Microsoft Dynamics 365 Business Central (BC) Secure
Let's start with a brief overview of the 3 "A" s
Before users can sign-in to the Business Central application, they must be authenticated as a valid user in the system. Business Central On-Premises supports several authentication methods, such as Windows and Azure Active Directory. Business Central Online uses strictly Azure Active Directory (Azure AD).
Once authenticated, authorization determines which areas a user can access, such as the pages and reports that they can open, and the permissions that they have on associated data. Auditing Business Central includes several auditing features that help you track information about who is signing-in, what their permissions are, what data have they changed, and more.
Beyond the 3 "A" s
Yes. There is more that you should be doing. Best practices include, as but 2 examples, the following: Data Encryption
You can encrypt data on the Business Central server by generating new or importing existing encryption keys that you enable on the Business Central server instance that connects to the database. Security Development Lifecycle
Microsoft's Security Development Lifecycle (SDL) is a software development process that helps developers build more secure software and address security compliance requirements while reducing development costs.
Stay tuned for part 2 of this series on application security
Security is not just a hot topic. It is imperative. We will take a deeper dive in our upcoming blog: "Security in Microsoft Dynamics 365 Business Central Online and BC On-Premises." Stay tuned!