Find every copy and identify who can reach it
Locate the working database, front-end copies, exports, backups and test files. Identify the users, shared folders and devices that can access them. A report exported to a spreadsheet or an old backup can contain sensitive records even if the current interface looks restricted.
Record the data owner and permitted uses before changing access. The aim is to understand exposure and operational needs, not to lock staff out without a recovery plan.
Distinguish file encryption from individual permissions
Microsoft documents database-password encryption for ACCDB files. This protects the file differently from giving named users distinct application roles. Microsoft also explains that the older Access user-level security feature is not available in ACCDB.
Ask what each person must be allowed and denied: opening data, editing records, approving transactions, exporting information and administering the application. A shared database password should not be described as evidence that these individual rules are enforced.
Review trusted code and distribution
Access applications can include VBA, macros, queries and other active components. Microsoft explains the trust decision for database content. Do not enable unknown content simply to remove a warning. Have the authorized owner identify its source, purpose and intended changes.
Review who can replace the front end, how approved versions are distributed and which locations have been marked trusted. A useful control depends on who can change the files in that location, not only the label applied to it.
For a server backend, review the server too
Microsoft identifies a database server such as SQL Server as an option for managing user security. If Access already links to a server, inspect the connection and permissions actually used. Do not assess that architecture as though it were only a single standalone file.
- Which identities connect to the backend?
- Can someone bypass a screen and still change restricted data?
- Who manages accounts, updates, connection settings and access removal?
- Which actions need a history, and is that history actually recorded and reviewed?
Keep support and recovery in the review
Check the installed Access, Windows, drivers and other components against their actual support status. Microsoft Lifecycle provides version-specific information; “Access is unsupported” is not a reliable statement about every deployment.
Identify what backups contain, who can restore them and when recovery was last tested. If a change fails, recovery must account for records added since the backup as well as the ability to open an older file.
A web replacement introduces its own responsibilities
A browser interface needs correctly implemented authorization, deployment and operations. Django’s permission system provides framework tools, but business-specific access still has to be implemented and tested. Its deployment checklist covers production security considerations; using Django does not certify a particular application.
Illustrative example: a customer portal should be tested with two different customer accounts. Confirm that each can view and change only the intended records, including direct requests to a record URL. Hiding a menu item is not an adequate acceptance test for record access.
Use an Access assessment to compare controls that can be improved in the current setup with requirements that justify a different architecture. The migration planning guide covers the transition after that decision.
Related reading
Sources and review notes
https://support.microsoft.com/en-us/access/encrypt-a-database-by-using-a-database-password
https://support.microsoft.com/en-us/access/what-happened-to-user-level-security
https://support.microsoft.com/en-us/access/decide-whether-to-trust-a-database
https://learn.microsoft.com/en-us/lifecycle/products/?terms=access
https://docs.djangoproject.com/en/6.1/topics/auth/default/
https://docs.djangoproject.com/en/6.1/howto/deployment/checklist/


Comments
Leave a comment
Comments are reviewed before publishing.