This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
IBM does not intend to provide an additional solution to this request at this time, so it is being closed. The security appliance functionality in the previous update provides a strategic single location to implement an IP address block list.
IBM i has built in "Security Appliance" capabilities.
IP Packet Filtering https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzajb/rzajbrzajb0ippacketsecuritysd.htm can solve this at the system level. Preventing addresses at the IP layer universally solves the issue for all servers, not just those with an exit point available that includes the remote IP address.
Another option applicable for most applications is the QIBM_QSO_ACCEPT socket user exit. https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzab6/socketuserexit.htm
This processing happens at a higher layer however it could make use of the existing blacklist file.
It is unlikely all server exit points can be updated to include the IP address in the next release. The referenced options are both available today in multiple releases and solve the issue at a system wide level. Will one of these options work to solve the requirement?
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Security
Operating system - IBM i
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Core OS
Operating system - IBM i
Source - Client
The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. Protecting the community from malicious attacks via denial of service should indeed be implemented.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/
Nancy Uthke-Schmucki - CAAC Program Manager
QIBM_QNPS_ENTRY
QIBM_QNPS_SPLF
QIBM_QPWFS_FILE_SERV
QIBM_QSQ_CLI_CONNECT
..etc...
... Basically any of the server exits that handle connections to an LPAR, the goal here is to stop the connection if the IP address has been determined to be an attack. I have had cases where someone did a port scan and then a vulnerability attack to try and connect to any of the servers listening on ports. Some of those that had IP address in the API parms I was able to drop and prove we were protected, others I had to just accept and move on and hope the user profile would do it.
Please be more specific as to which server exit points you would like to see the IP address of the requester added to so that I may route this request to the correct owner.
Maybe provide an example where it is not ?
Maybe the API QDCRDEVD format 0600 is an option ?