Edit

Processing sensitive data

Glossary

Sensitive data is defined as information that is protected against unwarranted disclosure. Access to sensitive data must be safeguarded. Protection of sensitive data can be required for legal or ethical reasons, for issues pertaining to personal privacy, or for proprietary considerations. Also, study the following articles:

• Personally Identifiable Information (PII)

• Protected Health Information (PHI)

• Health Insurance Portability and Accountability Act (HIPAA)

• General Data Protection Regulation (GDPR)

General information

WorkFusion SPA can be deployed in the following two ways:

• Cloud deployment (for example, to AWS). In this case, deployment is managed either by WorkFusion or the Customer.
• On-premise deployment. It is a more secure approach leveraging all security policies and enforcements established in the customer infrastructure. The deployment is managed by the customer.

WorkFusion storage

WorkFusion (WF) platform persists (or may persist) data in the following storages:

• MySQL DB (Control Tower system data, Business Process (BP), and transactional information)
• PostgreSQL DB (WF Data Stores, WorkSpace system data)
• S3-emulated Storage (static resources, temporary or long-term BP information, depending on the implementation design and Business requirements)
• Secrets Vault
• MongoDB (temporary OCR information, self-purged)
• Nexus (BP source code, development artifacts)
• Temporary files (for example, logs, Tomcat temporal files)

Storing sensitive data in Business Process workflow

For a general use case, thorough solution designing is required to cover specific requirements (for instance, GDPR, HIPAA, and so on).

Small pieces of information (key-value type of data) can be persisted to Secrets Vault (SV).

One of the options is to encrypt sensitive data in the BP logic itself, before it’s written anywhere or passed to the next step. In this case encryption keys are stored in SV.

Best practices

• The general guideline is to store sensitive data transiently or temporarily only (or not to store at all).
• All credentials should be stored in SV (for example, for RPA usage).
• Avoid logging any sensitive data in the BP workflow.
• Pass only necessary information between BP steps.
• Enable Data Purge.
• Clean up unnecessary information from Data Stores.