With every request to the WITDOM platform for processing of new data, the data are first transformed into the common WITDOM format (if it is not in this format already) and then stored in the WITDOM Storage for further processing.

Key Manager (KM)

KM Java client: Alberto Crespo (Atos). KM C++ client: Juan Troncoso (UVIGO). KM Server : Manca Bizjak (XLAB)

The WITDOM Key Management component provides management of secrets (for example, private and public encryption keys or credentials to access the storage) that are required for operations run by protection components.

The WITDOM Identity and Access Management (IAM) component ensures that sensitive data in WITDOM is only accessible to individuals who are granted explicit entitlements to specific services, and has the ability to monitor / audit access to data and operations.

IAM license: Apache 2.0

The Protection Orchestrator (PO) coordinates several protection components and services in order to effectively protect data before they leave a trusted environment for processing or storing reasons. The PO is in charge of parsing the protection configuration of an application and applying it.


Gonzalo Jiménez Balsa (Gradiant)

The main goal of the Broker in WITDOM is to support communication between the applications, modules and services both in the trusted and untrusted domain, even when they do not know the location of the target.