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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Unfortunately ZOS-I-2386 does not adress the same issue. It is simiply another technical option for downloading todays files. This idea is about adding the CPE into the download files as a new attribute. IT is needed to enable a Security Operation Center to monitor zProduct vulnerabilities by giving zProducts a commonly across plattforms used Product ID in the CPE format that can be mapped to installed SW packages on the zSystem. The CPE can be derived from existing information so I do not understand why it is a big deal for IBM to enhance their download files.
Once this has been done, then one can easily leverage automation (such as Ansible or z/OSMF APIs) end-to-end to get z/OS security reports easier. These reports will be customized and tailored for your specific z/OS system, making them applicable to that environment.
Vulnerability management is done by an organisational unit that is working with CPE across technical plattforms using vulnerability scanner and different security tools. These working units neither have mainframe expertise (FMID, HOLDDATA…), nor do they patch systems.
They
collect information about existing threats to the organisation,
identify if the organisation is affected by this vulnerability (first line) f.e. by matching the CPE with software inventories (i.e. FLEXERA),
inform mainframe product specialists about product related vulnerabilities
track patching and remind product specialists of timely dealing with the vulnerability.
report to CISO.
This way the product specialists will be actively informed (CVSS, APAR, PTF) and they need to decide on an environmental score and if and when a ptf will be installed.
SMP/E installation can also be centralized within an organisation and not every mainframe product specialist necessarily installs software by himself and knows about HOLDDATA and FMIDs. Product specialists generally know about the product names and version numbers which IBM uses for sales, but not necessarily about technical installation details. Unfortunately product names used for IBM sales contracts differ from the product names used within the IBM security portal, therefor a unique product ID is needed.
In general the way IBM treats vulnerability information and related product IDs is confusing, probably historically grown. In contrast an organisation needs to know ALL existing vulnerabilities within their IT-Systems. Therefor it is essential to have an organisational unit working within a standardized process across all IT platforms as well as automation wherever possible.
The IBM security portal unfortunately does not support these needs sufficiently. Different product categories have different product IDs (FMID for z/OS products, CompID for z/VM + RLS) and also different ways to find out about existing vulnerabilities (primary ressources => machine readable files and only vulnerabilities with existing ptf; security notices => only human readable, vulnerability information without ptf).
The usage of a CPE could be a first step to support automation and integrate mainframe vulnerability management into a standardized central vulnerability management within an organisation. Looking into the CPE standard it makes me hope that the CPE can be derived from the information that is already existing within the portal. Hopefully it can simply be added into the download files without major costly changes for IBM.
In the IBM Z and IBM LinuxONE Security Portal, we have SMP/E HOLDDATA which can help identify applicability for what products you are running and what Security/Integrity fixes are necessary with well-known and used reporting capabilities. In addition, other information in this Portal can help you to understand the vulnerability CVSS scoring, and z/OS products affected.
We would like to specifically understand what is the difficulty in using what is provided today with z/OS, vs. what a change to use CPE might provide which is necessary for your business and is not available today.
Very important and highly appreciated!
Mainframe customers are required to deliver zSystem vulnerabilities into standard vulnerability management systems of their company in order to track patching processes and make sure vulnerabilites are mitigated in line with security policy requirements. Without a correct and automatically processable matching of
vulnerability to product/version (IBM responsibility)
2. product/version to customers organizational unit for patching (customers responsibility)
dealing with something like log4j is a true nightmare.