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 Not under consideration
Workspace z/OS
Created by Guest
Created on Sep 15, 2022

Enhance zERT to Detect Non AT-TLS connections.

The product only identifies traffic if it uses ATTLS for encryption. Not all products or app servers connecting to us use ATTLS. For example, MFT is AES256 and yet they show up as unsecured. Same with CICS gateway and others.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 28, 2022
    zERT already collects TLS information from connections that do not use AT-TLS. This was an important design goal for zERT from the very beginning. There are a number of reasons zERT might report a protected connection as unprotected. Some of those reasons are addressed in Idea ZOS-I-3413 ("Enhance zERT discovery to be more accurate in recognizing and recording TLS sessions with very large handshake messages and unusual timing"). Others are documented in the z/OS Communications Server IP Configuration Guide under the heading "What are the limitations for zERT discovery?" As we learn about other conditions that can produce unexpected zERT results, we will try to document them. If you have specific connections that are producing unexpected zERT results, please open a case with the Communications Server support team so we can help you understand the data and the conditions behind it. Since the basic premise of this Idea is incorrect, this Idea is declined.