IBM z/OS Communications Server z/OS Encryption Readiness Technology (zERT)

© 2020 IBM Corporation
IBM z/OS Communications Server
z/OS Encryption Readiness Technology (zERT)
Chris Meyer, CISSP – meyerchr@us.ibm.com
June, 2020

IBM z/OS Encryption Readiness Technology
2
Please note
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice
and at IBM’s sole discretion.
Information regarding potential future products is intended to outline our general product direction and it should
not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment, promise, or legal
obligation to deliver any material, code or functionality. Information about potential future products may not be
incorporated into any contract.
The development, release, and timing of any future features or functionality described for our products remains
at our sole discretion.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled
environment. The actual throughput or performance that any user will experience will vary depending upon
many factors, including 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 results similar to those stated here.

3
Agenda
 Background – why zERT?
 zERT overview
 Configuring zERT Discovery and Aggregation
 zERT Network Analyzer
 zERT support in other products
 Considerations
 Summary

4
Agenda
 zERT overview
 Considerations
 Summary

5
Background: Cryptographic network protection on z/OS
z/OS provides 4* main mechanisms to protect TCP/IP traffic:
TLS/SSL direct usage
• Application is explicitly coded to use these
• Configuration and auditing is unique to each application
• Per-session protection
• TCP only
Application Transparent TLS (AT-TLS)
• TLS/SSL applied in TCP layer as defined by policy
• Configured in AT-TLS policy via Network Configuration Assistant
• Auditing through SMF 119 records
• Typically transparent to application
• TCP/IP stack is user of System SSL services
Virtual Private Networks using IPSec and IKE
• “Platform to platform” encryption
• IPSec implemented in IP layer as defined by policy
• Auditing through SMF 119 records – tunnel level only
• Completely transparent to application
• Wide variety (any to all) of traffic is protected
• Various topologies supported (host to host, host to gateway, etc.)
• IKE negotiates IPSec tunnels dynamically
Secure Shell using z/OS OpenSSH
• Mainly used for sftp on z/OS, but also offers secure terminal access and
TCP port forwarding
• Configured in ssh configuration file and on command line
• Auditing via SMF 119 records
• TCP only
1
2
3
4
TCP/IP
Comm
Server
Application
JSSE
DB2, CICS, IMS Connect,
Guardium, FTP, TN3270,
JES/NJE, RACF RRSF, ….
AT-TLS
Protected
Protected
TLS/SSL
System SSL
System SSL
1
2
IPSec
Systems
Protected
Any application
or subsystem
VPN
IKE
IPSec
3
Open SSH
SSH
Protected
4
MQ, CICS,
Connect:Direct, …
WAS, Java
applications
sftp, TCP
appls (port
forwarding)
* - z/OS also provides Kerberos support, but that is not covered in this presentation

6
Given all these mechanisms, configuration methods
and variation in audit detail…
 How can I tell…
– Which traffic is being protected (and which is not)?
– How is that traffic being protected?
• Security protocol?
• Protocol version?
• Cryptographic algorithms?
• Key lengths?
• …and so on
– Who does on the traffic belong to in case I need to
follow up with them?
 How can I ensure that new configurations adhere to
my company’s security policies?
 Once I’ve answered the above questions, how can I
provide the information to my auditors or compliance
officers?
 Many factors driving these questions:
– Regulatory compliance (corporate, industry, government)
– Vulnerabilities in protocols and algorithms
– Internal audits
– …and so on
TCP/IP
Comm
Server
Application
JSSE
DB2, CICS, IMS Connect,
Guardium, FTP, TN3270,
JES/NJE, RACF RRSF, ….
AT-TLS
Protected
Protected
TLS/SSL
System SSL
System SSL
1
2
IPSec
Systems
Protected
Any application
or subsystem
VPN
IKE
IPSec
3
Open SSH
SSH
Protected
4
MQ, CICS,
Connect:Direct, …
WAS, Java
applications
sftp, TCP
appls (port
forwarding)
Background: …so which traffic do I have and how is it protected?

7
Agenda
 zERT overview
 Considerations
 Summary

8
Overview: z/OS Encryption Readiness Technology (zERT – 1 of 2)
 zERT positions the TCP/IP stack as a central collection point and repository for
cryptographic protection attributes for:
– TCP connections that are protected by TLS, SSL, SSH, IPsec or have no recognized
cryptographic protection
– Enterprise Extender connections that are protected by IPsec or have no recognized
cryptographic protection
• Each peer-to-peer UDP port is considered a separate EE connection
• In this presentation, we’ll focus on TCP examples
 Two methods for discovering the security sessions and their attributes:
– Stream observation (for TLS, SSL and SSH) – the TCP/IP stack observes the protocol
handshakes as they flow over the TCP connection
– Advice of the cryptographic protocol provider (System SSL, ZERTJSSE, OpenSSH,
TCP/IP’s IPsec support)
 Reported through SMF 119 records via:
– SMF and/or
– Real-time NMI services

9
Overview: z/OS Encryption Readiness Technology (zERT – 2 of 2)
 zERT Discovery – available in V2R3
– Attributes are collected and recorded at the connection level
– SMF 119 subtype 11 “zERT Connection Detail” records
– These records describe the cryptographic protection history of each TCP and EE
connection
– Measures are in place to minimize the number of subtype 11 records, but they could still be very
voluminous
 zERT Aggregation – available via V2R3 new function APAR PI83362
– Attributes collected by zERT discovery are aggregated by security session
– SMF 119 subtype 12 “zERT Summary” records
– These records describe the repeated use of security sessions over time
– Aggregation can greatly reduce the volume of SMF records while maintaining the fidelity of the
information – well suited for reporting applications
 zERT Network Analyzer – available via V2R3 new function APAR PH03137 (but latest PTF always
has full install image)
– Web-based (z/OSMF) UI to query and analyze zERT Summary (subtype 12) records
– Intended for z/OS network security administrators (typically systems programmers)

10
Overview: Continuous Delivery!
Also, zERT Network Analyzer new function APARs PH16222 (V2R3) and PH16223
(V2R4) introduced in 1Q 2020 provides important database administration and
schema changes. Subsequent (2Q 2020) new function APARS PH24492 (V2R3)
and PH24494 (V2R4) build on these changes (these co-req z/OSMF APAR PH24579)

11
Overview: zERT Discovery (1 of 2)
Written at various events in a TCP or EE connection’s life:
 Connection Initiation (event type 1)
– Describes protection state when connection was
created (for TCP, state as established within the first 10
seconds of the connection’s life)
– Not usually written for short-lived TCP connections
 Protection State Change (event type 2)
– Describes significant changes in protection state
(security session added, deleted, or modified)
 Connection Termination (event type 3)
– Describes protection state when connection terminated
– Has an accompanying Connection Initiation record
 Short Connection Termination (event type 4)
– Describes protection state when connection terminated
– Written for short-lived TCP connections (less than 10
seconds long)
Also written when zERT is enabled (5) or disabled (6). Event type
is the only zERT information in these records.
Zero or more
of these will
be present

12
Overview: zERT Discovery (2 of 2)
What is collected and recorded?
 Attributes of the connection and its security sessions
– Significant attributes
• Identifying attributes like IP addresses, ports, jobname, userid, etc.
• Protection attributes like protocol version, cryptographic algorithms, key lengths, etc. Changes in these
cause a protection state change record to be written if they change
– Informational attributes like protocol session identifiers, session or certificate expiry data and certificate serial
numbers are recorded for informational purposes only. When recorded, the values of such attributes are taken
at the time the SMF record is written. Changes in these attributes do not constitute a significant change and
will not result in the creation of a change event record
 zERT does not collect, store or record the values of secret keys, initialization vectors, or any other secret
values that are negotiated or derived during cryptographic protocol handshakes
 zERT monitors the cryptographic protection attributes of all TCP and EE connections that terminate on the local
z/OS TCP/IP stack. This does NOT include connections that terminate in a z/OS Container Extension (zCX)
since they are considered to be routed traffic by z/OS TCP/IP. The cryptographic protection of zCX container-
related connections should be monitored using the same techniques used for other container-based traffic in your
enterprise.
 TLSv1.3 support is added to zERT in V2R4.
See the z/OS Communications Server IP Programmer’s Guide for all the details

13
Overview: zERT Aggregation (1 of 3)
Workloads that consist of large numbers of frequent short-lived connections could generate
huge volumes of zERT subtype 11 records
Some measures are already taken in zERT Discovery to reduce the number of subtype 11 records (timers and “Short-
lived Connection Termination” records), but in environments that manage thousands of connections per hour or minute,
the number of subtype 11 records can still be very large
Local
CICS
region
remote
client
1
remote
client
20
...
SMF
30 min
SMF interval
20,000 SMF 119-11 per minute
600,000 per SMF interval
(At least one per connection)
20suchclients

14
Zero or one
of these will
be present
Overview: zERT Aggregation (2 of 3)
 zERT Aggregation summarizes the repetitive use of
security sessions over time
– From the server’s perspective (based on server IP
address, server port, & client IP address)
– Regardless of whether z/OS is the client or the
server
 Summaries are written at regular intervals (either SMF
interval or a interval configured specifically for
zERT Aggregation) through SMF 119 zERT summary
(subtype 12) records which contain:
– Connection attributes (Server IP addr, server port,
client IP addr, transport protocol)
– Significant security attributes
– Statistics (connection counts, byte counts, etc.)
 With aggregation, the same example scenario from
the previous page would result in 20 SMF 119
subtype 12 records per interval – one per client TLS
session

15
Overview: zERT APIs (1 of 2)
Real-time network monitoring services
 Used by 3rd party Network Monitor products to collect SMF data in near real-time
 Two Network Monitoring Interfaces (NMIs):
– SYSTCPER service for collecting zERT Connection Detail (subtype 11) SMF records
– SYSTCPES service for collecting zERT Summary (subtype 12) SMF records
 Both use the same programming model as SYSTCPCN (TCP connection) service
– Clients connect to SYSTCPER/SYSTCPES service over an AF_UNIX socket
– Access control via SAF: EZB.NETMGMT.sysname.tcpprocname.SYSTCPER or
EZB.NETMGMT.sysname.tcpprocname.SYSTCPES
– Newly-generated SMF records are written to the service in real time
– Server sends sequence of token records, each of which describes a data buffer that contains
requested SMF records
– For each token record, client uses a built-in function to copy SMF data into own buffers
See the z/OS Communications Server IP Programmer’s Guide for details

16
Overview: zERT APIs (2 of 2)
SIOCSHSNOTIFY IOCTL (for System SSL applications)
See the z/OS Communications Server IP
Programmer’s Guide for details and a coding example
• For System SSL application programs
that initiate TLS session mid-stream
• Use this interface ONLY IF:
• Your program calls the System SSL gsk_*
APIs directly for TLS/SSL protection (i.e., it is
NOT protected by AT-TLS or another TLS/SSL
provider like JSSE)
• TLS session is initiated after one or more
bytes of application-specific data flow over
the TCP connection (this is not the typical case)
• Re-activates zERT stream observation
immediately before a TLS/SSL handshake begins.
• zERT stream observation is required for sessions
created by System SSL
• Stream observation automatically activated when a
TCP connection is first established, but is disabled as
quickly as possible
• As such, handshakes that occur mid-stream will not be
observed without an explicit notification from the
program that’s invoking System SSL APIs
• Inbound and outbound buffers must be flushed before
issuing this IOCTL
• Note that AT-TLS internally provides the notification that
zERT needs in the mid-stream handshake scenario.
IBM Sterling Connect:Direct relies on this interface.
Install Connect:Direct APAR PI77316 to ensure that C:D
connections are properly monitored by zERT.

17
Agenda
 zERT overview
 Considerations
 Summary

18
Configuring: The steps
1. Enable SMF 119 records in SMF (PARMLIB)
2. Enable zERT monitoring (TCPIP profile)
3. Specify recording destinations (TCPIP profile)
4. Verification (NETSTAT and DISPLAY TCPIP commands)

19
Configuring: 1. Enable SMF 119 records in SMF (PARMLIB)
In your PARMLIB(SMFPRMxx):
 Ensure that SMF 119 records are enabled (SYS(TYPE(119)… )
 OPTIONAL : If you plan to use Aggregation and want to base the recodrding of SMF 119-12 records on
the system’s SMF interval, ensure that your SMF interval is set appropriately (INTVAL and INTERVAL(SMF))

20
Configuring: 2. Enable zERT monitoring (TCPIP profile)
In your TCPIP profile data set:
 GLOBALCONFIG ZERT controls zERT in-memory monitoring (default is NOZERT)
GLOBALCONFIG ZERT [AGGRegation]| NOZERT
AGGRegation subparameter enables aggregation function
agg-subparms are: INTVAL SMF | interval [SYNCVAL hh:mm ]
INTVAL is the recording interval:
SMF says to use the system’s SMF interval (like before – this is the default)
interval is a specific interval in hours (1-24)
SYNCVAL hh:mm specifies the time of day from which INTVAL is calculated (only
meaningful when a non-SMF interval is specfified – default is 00:00)
Specifying a non-SMF recording interval reduces the number of SMF 119-12 records written.
Note that in some cases, it may also lead to higher consumption of above-the-bar private
memory. In most cases, this should not be an issue, but if it is, you may need to strike a
balance between saving SMF storage space and reducing 64-bit memory consumption by
specifying a shorter intval value.
 Note that the discovery and aggregation in-memory functions are enabled independently of the destinations to
which records are written.
 Can be dynamically enabled or disabled
 Can be configured by hand or through the z/OSMF Network Configuration Assistant for z/OS Communications
Server
with APARs PH25049 (V2R4)
and PH24543 (V2R3)GLOBALCONFIG ZERT [AGGRegation [agg-subparms]]| NOZERT

21
In your TCPIP profile data set:
• SMFCONFIG controls writing of zERT records to System Management Facility
• SMFCONFIG TYPE119 ZERTDetail | NOZERTDetail
• SMFCONFIG TYPE119 ZERTSUMmary | NOZERTSUMmary
• Defaults are NOZERTDetail and NOZERTSUMmary
• NETMONITOR controls writing of zERT records to real-time network monitoring services
• NETMONITOR ZERTService | NOZERTService
• NETMONITOR ZERTSUMmary | NOZERTSUMmary
• Defaults are NOZERTService and NOZERTSUMmary
• Note that the discovery and aggregation in-memory functions are enabled independently of
the destinations to which records are written.
• Can be dynamically enabled or disabled
• Can be configured by hand or through the z/OSMF Network Configuration Assistant for z/OS
Communications Server
Configuring: 3. Specify recording destinations (TCPIP profile)

22
Configuring: Using Network Configuration Assistant (1 of 3)
TCP/IP profile configuration tasks
Configure Network Security
Select “customize” to enable
coding of this parameter
Checkbox enables zERT in-memory montoring
Dropdown controls coding of
AGGREGATION subparameter
Brings you to the next page
Aggregation requires Network Configuration Assistant APAR PI94208

23
.
.
.
.
.
.

24
24

25
Configuring: 4. Verifying zERT configuration
NETSTAT CONFIG or DISPLAY TCPIP,tcpipprocname,NET,CONFIG command shows current configuration:

26
Agenda
 zERT overview
 Considerations
 Summary

27
zERT Network Analyzer Overview
• A z/OSMF plugin:
• Web UI makes zERT data consumable for z/OS network security administrators (typically systems programmers)
• Access to UI controlled through SAF resource IZUDFLT.ZOSMF.ZERT_NETWORK_ANALYZER in the ZMFAPLA class
• Used primarily to investigate specific network encryption questions (but could also be used for periodic report generation)
• The IBM zERT Network Analyzer is available via new function APAR PH03137 (but latest PTF always has full install
image)
SMF
SMF
SMF
z/OS
WAS Liberty
z/OSMF
zNA plugin
zNA DB
(Db2 for
z/OS)
Contains zERT summary data
for some fixed range of time
SMF dump data sets
generated by IFASMFDP
or IFASMFDL
Users build queries over a variety of attributes:
• Specific scope attributes like Sysplex / system /
stack, IP addresses / server port, z/OS role (client or
server) and range of dates
• Specific security attributes like crypto protocol,
protocol version, crypto algorithms and key lengths,
etc.

28
zERT Network Analyzer Overview: Welcome page and layout
Click here to import SMF dump data
sets and to prune old data out of the
database
Click here to create, modify, and
run queries over the imported
data
Click here to view the query
results (more on this in the
following slides)
Click here to modify application
and database settings
Click here for topical
help in the IBM
Knowledge Center

29
zERT Network Analyzer Overview: Report summary view (1 of 2)
TCP Server Traffic: Summary of all
the traffic connecting in to servers
running on local z/OS systems
TCP Client Traffic: Summary of all
the traffic connecting out to
servers running on other systems
EE Peer Traffic: Summary of all
EE traffic connected to local z/OS
systems
Exports the query results and all
related details to a comma
separated value file
Each row summarizes traffic for
one server (TCP) or local peer
(EE)
Click this icon to select the
specific data points (columns) to
display and which to hide

30
zERT Network Analyzer Overview: Report summary view (2 of 2)
Data points are organized by category.
The selected points will be displayed in
both the summary and client detail views.
Click this icon to select the
specific data points (columns) to
display and which to hide

31
zERT Network Analyzer Overview: Client detail view for a given server
Click on a summary row to open
the client view for that server
Each row contains information
for a specific client to the
selected server. Note that the
columns displayed for the clients
are the same ones selected for
the server summary.
Select one or more clients to
enable the “View security session
details” button
Select one or more clients to
enable the “View security session
details” button. Click on that
button to go to the next slide

32
zERT Network Analyzer Overview: Security session details view (1 of 2)
Select here between cryptographic
protocols. Only those that apply to
this client-server pair will be in the
dropdown list.
Select here between different categories of
cryptographic attributes for the selected protocol. For
example, TLS offers basic Cryptographic details,
Certificate details, and Distinguished Name details.
Click here to select the
columns to display in the
security session details view.
Note that the options change
according to the specific
categories of attributes
selected in the second
dropdown.

33
zERT Network Analyzer Overview: Security session details view (2 of 2)
Select here between cryptographic
protocols. Only those that apply to
this client-server pair will be in the
dropdown list.
Click here to select the
columns to display in the
security session details view.
Note that the options change
according to the specific
categories of attributes
selected in the second
dropdown.
Select here between different categories of
cryptographic attributes for the selected protocol. For
example, TLS offers basic Cryptographic details,
Certificate details, and Distinguished Name details.

34
zERT Network Analyzer Overview: TCP Client Traffic report
Click on a foreign server row to
expand the list of all the local clients
Client details include the job
name and user ID of each local
client

35
zERT Network Analyzer: Setup and configuration (1 of 3)
NOTE: In most shops, setting up the zERT Network Analyzer will require some coordination between
your z/OS networking team, your z/OS security team and your Db2 for z/OS team. The steps that
need to be accomplished are:
1. Enable the zERT Network Analyzer plugin in z/OSMF IZUPRMxx parmlib member. For example:
PLUGINS(COMMSERVER_CFG,SOFTWARE_MGMT,…,ZERT_ANALYZER)
2. Edit the IZUNASEC* sample JCL stream to add names of z/OS user IDs that are to be permitted
access to the plugin. For example:
/* Connect the users of the zERT Network Analyzer to the */
/* zERT Network Analyzer group */
CONNECT USER1 GROUP(IZUZNA)
CONNECT USER2 GROUP(IZUZNA)
/* End connect the users to zERT Network Analyzer group */
3. Run the IZUNASEC* job to create the appropriate SAF resources to control access to the plugin and
grant the appropriate permissions for the appropriate z/OS user IDs
4. Create the zERT Network Analyzer database objects…
* - IZUNASEC works with RACF. Check with your vendor if you use a different security manager product.

36
 Requires Db2 for z/OS 11 or higher
 Tooling is provided to allow DBAs to create zERT Network Analyzer database objects according to their own local
conventions
– IZUZNADT and ( ) IZUZNADA – DDL templates
with variables for appropriate names and values
– IZUZNADI – sample variable substitution file (provides
values for each variable in the IZUZNADT/A template)
– IZUZNADG – REXX exec that reads IZUZNADT/A and
IZUZNADI and produces a customized DDL data set that your Db2 for z/OS DBAs can use to create the required
database objects
 JDBC binding needs to be created on Db2 side (not done automatically)
 The zERT Network Analyzer performs all database operations under a single user ID that is configured via the
database settings panel. This user ID must be granted the appropriate database privileges
 Once the zERT Network Analyzer database is created, the required JDBC connectivity parameters must be configured
on the Database Settings panel of the UI
– When a user logs into the UI, they will be forced to the Database Settings panel
– Once the correct information is successfully configured, you can use the zERT Network Analyzer

37
Parameterized values in IZUZNADT and IZUZNADA templates:
Both templates:
<authId> - z/OS auth ID for the Db2 objects
<database> - Database name
<QRTDatabase> - Query Result Tables (QRT) database name
<QRTParts> - Number of QRT partitions
<tableStoGrp> - Storage group name - table spaces
<indexStoGrp> - Storage group name - indexes
<tablePriqty> - min primary space alloc - tables
<tableSecqty> - min secondary space alloc - tables
<indexPriqty> - min primary space alloc - indexes
<indexSecqty> - min secondary space alloc - indexes
<table4KbpName> - 4K buffer pool name - tables
<table8KbpName> - 8K buffer pool name - tables
<indexBpName> - Buffer pool name - indexes
For each table:
- Table space name
- Index names
IZUZNADA only:
<schema> - Schema name
For each table:
- Table names
with APAR PH16222 (V2R3), PH16223 (V2R4)

38
Agenda
 zERT overview
 Considerations
 Summary

39
Other products with zERT support (as of today)
IBM is aware of the following products that have shipped support for zERT data. Note that this may not be a comprehensive
list as there may be others of which IBM is currently unaware:
 IBM zSecure Audit V2.3 (subtype 11 and subtype 12 records)
 IBM QRadar SIEM (supports what zSecure feeds it)
 Merrill Technologies MXG (feeds subtype 11 and subtype 12 records into SAS)
 Broadcom NetMaster Network Management for TCP/IP 12.2.03 (subtype 11 records through NMI)
 BMC Mainview for IP 3.6 (subtype 11 and subtype 12 records through NMI)
 Vanguard Advisor 2.3 (subtype 11 records)
 IntelliMagic Vision (subtype 12 records)
 IBM Z Common Data Provider 2.1.0 (subtype 11 and 12 records)
 IBM NetView Version 6.3 (supports subtype 11 records through NMI)
 IBM Omegamon for Networks on z/OS version 550, fixpack 4 (APAR OA57939 - subtype 11 records through NMI)
 Pacific Systems Group’s Spectrum SMF Writer (subtype 11 and 12 records)

40
Agenda
 zERT overview
 Considerations
 Summary

41
Considerations (1 of 2)
 zERT can generate very large volumes of subtype 11 records, depending on the number of
connections supported by your z/OS system.
– Please plan accordingly
– Consider only capturing subtype 12 records on a regular basis and only capture subtype 11s for
limited times when investigating specific traffic. You can also use a non-SMF aggregation
recording interval to reduce the number of subtype 12 records captured per day.
 zERT monitors TCP and Enterprise Extender traffic. All other IP protocols are unmonitored.
 zERT monitors TCP and EE connections that terminate on the local TCP/IP stack.
– It does not monitor routed traffic
– Since connections that terminate in zCX containers are treated as routed traffic (not local) by the
z/OS TCP/IP stack, zCX traffic is not monitored by zERT
 zERT does not store or record the values of secret keys, initialization vectors, or any other secret
values that are negotiated or derived during cryptographic protocol handshakes.
 Regardless of the prior point, the zERT data that is recorded provides a fairly complete
picture of the z/OS system’s network cryptographic protection profile. As such, you
should take appropriate steps to protect the recorded SMF data as well as access
to the zERT real-time network monitoring services.

42
Considerations (2 of 2)
 zERT only monitors connections that are established after zERT is enabled (or re-enabled).
– If you disable and later re-enable zERT, it will no longer monitor any of the connections that
existed before re-enabling.
– To ensure the most complete monitoring, enable zERT in your TCP/IP profile
 TCP traffic protected by other TLS/SSL implementations (JSSE, OpenSSL, other SSH, etc.) will only
be reported through stream observation. Limitations:
– Only reports initial handshake as long as it is the first thing to flow over the connection. zERT
stream observation has no visibility to rehandshakes or early termination of security sessions
– zERT has no visibility to attributes that are negotiated during the initial handshake using
encrypted messages
 There are a small number of System SSL applications that cannot be monitored and are therefore
reported as being unprotected. These are applications that:
– Send or receive application-specific data before initiating the TLS/SSL session
– Do not use the SIOCSHSNOTIFY ioctl
 In certain mixed-release environments, some IPSec-related attributes will not be
available for reporting

43
Summary: Customer value
 zERT SMF 119 Connection Detail (subtype 11) records:
– Provide ample opportunity for correlation to records (SMF or otherwise) from other applications,
workloads and devices to help build an larger picture of individual network connections to z/OS
– Can reveal traffic that is being double-protected
 zERT SMF 119 Summary (subtype 12) records: Provide the same level of cryptographic detail in a
condensed format, typically with a great reduction in the volume of SMF records vs. Connection Detail
records. Even greater reduction possible using a non-SMF aggregation recording interval
 Several network monitoring and audit-related products now support zERT data – some of them
providing near real-time views based on Connection Detail records
 The zERT Network Analyzer:
– Makes it easy for z/OS network security admins to consume, query and search zERT data
– Great flexibility in creating queries that zero in on the specific systems, endpoints, time spans, and
security attributes of interest. These queries can be built for regular compliance checks or for
special purpose investigations
– Query results can be viewed through a browser or exported to a CSV file for post-processing
 zERT support for TLSv1.3 is added to z/OS V2R4

44
For more information
URL Content
http://ibm.biz/thingsaboutzert IBM zERT “all-in-one” page
https://www.ibm.com/community/z/software/comm-server IBM Communications Server blog
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/co
m.ibm.zos.v2r4.cs3/cs3.htm
IBM Communications Server library

45
Thank you!

46
Notices and disclaimers (1 of 2)
© 2018 International Business Machines Corporation. No part of this
document may be reproduced or transmitted in any form without
written permission from IBM.
U.S. Government Users Restricted Rights — use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to
products that have not yet been announced by IBM) has been
reviewed for accuracy as of the date of initial publication and could
include unintentional technical or typographical errors. IBM shall have
no responsibility to update this information. This document is
distributed “as is” without any warranty, either express or
implied. In no event, shall IBM be liable for any damage arising
from the use of this information, including but not limited to, loss
of data, business interruption, loss of profit or loss of
opportunity. IBM products and services are warranted per the terms
and conditions of the agreements under which they are provided.
IBM products are manufactured from new parts or new and used
parts.
In some cases, a product may not be new and may have been
previously installed. Regardless, our warranty terms apply.”
Any statements regarding IBM's future direction, intent or
product plans are subject to change or withdrawal without
notice.
Performance data contained herein was generally obtained in a
controlled, isolated environments. Customer examples are presented as
illustrations of how those
customers have used IBM products and the results they may have
achieved. Actual performance, cost, savings or other results in other
operating environments may vary.
References in this document to IBM products, programs, or services does
not imply that IBM intends to make such products, programs or services
available in all countries in which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared
by independent session speakers, and do not necessarily reflect the
views of IBM. All materials and discussions are provided for informational
purposes only, and are neither intended to, nor shall constitute legal or
other guidance or advice to any individual participant or their specific
situation.
It is the customer’s responsibility to insure its own compliance with legal
requirements and to obtain advice of competent legal counsel as to
the identification and interpretation of any relevant laws and regulatory
requirements that may affect the customer’s business and any actions the
customer may need to take to comply with such laws. IBM does not
provide legal advice or represent or warrant that its services or products
will ensure that the customer follows any law.

47
Notices and disclaimers (2 of 2)
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products about
this publication and cannot confirm the accuracy of 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. IBM does not warrant
the quality of any third-party products, or the ability of any such third-
party products to interoperate with IBM’s products. IBM expressly
disclaims all warranties, expressed or implied, including but not
limited to, the implied warranties of merchantability and fitness
for a purpose.
The provision of the information contained herein is not intended to,
and does not, grant any right or license under any IBM patents,
copyrights, trademarks or other intellectual property right.
IBM, the IBM logo, ibm.com and [names of other referenced IBM
products and services used in the presentation] are trademarks of
International Business Machines Corporation, registered in many
jurisdictions worldwide. Other product and service names might
be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at "Copyright and trademark
information" at: www.ibm.com/legal/copytrade.shtml.
.

IBM z/OS Communications Server z/OS Encryption Readiness Technology (zERT)

More Related Content

What's hot (20)

Similar to IBM z/OS Communications Server z/OS Encryption Readiness Technology (zERT) (20)

More from zOSCommserver (13)

Recently uploaded (20)

IBM z/OS Communications Server z/OS Encryption Readiness Technology (zERT)