Why we don't give direct, read-only access to cloud database instances

Read-only access comes with significant risks and challenges that outweigh the potential benefits

This page is for MYOB Acumatica consultants

Check all changes in a test environment before taking them live. Make sure all related features still work as expected and that your data is unaffected.

Giving customers direct, read-only access to our cloud database instances may seem like a convenient way to share data, but it poses significant risks and challenges that outweigh the potential benefits.

Here’s why we maintain strict controls over direct database access.

Security and data protection

Direct access to database instances can expose sensitive data to potential security vulnerabilities. Even with read-only permissions, there’s a risk of unauthorized data access or data leakage. Malicious actors could exploit vulnerabilities in database software or misconfigurations to escalate privileges or gain deeper access. Maintaining a secure environment is paramount, and restricting direct access helps prevent potential security breaches.

Data integrity and consistency

Allowing read-only access can inadvertently lead to data integrity issues. For instance, customers might perform intensive queries that could lock tables or cause performance degradation, impacting other users or services relying on the same database. Additionally, even with read-only access, certain operations (such as reading data during an ongoing transaction) could lead to inconsistencies or misinterpretation of data due to uncommitted changes.

Regulatory compliance

Many industries are subject to strict data protection regulations, such as GDPR, HIPAA, or PCI DSS. Providing direct access to databases can complicate compliance efforts, as it becomes challenging to monitor and control data access. We ensure compliance by centralizing data access through secure, monitored interfaces that allow us to log and audit data access, thus maintaining adherence to legal and regulatory requirements.

Data access management

Managing direct access rights for multiple customers can be complex and prone to errors. Misconfigured permissions can lead to unintended data exposure. By restricting direct access, we streamline data access management, ensuring that only authorized users and systems have the necessary permissions, reducing the risk of accidental data breaches.

Availability and reliability

Ensuring high availability and reliability of our services is a top priority. Allowing direct access could lead to situations where customer queries impact the stability or uptime of our database instances. By controlling access through APIs or data export mechanisms, we can better manage and mitigate risks associated with database performance and availability.

Conclusion

For these reasons, we opt to provide data access through controlled, secure channels such as APIs, data exports, or dashboards. These methods offer customers the data they need while ensuring robust security, maintaining data integrity, optimizing performance, complying with regulations, and simplifying access management. By not allowing direct read-only access to our cloud database instances, we protect both our infrastructure and our customers' data, ensuring a secure and reliable service for all.