This is an IBM Automation portal for Integration products. 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.
Thanks for additional information - We recognize that this is a valid requirement for you.
We currently have no plans to do this at this time.
As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon, and it remains on our list of potential future items.
Adicionando información sobre el escenario, el cliente realiza escaneo de vulnerabilidadades mediante detección de puertos abiertos, al identificar un puerto (8443, 8445) realiza peticiones tipo <servidor>:<puerto>, la respuesta al no tener contexto es un error 500, es directamente "resuelta" por el HTTPS Handler, siendo específicos, el services.https sin llegar a ningun Web Service Proxy. en dicha respuesta no se encuentra el encabezado HSTS resultando en el reporte de seguridad.
Hola, many thanks for submitting your idea. I’ve translated your Idea as “The consumption of exposed services, whether WSP or MPG, requires the addition of the HSTS header to close a common vulnerability reported in the different port scans.” In DataPower you can already inject HSTS header(any header) and if you are already enforcing HTTPS there is not much additional benefit of HSTS. Please could you clarify your use case in more detail and how you would expect the feature to work.