AODocs Security and Compliance

Last update :

Security is a critical aspect of document management and one of the top priority of AODocs. This article describes the architecture and processes that AODocs has implemented to ensure the protection of its customers’ data.

Infrastructure

AODocs runs entirely on Google Cloud Platform, and in particular on Google App Engine, one of the most secure platform-as-a-service on the market. Google App Engine features a number of certifications such as SOC2, SOC3, ISO 27001, ISO 27017, ISO 27018, FedRamp ATO and PCI DSS, which reflect the high level of security of this platform.
Learn more here:
Google Cloud Platform compliance

Customer data stored in AODocs benefits from Google App Engine’s security features, such as the at rest encryption, the security of Google’s network and the physical security of its datacenter facilities. Data storage in Google App Engine is highly redundant, with automatic replication across multiple datacenters.
Learn more here:
Google Cloud datastore

AODocs also implements a “cloud only” policy for its internal IT: all internal application are running on highly redundant public cloud to make sure our employees can work from anywhere. The loss of any one of our physical offices cannot impact the continuity of our business operations. 

Data transfers

All data transferred to and from AODocs is encrypted by industry standard protocols such as SSL/TLS. AODocs front-ends are managed by Google App Engine, which provides highly secured web servers that are regularly updated against any known vulnerabilities.

Since AODocs runs on Google Cloud Platform, the data exchanged between the AODocs application and Google Drive is transferred via Google’s internal private network, communication between AODocs and Google Drive running on Google’s internal private network.

User authentication

Users accessing AODocs are authenticated by their Google account, via the OAuth2 login flow. Access permissions and roles in AODocs are set on Google accounts and Google groups, while the access control on AODocs files in Google Drive is done by Google Drive itself.

AODocs does not store any password and never asks users for any password.

Segregation of customer data

AODocs is a multi-tenant SaaS application, where all customers are hosted on a single instance of the application. AODocs stores customer data in two different places:

  • The files attached to AODocs libraries are stored in each customer’s Google Drive domain, owned by the AODocs storage accounts (learn more here: The AODocs storage account)
  • The AODocs-specific data such as custom document properties, AODocs configuration, workflow status, audit log, etc, are stored in the Google App Engine Datastore

As a result, the Google Drive files managed by AODocs are automatically segregated since they belong to each customer’s specific Google Drive domain. 

The AODocs-specific data stored in the Google App Engine Datastore relies on a built-in multi-tenancy feature named 'namespace', which defines virtual “silos” within the AODocs database. Each customer is assigned a specific namespace (which is in fact the customer’s primary G Suite domain name),  and the namespace separation is implemented at the lowest possible level of the application to maximize the isolation between data structures belonging to different customers.

AODocs also maintains completely separated environment for development, pre-production and production, so that no customer data is ever used for software development and testing. 

Operational processes

AODocs is SOC2 certified, which means that AODocs internal processes for HR, support and operations are regularly assessed by an independent audit firm, who validates the compliance of our internal controls with the SOC2 framework. Our latest SOC2 audit report is available to our customers upon request. 

AODocs is also a 'Recommended for G Suite' application, and as part of this program, is regularly audited by Google about the security of its application.

AODocs implements strict internal security policies controlling how employees can handle confidential information and customer data in particular. These policies are reviewed at least annually, and employees receive periodic training on IT security.

AODocs performs periodic penetration testings on its Web application, conducted by external firms, to detect any vulnerabilities.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk