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.
Secure Connection between Secure Proxy Engine (in DMZ) and SSP Perimeter Server (in Secure Network)
There is a requirement from customer to have Secure Connection between Secure Proxy Engine (in DMZ) and SSP Perimeter Server (in Secure Network).
Add TLS 1.3 Support to Sterling Secure Proxy
Add SSL Support between Sterling Secure Proxy Configuration Manager / Engine and WebSphere MQ
Security mandates that all the connections need to be secured. WebSphere MQ supports SSL but not SSP CM / SSP Engine, adding this functionality allows meeting the newer security requirements.
Hooks to enable the SSO Authentication for SSPDashboard URL
SSP - Disable TLS1.0
SSLv3 is disabled by default in SSP in the java.security file with the following line of code. We have attempted to add TLS1 to disable TLS1.0 only and we were not successful. Adding TSL1 to the list of algorithms disabled all versions of TLS not ...
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...
OCSP implementation for CD/SEAS
CD/SEAS do not provide any means to check the status of the certifcate in real time. They current rely on cache update on regular basis. Addition of OSCP in SEAS will provide a realtime check of revocation
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.
SSP Custom User Roles
Right now SSP currently allows for two user roles (Admin, Operator)within the application. We would like to be able to create custom roles based on specific user requirements so exact permissions can be assigned.
GCM mode for SFTP
We are seeing increased reluctance from partner organisations to trust CBC mode, due to OpenSSH's withdrawal of support for this mode by default. This leaves Secure Proxy with only CTR mode encryption as a widely accepted option. To ensure that we...