80% of GDPR sensitive information is NOT in databases


This is making it harder to comply.
Is there a solution?

In most organisations, the following processes (manual or automated) potentially contain Personal Data, and have to be reviewed and re-organised in order to comply with the regulation:

  • employee management
  • salary management
  • customer and supplier contacts
  • direct marketing
  • accounting
  • video surveillance
  • business specific processes:
    • consulting
    • interventions
    • ...

Where is all of the Personal Data stored?

Structured databases: About 10% to 30% of your content volumeExamples: ERP, CRM, BPM, Custom database applications
Unstructured data: About 70% to 90% of your content volumeExamples: File server, Mail server, DMS - eCM Paper

Big / Profiling Data

Examples: Indexes, Mathematical profiles


In order to comply with GDPR, organisations have to identify where exactly the Personal Data is processed and stored. Both the internal and external systems count, and every process needs to guarantee the adherence to the regulation.  

It is obvious that such a variety of systems require different approaches and solutions. If this is not automated intelligently (e.g. taking the different sources and types of information into account, automatically),then this will involve a lot of work.

Discover how Knowliah automatically understands your data – no matter how scattered it is or where it is stored – and decides how to assure GDPR compliancy, without a huge impact on the organization.

Find out more by reading our white paper around "5 steps to minimize GDPR efforts" or contact us for more information:

Request this whitepaper

Share this insight