z/os Data Set Encryption In the context of pervasive encryption IBM z systems IBM Corporation

Transcription

1 z/os Data Set Encryption In the context of pervasive encryption IBM z systems 1

2 Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a more complete list of IBM Trademarks, see *BladeCenter, CICS, DataPower, DB2, e business(logo), ESCON, eserver, FICON, IBM, IBM (logo), IMS, MVS, OS/390, POWER6, POWER6+, POWER7, Power Architecture, PowerVM, PureFlex, PureSystems, S/390, ServerProven, Sysplex Timer, System p, System p5, System x, z Systems, System z9, System z10, WebSphere, X-Architecture, z13, z Systems, z9, z10, z/architecture, z/os, z/vm, z/vse, zenterprise, zseries The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured Sync new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-ibm products is obtained Sync the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. IBM z systems 2

3 z/os Data Set Encryption Some terminology IBM z systems 3

4 Terminology Data-encrypting key An encryption key that is used to encrypt and decrypt data Data key A type of data-encrypting key Key-encrypting key (KEK) A key that encrypts or wraps other keys Master key A special key-encrypting key CPACF wrapping key A special key-encrypting key that is generated at LPAR activation (HSA) Secure key A data-encryption key that is encrypted by a master key or KEK Clear key A data-encryption key that is NOT encrypted by any other key Protected key A data-encryption key that is encrypted by a CPACF wrapping key Operational key A key that is NOT a master key, such as a data-encrypting key IBM z systems 4

5 How z/os data set encryption works New data sets or group of data sets are encrypted by using SAF controls or RACF and SMS policies You can specify key labels to identify encryption keys Secure keys in CKDS Protected keys in cache Authorization to view contents is based on access to the key label associated with the data set The encryption key associated with the key label is used by DFSMS to start CPACF to encrypt / decrypt the data IBM z systems 5

6 How z/os data set encryption works cont. Encrypted data sets must be extended-format and catalogued z/os data set encryption support the encryption of the following data set types: Sequential extended-format data sets, which are accessed through BSAM and QSAM VSAM extended-format data sets (KSDS, ESDS, RRDS, VRRDS and LDS), which are accessed through base VSAM and VSAM LRS A data set is defined as encrypted when a key label is supplied on allocation You can supply a key label by using keywords in any of the following source formats (by using the following order of precedence): 1. Data Facility Product (DFP) segment in the RACF data set profile 2. JCL, dynamic allocation, TSO Allocate, IDCAMS DEFINE 3. SMS data class IBM z systems 6

7 Does and dont s Data set compression Encrypted data does not compress. When a data set is allocated as compressed format, DFSMS first compresses the data; then, it encrypts the data Data sets remain encrypted during DFSMShsm and DFSMSdss migration and backup Data sets remain encrypted during hardware-based data replication services Sequential data sets support generic, tailored, or zedc compression A VSAM extended format KSDS support generic compression (only KSDS can be compressed format Encrypted data set availability at IPL MUST be started before encrypted data sets are used IBM z systems 7

8 Does and dont s contd. Encrypted data sets are supported by: Db2 (v11 with UI51358, v12 with UI51499) IMS starting from V13 on z/os 2.3 and above (z/os 2.2 after APAR OA50569) CICS See IBM Knowledge Center MQ See IBM Knowledge Center zfs New and existing zfs data can be encrypted and compressed see IBM Knowledge Center IBM z systems 8

9 z/os Data Set Encryption First steps flowchart IBM z systems 9

10 First steps z/os Allocate Key Datasets CKDS PKDS TKDS Exit No Hardware Crypto Coprocessor? A Yes TKE Using TKE PPINIT Panel Master key entry panel NOTE! The TKE cannot be used to: Reencipher CKDS Change new DES or AES MK Activate reenciphered CKDS Init key data sets Load master keys Enter master keys Init key data sets IBM z systems 10

11 First steps (contd.) A SAF Define CSFKEYS class Define CSFSERV class Define DATASET class Define OPERCMDS class Access to keys in CKDS/PKDS Access to callable services + TSO panels Protect key data sets Control auth. to enter oper commands IBM z systems 11

12 Details z/os Allocate Key Datasets CKDS PKDS TKDS Create the key data sets Use JCL in SYS1.SAMPLIB CKDS: SYS1.SAMPLIB(CSFCKDS3) PKDS: No change to allocation process CKDS: SYS1.SAMPLIB(CSFTKD2) Use the common records format (KDSR) LRECL 2048 for HCR77A1 and newer Most current FMID: HCR77C1 (as of August 2018) IBM z systems 12

13 Details SAF Define CSFKEYS class Define CSFSERV class Define DATASET class Define OPERCMDS class Protect your resources Access to keys in CKDS/PKDS Access to callable services + TSO panels Protect key data sets Control auth. to enter oper commands IBM z systems 13

14 Details PPINIT Panel Init key data sets Create master keys PPINIT Panel Using the pass phrase initialization utility you can: Generate master keys using a phrase Load the AES, DES, ECC and RSA master keys to all active coprocessors Initialize the CKDS and the PKDS data sets Make them the active key data sets You cannot use this utility to change master keys Load master keys IBM z systems 14

15 Details Master key entry panel Enter master keys Init key data sets Create master keys master key entry panels Using the enhanced master key entry panel(s) : Generate master key parts for AES, DES, ECC and RSA master keys (in parts) Generate checksums and verification patterns for the keys Load the master key parts in to the CCA coprocessor Initialize the key data sets Create header record in key data sets Contains verification pattern of master keys IBM z systems 15

16 z/os Data Set Encryption Write an encrypted dataset IBM z systems 16

17 Data set write DFSMS Will determine the indicated compression type based on the DATACLASS & system default in IGDSMSxx Continue to write (compressed) data set No DFSMS Calls SAF to check for keylabel in DATASET class Yes Uses the key label specified by DFSMS to locate the protected key DFSMS Specifies the saved key label to Yes Uses the key label to locate the secure key in the CKDS CPACF Unwraps the protected key and uses the clear key value to encipher the (compressed) data Yes Is there a protected key present? No Calls the CCA coprocessor to: Unwrap key value from MK CCA coprocessor Rewraps the key value under a CPACF wrapping key to make a protected key IBM z systems 17

18 What happens in the magic box? Processes running on the CCA coprocessor during key refresh IBM z systems 18

19 z/os Data Set Encryption Read an encrypted dataset IBM z systems 19

20 Data set read DFSMS Will determine the indicated compression type based on the DFSMS DATACLASS & system default in IGDSMSxx Deny access to dataset content No DFSMS Calls SAF to check that the user is authorized to the CSFKEYS class Yes DFSMS Specifies the saved key label to Uses the key label specified by DFSMS to locate the protected key Yes Is there a protected key present? No Uses the key label to locate the secure key in the CKDS Calls the CCA coprocessor to unwrap the key value from the master key CPACF Unwraps the protected key and uses the clear key value to decipher the (compressed) data CCA coprocessor Rewraps the key value under a CPACF wrapping key to make a protected key IBM z systems 20

21 Reference & Links Links IBM Developerworks: Pervasive Encryption - zos Data Set Encryption Presentations _Best_Practices_SHARE_Pittsburgh_2014 MoP_CryptoKeyManagement_01B MoP_z14_CryptoUpdate_04A z14_introtokeymanagement Manuals z/os Cryptographic Services Integrated Cryptographic Service Facility Administrator's Guide z/os Cryptographic Services Integrated Cryptographic Service Facility Overview Redbook: System z Crypto and TKE Update Redbook: Getting Started with z/os Data Set Encryption TechDoc: Another Paper on CPACF Clear Key and CCF Functionality Whitepaper: A Clear Key / Secure Key / Protected Key Primer Whitepaper: A Synopsis of z Systems Crypto Hardware IBM z systems 21

22 End of Presentation Questions and Comments please send to: IBM z systems 22