Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace z/OS
Created by Guest
Created on Jul 20, 2022

Enable zERT to Detect Partial/Failed Secure Handshakes

We would like an enhancement to zERT reporting that would detect a failed or otherwise incomplete SSL/TLS or SSH handshake/negotiation in order to distinguish it from a fully unencrypted connection. Right now zERT marks connections that failed to complete a handshake due to mismatched parameters or even a timeout as "unencrypted". This can cause misleading entries in aggregate reporting for ports, leading one to believe that there is unencrypted activity occurring when in fact the connection was never able to pass any data.


Being able to distinguish between failed encrypted sessions and established connections with no security will save time in analysis and followup for security migrations and ongoing compliance reporting. It is understood that the failed connections are not cryptographically secure and will still need to be marked as such, but an additional flag to indicate that encryption was attempted and failed will aid in analysis.

Idea priority High
  • Guest
    Reply
    |
    Jul 26, 2022

    Great idea -- I was about to suggest something similar but then I found this one :)


    zERT SMF records are a great source of information as they offer very detailed auditing and profiling information. We use them almost on a daily basis to generate reports as well as to review our systems' compliance (e.g. TLS versions and cipher suites in use, session handling or expiring certificates).


    The focus of this information, however, seems to be on "successful" sessions. We'd highly appreciate if information on a similar level of detail was added for failed sessions. For instance, it would be great to have access to the level and description of TLS alert messages as well as the types of the last TLS message which was sent and/or recieved for a given session. Recently, we had a case where our colleagues ran into problems when they tried to migrate a production system to encrypted Db2 connections. Since they were under pressure to get the system up again (and they did not inform us about the migration in the first place :) ), there was no time to take IP packet traces which would probably have helped us to find the reason for the connection failures. According to the SMF 119.2 records, the TCP sessions in question ended with SMF119AP_TTTTLSCS=X'02'. But that's it...