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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
License FASP at SSP rather than the endpoints. Add FASP support to SSP for additional protocols
FASP licensing could be applied to SSP rather than the underlying endpoints thereby allowing bridging to be performed where a multitude of underlying endpoints route through that SSP instance. Currently each endpoint has to be licensed individuall...
Option for TLSv1.1 or Higher in FTPS Netmap
Request to either add an option for TLSv1.1 or higher under FTPS netmap > Security > Secure Connection > Security Setting for a FTPS adapter, or remove SSLv3 and TLSv1 from the "SSLv3, TLSv1, TLSv1.1, or TLSv1.2" option under the same loc...
Add successful security handshake information to the audit log
Add information to the SSP audit log regarding what was negotiated during a successful security handshake. For SSL/TLS this would include the protocol version(SSLv3.0, TLSv1.0, etc.), the cipher agreed upon and the client source IP. For SFTP/SSH t...
Allow CD netmap in SSP multiple hosts/IP addresses under the same s-node name
Allow multiple hosts/IP addresses per CD node on SSP netmap. Currently in SSP v343 product, CD node and its address are 1:1 mapping. We currently have 4 CD server adapters on backend SBI 2 node cluster. These SBI CDSA all share the same CD node na...
Multiple Configuration Managers supporting proxy/perimeter servers
Currently SSPcm is a single point of failure since only 1 instance can manage a set of proxies. If the one instance goes offline, the proxies being managed a stop functioning correctly
SSP CM : Alternate JMS Connection Info under JMS Queue Management in Advanced - System Settings - CMSystemSettings - Globals
Sterling Secure Proxy Configuration Manager Hello Team, Even though there is option to have multiple JMS Configuration under CMSystemSettings, at a time only one JMS configuration can be set in JMS Queue Management to enable JMS queuing for CM. Th...
Limit Secure Proxy sessions by inbound IP address
We want the ability to limit inbound sessions per IP address at the adapter level. We don't want to maintain inbound IP addresses in SSP but we would like SSP to be intelligent enough to realize when an external inbound IP is consuming X number of...
Sterling Secure Proxy does not currently support the forward proxy
Inactive User Accounts Controls - Administrator Accounts
Application parameter settings that do not automatically disable and/or remove user accounts after a specified period of inactivity may result in unauthorized access, modification, destruction, and/or disclosure of confidential information.
Allow SSP engine certificate to be configured through configureEngineSsl.sh directly
The configureEngineSsl.sh script only supports importing configuration exported from CM. Typically CM and SSP engines are installed on different machines in different network zones. The certificates will be put on the servers directly. It's a lot ...
Do not place IBM confidential, company confidential, or personal information into any field.