Introducing data governance and lockdown configuration options
draw.io is a unique security-first diagramming tool in that we provide the application platform, but your diagram data only lives in your computer memory while you are working on it. As you can store your diagrams on your preferred enterprise-level cloud storage platforms or on your local device, draw.io gives you control over your diagram data.
Some extended editor features, such as PDF generation (
File > Export As > PDF), are only available from the draw.io server endpoints. In these cases, your diagram data is securely transmitted from your browser to our server endpoint, and when the converted file is sent back to your browser, your diagram data is deleted from the draw.io server.
Data is encrypted during all network transmission up to the endpoint processing.
Data governance regions for server endpoints
The online draw.io editor at app.diagrams.net is delivered via Cloudflare edge data centers and data transmitted outbound is directed via those same Cloudflare centers. The server endpoints are all located within AWS data centers. The features requiring server-side functionality are:
- Translation of
vsdx. draw.io understands
- Import of Gliffy files.
- Migration of EMF images embedded in
vsdxfiles. EMF licensing means only the Windows operating system may manipulate these.
- Generation of PlantUML diagrams. PlantUML is written in Java.
- Generation of PDFs of diagrams.
- Collaborative editing by sending only deltas of changes to other editors.
Wherever possible we use serverless (AWS Lambda) functionality to reduce the attack surface of the endpoints.
draw.io has server endpoints in three regions: one in the EU (in Frankfurt, Germany) and one in the US (in Northern Virginia). By default, invoking each of the above functions will use the server endpoint that is nearest to the Cloudflare data center that the request entered via. That is, geolocation is not performed on your IP address to determine the endpoint.
However, you can force the endpoint locations, rather than rely on entering the Cloudflare network at the right place. Specifying
dataGovernance region in the editor configuration to
US ensures draw.io uses your preferred server endpoint.
Data transmission lockdown
Additionally, you can use the
lockdown toggle in the editor configuration to disable data transmission apart from directly between your browser where you are editing your diagram, and the cloud platform or location you have chosen to store the diagram file.
Set server endpoints and disable data transmission
- Select Extras > Configuration to customise draw.io.
- To restrict data transmission to between your browser and your storage location, add the following JSON string:
"lockdown": true". Note the dataGovernance value is ignored with lockdown set to true.
- Click Apply to save your changes, and then reload the draw.io editor (refresh the browser page).
Data residency in Atlassian Cloud
The architectures for draw.io for Confluence and Jira Cloud are identical to those used with draw.io. However, you can set the data governance rules centrally for all users on your Confluence instance.
If you are using the draw.io apps for Confluence or Jira Cloud, Atlassian lets you additionally set your data residency region to choose where your data or in-scope product content resides. That means the content of your instance and associated metadata will be stored on servers in that region when it is at rest.
An administrator can set the server endpoint in the draw.io app Configuration in the administration settings via the JSON string.
You can also vote for our existing server endpoint deployments, or submit your own endpoint location request at the issue tracker: