Study guide
2.3 Security Filters, Change Log & Security Auditing
Microsoft Dynamics 365 Business Central Functional Consultant MB-800
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Company Creation & Data Migration
1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies
2 Chapter 2: Security, Profiles & Auditing
2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing
3 Chapter 3: Core System Configuration, Number Series & Copilot
3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities
4 Chapter 4: Dimensions Architecture & Governance
4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities
5 Chapter 5: Workflows & Approvals
5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration
6 Chapter 6: Financial Setup, Periods & Currencies
6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates
7 Chapter 7: Chart of Accounts, Categories & Allocations
7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing
8 Chapter 8: Posting Groups & Posting Setup
8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups
9 Chapter 9: General Journals & Recurring Methods
9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods
10 Chapter 10: Accounts Payable & Accounts Receivable Setup
10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup
11 Chapter 11: Fixed Assets Setup & Depreciation Books
11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods
12 Chapter 12: Inventory Setup, Costing & Locations
12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
13 Chapter 13: Logistics Master Data, Pricing & Discounts
13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds
14 Chapter 14: User Interface, Views, Inspection & Excel
14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode
15 Chapter 15: Purchase & Sales Order Execution
15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders
16 Chapter 16: Invoices, Credit Memos & Document Corrections
16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows
17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications
17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules
18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting
18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals
2.3 Security Filters, Change Log & Security Auditing
Key Takeaways Explain This Topic AI
Record-level Security Filters restrict user access to specific rows within a table (such as G/L accounts, customer territories, or dimension values) directly at the database permission level.
The Change Log records an immutable historical audit trail of data insertions, modifications, and deletions on critical tables, but should be restricted to setup and master tables to prevent severe performance bottlenecks.
Field Monitoring provides active, automated protection on ultra-sensitive fields (such as vendor bank accounts and IBANs), dispatching immediate email alerts when unapproved edits occur.
Enterprise security auditing integrates native Business Central change logs and field monitoring with Azure Application Insights telemetry to monitor authentication anomalies, permission escalations, and bulk data exports.
Last updated: September 2026
Security Filters, Change Log & Security Auditing
Enterprise implementations demand granular data segregation and comprehensive auditing. Dynamics 365 Business Central provides a defense-in-depth architecture consisting of record-level security filters, passive historical change logs, real-time field monitoring alerts, and cloud telemetry integration via Azure Application Insights.
Record-Level Security Filters: Architecture & Syntax
While standard permission sets control table-level access (e.g., whether a user can read TableData 18 Customer ), data governance often requires row-level segregation. For example, an organization may require regional sales agents to access only customers located in their assigned territory, or prevent junior accountants from viewing confidential payroll general ledger accounts.
In Business Central, row-level security is enforced via Security Filters applied directly to TableData lines within User-Defined Permission Sets .
Configuring Security Filters
Open Tell Me ( Alt+Q ) and search for Permission Sets (Page 9802).
Select a User-Defined permission set and choose Permissions .
Locate the target TableData row (e.g., TableData 18 Customer or TableData 15 G/L Account ).
Scroll to the Security Filter column and click the ellipsis ( ... ) to open the Table Filter dialog.
Select the field to filter upon and specify the filter expression.
Filter Syntax & Practical Applications
Security filters use standard Business Central filter expressions:
Number Ranges : 1000..1999 applied to No. on TableData 15 ( G/L Account ) restricts the user to view and post only balance sheet asset accounts.
Multiple Discrete Values : NORTH|WEST applied to Territory Code on TableData 18 ( Customer ) limits user visibility to customers in the North or West territories.
Exact Matches : ='DOMESTIC' applied to Customer Posting Group restricts visibility strictly to domestic accounts.
Exclusions : <>PAYROLL applied to Global Dimension 1 Code prevents the user from viewing any transaction or account tagged with the Payroll department dimension.
Runtime Behavior & Transaction Rollbacks
Understanding how security filters interact with application execution is critical for functional consultants:
List Page Filtering : When a user opens a list page (e.g., Customer List), Business Central automatically injects the security filter into the SQL query's WHERE clause. Rows outside the filter criteria are invisible. The user cannot clear this filter using the UI filter pane.
Lookup Validation : If a user attempts to manually enter a customer number or G/L account outside their security filter, Business Central rejects the input as an invalid record.
Posting Abort Hazard : If a user initiates an automated posting routine (e.g., posting a sales invoice) and the posting codeunit attempts to read, validate, or insert a record that violates the user's security filter (for example, reading a restricted rounding G/L account or tax account), the entire transaction terminates immediately with a runtime error and rolls back all database changes .
Architectural Limitations
No FlowFields : Security filters cannot be applied to FlowFields or FlowFilters; they can only be defined on physical database fields.
Indexing & Performance : Because security filters are injected into every SQL query executed on that table, applying filters to unindexed fields on large tables forces SQL Server to perform full table scans. Always apply security filters to indexed key fields.
The SUPER Exception : If a user is assigned the built-in SUPER permission set without a company filter, Business Central bypasses all security filters completely.
The Change Log: Comprehensive Historical Auditing
Regulatory compliance standards (SOX, ISO 27001, GDPR) require organizations to maintain verifiable audit trails of changes made to master data and system configuration. Business Central fulfills this through the native Change Log mechanism.
Activating and Configuring Change Log
Open Tell Me -> Change Log Setup (Page 592).
Check the Change Log Activated toggle.
Choose Actions -> Setup -> Tables to open the Change Log Setup (Table) List .
For each table requiring auditing, configure the three operational events:
Log Insertion : [Blank] , Some Fields , or All Fields .
Log Modification : [Blank] , Some Fields , or All Fields .
Log Deletion : [Blank] , Some Fields , or All Fields .
If Some Fields is selected for Modification, click into the table's field list and check the specific fields that warrant tracking.
Inspecting Change Log Entries
When an audited table or field is modified, Business Central writes an immutable record to Table 405 Change Log Entry . Users inspect these records via Tell Me -> Change Log Entries (Page 595).
Each Change Log Entry captures complete forensic metadata:
Entry No. : Unique sequential integer.
Date and Time : Exact UTC timestamp of the commit.
User ID : The authentication identity who committed the change.
Table No. & Table Caption : The database table affected (e.g., Table 23 Vendor ).
Field No. & Field Caption : The specific field altered (e.g., Field 8 Address ).
Type of Change : Insertion , Modification , or Deletion .
Old Value : The field value prior to the edit.
New Value : The newly committed field value.
Audit Immutability : Change Log Entries are strictly read-only within the Business Central application. Even users with the SUPER role cannot edit or delete individual change log records from the user interface.
Performance Hazards & Best Practices
A common point of failure in real-world implementations—and a central concept tested on the MB-800 exam—is the misconfiguration of Change Log on transactional ledger tables.
The Transaction Ledger Rule
Never enable the Change Log on high-volume transactional ledger tables! Tables such as Table 17 ( G/L Entry ), Table 21 ( Cust. Ledger Entry ), Table 25 ( Vend. Ledger Entry ), and Table 32 ( Item Ledger Entry ) are already immutable append-only ledgers by design. Every financial transaction posted in Business Central writes permanent records containing user stamps, dates, and document references.
Enabling Change Log on ledger tables creates severe operational disasters:
Every posted invoice line generates dozens of redundant change log entries.
High-volume batch posting encounters massive SQL lock contention on Table 405 ( Change Log Entry ), causing posting deadlocks and timeouts.
Database storage expands exponentially, driving up cloud infrastructure costs.
Change Log Best Practices :
Audit Setup Tables : Enable All Fields on core setup tables that dictate financial behavior (e.g., General Ledger Setup , Sales & Receivables Setup , Purchases & Payables Setup , Posting Groups ).
Audit Master Data Selectively : Use Some Fields on master entities (e.g., Customer , Vendor , Item , Bank Account ) to track critical attributes such as Credit Limit, Payment Terms, or Posting Group assignments.
Implement Retention Policies : Use the native Retention Policies framework ( Tell Me -> Retention Policies ) to automatically delete Change Log entries older than an organizationally approved retention window (e.g., 1 year or 3 years) using scheduled background job queues.
Monitored Fields: Real-Time Fraud Prevention
While the Change Log provides passive historical auditing, it requires someone to manually review log entries after the fact. In high-risk areas such as corporate treasury and vendor management, passive logging is insufficient to stop internal fraud.
A common fraud scheme involves a compromised user changing a legitimate vendor's bank routing details to a personal account, waiting for a payment batch to execute, and then switching the bank details back. To prevent this, Business Central provides Field Monitoring (Monitored Fields) .
Configuring Monitored Fields
Navigate to Tell Me -> Monitored Fields Worksheet (Page 1362).
Add the sensitive table and field combinations. Standard audit fields include:
Table 23 Vendor -> Field 59 Our Account No.
- Table 288 Vendor Bank Account -> Field 11 Bank Account No. / IBAN / SWIFT Code
- Table 27 Item -> Field 18 Unit Cost
- Table 98 General Ledger Setup -> Field 10 Allow Posting From
Navigate to Tell Me -> Field Monitoring Setup (Page 1360).
Specify the Notification Email (e.g., compliance@company.com ) and the User ID of the compliance officer.
Enable the monitoring service.
Operational Alerting & Anti-Tamper Security
Immediate Email Dispatch : The instant a user commits a change to a monitored field, Business Central logs the modification to Monitored Field Log Entries and dispatches an immediate email alert to the designated notification address detailing who made the change, the old value, and the new value.
Anti-Tampering Self-Defense : To ensure a rogue administrator cannot silently disable field monitoring before executing a fraudulent edit, modifying or disabling the Field Monitoring Setup itself requires administrative re-authentication, logs an audit entry, and sends an immediate high-priority warning email to the security team.
Enterprise Security Telemetry & Application Insights
For enterprise threat detection and comprehensive IT governance, Business Central environments can be connected directly to Azure Application Insights .
Configured within the Business Central Admin Center, Application Insights streams live platform telemetry to Azure Monitor without generating database overhead. Key security and operational events captured include:
Authorization Failures : Tracks error code RT0004 (permission denied) to identify users attempting to access restricted tables or unauthorized pages.
Privilege Escalations : Records when a user is granted the SUPER permission set or added to an administrative security group.
Data Export Events : Logs when users execute Open in Excel , Edit in Excel , or bulk data export routines, enabling compliance teams to detect potential data exfiltration of customer or financial lists.
Session Anomalies : Analyzes login geographic locations, authentication failures, and concurrent user sessions.
Security analysts use Kusto Query Language (KQL) in Azure Monitor to create real-time alert rules that notify IT teams if anomalous export volumes or repeated authorization rejections occur.
Governance & Auditing Comparison Matrix
Auditing Feature Primary Purpose Trigger Mechanism Output / Action Performance Impact
Security Filters Restrict row-level record visibility (e.g., by territory or account range). Injected into SQL WHERE clause on every data query. Hides records in lists; aborts posting if out-of-filter record is touched. Low if filtered on indexed fields; high if placed on unindexed fields.
Change Log Passive historical auditing of master data and configuration changes. Database triggers on Insert, Modify, or Delete. Permanent, immutable records in Change Log Entries (Table 405). Extreme if enabled on transaction ledgers; negligible if restricted to setup tables.
Field Monitoring Active real-time fraud prevention on critical bank and financial fields. Background monitor on specifically tagged fields. Log entry in Monitored Field Entries plus instant email notification. Minimal; evaluates only specified critical fields.
Application Insights Tenant-wide security telemetry, diagnostics, and export surveillance. Asynchronous telemetry pipeline to Azure Monitor. External Azure dashboards, KQL query logs, automated alert rules. Zero database impact; telemetry is offloaded asynchronously.
Common Pitfalls & Exam Gotchas
Enabling Change Log on G/L Entry : A classic MB-800 question asks why batch posting became painfully slow after activating Change Log. The answer is almost always that Change Log was turned on for transactional ledger tables (Table 17, 21, 25, or 32).
FlowField Security Filter Myth : Attempting to place a security filter on a FlowField (such as Customer Balance (LCY) ) is impossible and will throw an error. Security filters can only filter on stored database fields.
Assuming Change Log Blocks Modifications : Change Log is purely passive and retrospective. It records that a change occurred; it does not prevent the user from making the change. To prevent unauthorized modifications, administrators must use Permissions or Security Filters.
Bypassing Security Filters with Global SUPER : When testing security filters, functional consultants often log in using their own administrative account and observe that the filter does not work. This occurs because the SUPER role assigned without a company filter automatically bypasses all record-level security filters.