Product Documentation

1. Zuse Overview

2. Getting Started
2.1 Setting up your organization
2.2 Home Page
2.3 Entities in Zuse
2.4 Workspace details page

3. Data Import
3.1 Add new dataset
3.2 Import data from local files
3.3 Import data from local databases
3.4 Import data from cloud databases
3.5 Import data from FTP servers
3.6 Import data from URLs
3.7 Import data from Google BigQuery
3.8 Saved data connections
3.9 Schedule import
3.10 Reload data

4. Data Transformation
4.1 Zuse Studio
4.2 Column transformations
4.3 Dataset transforms
4.4 Datatypes

5. Data Export
5.1 Export options
5.2 Local files
5.3 Export data to FTP
5.4 Cloud Storage Services
5.5 Cloud databases
5.6 Export data to Google BigQuery
5.8 Schedule export
5.9 Processing history and processed data

6. Sharing & Collaboration
6.1 Workspaces
6.2 Datasets
6.3 Ruleset templates
6.4 Roles and permissions
6.5 Data cataloguing

7. Privacy & Compliance
7.1 Encryption at Zuse
7.2 GDPR Compliance in Zuse
7.3 HIPAA Compliance in Zuse

8. FAQs

View Documentation

Security & Data Protection

GDPR Compliance in Zuse

Features that Zuse offers with respect to GDPR compliance:

· Marking Personal Data
· Encryption at Rest
· Enhanced Data Privacy and Security
· Right to Data Portability
· Right to Erase and Forget Data
· Zuse's GDPR Compliance and Privacy Policy

Field Level Encryption

The sensitive data you input into the application, or the sensitive service data, is stored in respective Zuse service database. Data in these are encrypted according to AES 256 standard with AES/CBC/PKCS5Padding mode. The data that is encrypted at rest varies with the services you opt for about the data we encrypt in our services.

There are two types of field level encryption-

· Depending on the sensitivity of data
· Depending on the search functionality

File encryption

The files you create or attach are saved into our Distributed File System (DFS). The files that are encrypted at rest varies with the services you opt for about the data we encrypt in our services. The encryption happens at application layer and only the authorized application user will be able to view the data.

URL encryption

Anything that is identifiable in the URL, say the ID of a document, that part is encrypted.

This encryption has two types- One key per Org or One key per feature. Again, this is decided by the sensitivity of data in the URL.

Backup encryption

We backup data frequently, and our backup servers are equipped with the same standard of protection as the main servers. All data we take as backup will be encrypted at rest.

Encryption of Logs

Zuse Logs uses Hadoop Distributed File System (HDFS) to store and manage logs. We use the encryption technology of Hadoop to encrypt the data while key management is handled by our KMS.

Encryption of cache

We use Redis open-source software for storing and managing cache data. If any data contains sensitive personal information, we choose to encrypt it.

Key Management

Our in-house Key Management Service (KMS) creates, stores and manages keys across all services. We own and maintain the keys using KMS. Currently, we do not have the provision to encrypt data with keys owned by the customer.

Full-disk encryption

We employ self-encrypting drives (SEDs) to support hardware-based full disk encryption. An SED is a hard disk drive (HDD) or a solid-state drive (SSD) that has an encryption circuit built into it.