This portal is to open public enhancement requests for IBM Sterling products and services. 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).
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Add captcha in the IBM Sterling Store Engagement Application Login Screen for additional security
During the security testing, it was found that the login mechanism used by the Store application did not prevent automated attacks. This fact could be demonstrated by attempting to brute-force the login credentials of a testing account, where after 100 failed attempts, authentication would still be allowed by submitting valid credentials.
This scenario allows the possibility of an attacker attempting to guess the credentials of a victim user’s account.
Our Info Security team recommended -> A general solution for this problem is to implement a CAPTCHA to prevent automated attacks.
What is your industry?
How will this idea be used?
If captcha is implemented, it can prevent bots from performing brute/reverse brute force attacks if the attacker gets a hold of username or password. With the current implementation of using just username/password to access the Store application, it poses a security risk. In the times, when almost most of the enterprise applications use captcha or employ MFA to prevent such risks, it's necessary to be in line with the security threats that could be prevented in the near future.
Do not place IBM confidential, company confidential, or personal information into any field.