{"title":"Layered security model in Business Central","url":"https://jonas-paprotka.de/docs/dev-itpro/security/security-application/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/security/security-application, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/security/security-application","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Helps you understand and improve the security of your Business Central application regardless of where it's hosted.","date":"2025-11-19","meta":{"topic":"article"},"outline":[{"level":1,"title":"Layered security model in Business Central","slug":"layered-security-model-in-business-central","at":0,"chars":5318},{"level":2,"title":"Authentication","slug":"authentication","at":529,"chars":938},{"level":2,"title":"Authorization","slug":"authorization","at":1467,"chars":1185},{"level":2,"title":"Data encryption","slug":"data-encryption","at":2652,"chars":322},{"level":2,"title":"Security development lifecycle","slug":"security-development-lifecycle","at":2974,"chars":316},{"level":2,"title":"Auditing data fields","slug":"auditing-data-fields","at":3290,"chars":1875},{"level":3,"title":"Sensitive field monitoring with email alerts","slug":"sensitive-field-monitoring-with-email-alerts","at":4317,"chars":848},{"level":2,"title":"Related information","slug":"related-information","at":5165,"chars":153}],"text":"# Layered security model in Business Central\nThis article helps you understand and improve the security of your Business Central installation regardless of where it's hosted. It includes guidance and recommended practices related to authentication, authorization, and auditing. It also touches on data encryption and secure development practices that can be applied to any Business Central environment.\nBusiness Central uses a layered approach to application security, as outlined in the following diagram.\n![Security overview.]\n## Authentication\nBefore 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 Microsoft Entra ID. Business Central online deployments use Microsoft Entra ID only. Learn more in the following articles:\nManaging Users and Permissions</ui-how-users-permissions>\nAudit user administration events in Microsoft Purview<../auditing/audit-events-in-purview#administered-user-activities>\nSet up Business Central Access with Microsoft 365 Licenses</admin-access-with-m365-license>\nAuthentication and Credential Types (on-premises only)<../administration/users-credential-types>\nSet up Multifactor Authentication (MFA)<multifactor-authentication>\nThe authentication method configured for Business Central Server is also used to access web services. See ../webservices/web-services-authentication.\n## Authorization\nAfter a user is authenticated, authorization determines which areas the user can access. For example, it determines the pages and reports a user can open and the permissions they have on associated data. Learn more in the following articles:\n#user-permissions-in-the-application\nAudit permission administration events in Microsoft Purview<../auditing/audit-events-in-purview#administered-user-activities>\nAnalyzing Permission Changes Trace Telemetry<../administration/telemetry-permission-changes-trace>\ndata-security?tabs=database-level\nRemoving Elements from the User Interface According to Permissions<../administration/hide-ui-elements>\nAnalyzing Authorization Telemetry<../administration/telemetry-authorization-trace>\nUsing OAuth to Authorize Business Central Web Services<../webservices/authenticate-web-services-using-oauth>\n> NOTE\n> After successful authentication, Business Central allows a user in only if they exist in the environment and have permission to the company or data they're trying to access. In other words, being a licensed in Microsoft Entra ID isn't enough&mdash;the user must also be set up inside Business Central with appropriate access.\n## Data encryption\nYou can encrypt data on the Business Central server by generating new encryption keys&mdash;or importing existing ones&mdash;that you enable on the Business Central server instance that connects to the database. See Encrypting Data in Dynamics 365 Business Central<../developer/devenv-encrypting-data>.\n## Security development lifecycle\nThe Microsoft Security Development Lifecycle (SDL) is a software development process that helps developers build more secure software. SDL addresses security compliance requirements while reducing development cost. See Security Development Lifecycle<https://www.microsoft.com/sdl>.\n## Auditing data fields\nFor a comprehensive audit trail of data changes, Business Central offers a change log feature. When the change log is enabled enabled for specific tables/fields, it records every insertion, modification, or deletion (including the old and new values, user, and timestamp).\nThis information is useful for compliance and investigations. However, be mindful of performance. Enable it only on the records that truly need detailed tracking. For instance, avoid logging every change on large ledger entry tables, because these changes are append-only by nature.\nLearn more about the change log in Audit changes</across-log-changes>.\n> TIP\n> Instead of the change log, you can use Business Central's analysis mode on any list page. Add the system fields (Created/Modified date and user) to the list (they can be hidden), then turn on analysis mode. With these fields present, the analysis mode (and Copilot) can help summarize recent changes to the data in that list&mdash;giving you a lightweight audit view.\n### Sensitive field monitoring with email alerts\nAdmins can set up monitoring of specific fields in Business Central, letting you flag fields as sensitive. If these fields are changed, the system can send an email alert to designated recipients and emit telemetry about the change. For example, you might monitor the bank account number field on a vendor card. This way, any change triggers an immediate alert, helping you quickly catch potential fraud attempts.\n> TIP\n> Sensitive field monitoring has significantly less performance impact than the change log feature, making it a recommended alternative. Use it to track critical fields without the overhead of logging every change across entire tables.\nSee /across-log-changes#monitor-sensitive-fields and Analyzing field monitoring telemetry<../administration/telemetry-field-monitoring-trace>.\n## Related information\nsecurity-and-protection\nSecurity Tips for Business Users<security-users>\nsecurity-online\non-premises Security<security-onpremises>"}