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.
Make the version info in the banner of the CLI commands (direct, ndmcli, ...) & GUIs consult a file in the install tree
We have received several security findings because CD gives version details that will allow hackers info on how to hack the software.
|
What is your industry?
|
Banking
|
|
How will this idea be used?
We would edit the version file with "IBM(R) Sterling Connect:Direct(R) for UNIX "
|
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Guest
Thank you very much for including that additional information. We've discussed this further internally, but don't believe that we'll be able to focus resources on this change in the short to medium term.
While I understand your explanation we feel that anyone who is granted access to one of these systems should also have basic information available about the system that they are logging into. There are also other ways that a user could view the version information as well which could not be blocked in a reasonable fashion. Those points as well as a lack of broader market interest make it unlikely that we'd be able to focus on this within a reasonable amount of time so this will be declined.
I do want to thank you very much for using the enhancement request tool and would encourage you to utilize it again if you uncover other ideas that we should consider.
Thanks,
Chris Sanders
Connect:Direct Offering Manager
Attachments Open full size
Chris,
Multiple security frame works(PCI-DSS, OWASP, etc.) discuss altering software banners to not provide version data to a potential hacker. By placing the banner in a file external to the executable, then administrator of a Connect:Direct install can customize the banner to show legal messages, remove version info, display help phone numbers, etc.
Indeed as you mention this should only be accessible to users that have access, however, many of the most damaging penetrations of enterprise systems arise from internal actors or valid accounts that have been compromised. Please consider this enhancement as a way to allow your customers to meet this requirement. By comparison understand that sFTP provides this capability.
Thanks
Attachments Open full size
Thank you for opening this enhancement request with IBM. I have reviewed it thoroughly with my team and we aren't quite sure we understand the security implications that you've mentioned.
The C:D CLI should only be accessible by users that have permissions to interact with C:D. We would expect that these users should know the version/maintenance that is being used as they would have access to perform other tasks such as submitting processes, checking the status of transfers, potentially making configuration changes, etc. If we have overlooked a specific reason that you believe this causes security concerns I'd be happy to review further however.
Sincerely,
Chris Sanders
Connect:Direct Offering Manager
Attachments Open full size