Data Privacy Passports solution (referred to as Passport Controller) contain Data Controller  modules. Data Controller provides an intercept point to transform  raw  data into Trusted Data  Objects (TDO) or enforce data protection. It must be deployed on IBM Z for protection or  enforcement. Before the ETL process, the data is packaged on Z platform into a TDO, which contains  metadata, and a single protected table can be created to provide multiple views of data. In a  protected table, fields in specific (or all) columns can be TDOs rather than clear data. The data is protected at the point of extraction and is enforced at the point of consumption.  The flexible policy defines the pool of trusted users, and their access to the data based on  their role. The key lifecycle management (generation, revocation, and so on) is done within  Passport Controller. The data is encrypted with standard AES256 keys, which are all managed by the Passport  Controller. Applications access Passport Controller through industry standard Apache Hive drivers. In a production environment, applications are subject to any number of security risks external  (cyber attacks) or internal (malicious software, system administrators who use their privileged  rights for unauthorized access and many others). Secure Service Containers provide trusted  execution environments for applications by way of tamper protection during installation and  runtime, restricted administrator access, and encryption of data in-flight and at-rest. A Secure Service Container is an integrated IBM Z appliance and hosts the most sensitive  workloads and applications. They act as a highly protected and secured digital vault and  enforce security by encrypting the entire stack. The application that is running inside the  Secure Service Container is isolated and protected from outsider and insider threats. Secure Service Containers combine hardware, software, and middleware and is unique to the  IBM Z platform. Although it is called a container, it should not be confused with purely open  source containers (such as Docker). An LPAR is defined as a Secure Service Container through the HMC. A Secure Service Container features the following key advantages: All diagnostic information (debug dump data, logs) are encrypted and do not contain any  user or application data. GLYPH<SM590000> Existing applications require zero changes to use Secure Service Container; software  developers do not need to write any Secure Service Container specific programming  code. GLYPH<SM590000> End-to-end encryption of data-in-flight and data at-rest: – Automatic Network En cryption (TLS, IPSEC): Data in-flight. – Automatic volume encryption (LUKS): Data at-rest. Linux Unified Key Setup (LUKS) is  the standard way in Linux to provide volume encryption. A Secure Service Container  encrypts all data with a key that is stored within the appliance. – Protected memory: Up to 16 TB can be defined per Secure Service Container LPAR. GLYPH<SM590000> Encrypted Diagnostic Data 4.6.2 Secure Service Container 76  IBM z15 Technical Introduction