Preparing for a VaultLens audit on your vault doesn’t have to be a daunting task. We’ve streamlined the process to ensure it’s efficient and straightforward. Whether you’re ready to prepare ahead or prefer to handle it together during a call, we’ve got you covered. Here’s a concise guide on what you need to ensure the audit runs smoothly.
Access Requirements
VaultLens operates by interfacing with your PDM Vault’s SQL Server database, so the primary requirement is access to that server. Typically, audits are conducted over a virtual meeting, where we will access the server remotely. You’ll be able to view all live operations in real-time as we execute them.
SQL Login
For VaultLens to perform its functions, we require a SQL login with read access to your PDM databases. At a minimum, the login should have db_datareader permissions for two key databases:
- Your Vault Database
- The PDM Master Database (specifically named CanesioMasterDB)
Additionally, this login must have the “view server state” permission, allowing us to read performance and configuration data.
Creating the SQL Login
You have three options for setting up the SQL login permissions:
Pre-creation: You can set this up ahead of time. If needed, we can provide a script to simplify this task, ensuring the login has the required permissions.
On-the-fly Creation: If preferred, we can establish the login during our session. This process is quick, typically taking about a minute, and you’ll witness each command as it is executed. We only require someone on the call with the ability to create logins.
Using Existing Accounts: If your internal policies permit, using a sysadmin or the SQL SA account is also an option, thus bypassing the setup step entirely.
Rest assured, all operations conducted by VaultLens are read-only – no data will be written, altered, or deleted.
Audit Execution
The execution process for VaultLens is seamless. The tool is a single executable, with no installations or residencies left on your server. Once the audit is complete, the program is removed entirely. During the setup, we direct it to your SQL Server instance, select the appropriate vault database, and use the previously mentioned login information.
From there, the audit commences without any further configuration needed. All operations performed are read-based, querying your database for information on permissions, workflows, backups, server configurations, etc. Importantly, your users can continue to work in the vault during this process, with no downtime or need for after-hours scheduling.
Completion and Reporting
The duration of the audit is contingent on the size of your vault but generally ranges from ten to sixty seconds. Post-audit, one key output is generated – a findings file. This file is sent back to our technical team at MLC, where an applications expert reviews the results and compiles your final report. You will receive both an interactive HTML report and a Word document.
Conclusion
Ensuring a smooth VaultLens audit is as simple as deciding on your SQL login setup and ensuring the right individuals are available for the call. Once this brief preparation is complete, you’re free to leave the rest to us, allowing you to discover actionable insights within your database swiftly and with minimal disruption.
