Skip to Main Content
IBM Sterling


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Status Future consideration
Categories Reporting
Created by Guest
Created on Jan 19, 2018

Add built-in report for bruteforce attempts.

The Sterling Proxy is our gateway between

the internet and SFG.  As such, we are

exposed to attempts to guess user IDs

using brutefore methods. 

 

The raw internal logs show each event and

contain the IP address, Time, username and

number of failed authentication attempts. 
I believe it would be useful to create a

built-in Sterling report that can provide

information according to a selectable

timeframe, which contains, IP address,

number of attempts, userIDs used in

attack.  Selectable time frame would be

monthly for automated creation and user

selectable for one off report creation.

What is your industry? Government
How will this idea be used?

Security personnel monitor attempt

activity and may involve other units to

block specific IPs. 

This enhancement could also be used, if

implemented,  in conjunction with RFE: 

"Ability to reject user access at proxy

before authentication check" ID:113153 to

identify userIDs to be blocked.

  • Admin
    Kiran Krishnan
    Reply
    |
    Nov 6, 2023

    Hi,

    Thank you for your patience and sharing your valuable inputs. We currently have some high priority items on our roadmap that we need to address first and have planned this feature to be available by late 2024. We have considered monitoring and reporting capabilities of security related events as one of the high-priority theme for SSP and will keep you updated about the progress of it. In the meantime, if you have any other suggestions or questions please feel free to drop a comment or open more Enhancement Requests.

    Thank you,

    Product Management - Sterling Data Exchange



  • Guest
    Reply
    |
    Apr 12, 2018

    Hi,

    Thanks for opening this Enhancement Request with us. We have looked into it and at this point we are figuring out the best way to get this done. We will likely do it in Control Center as this is a monitoring task and we are parallely planning work on improving monitoring of Secure Proxy using Control Center. Having said that, we will update you once we have more details.

    Feel free to use the system to open more Enhancement Requests with us as you see fit.

    Thanks & Regards,

    Ripudaman Singh Kushwah

    Offering Manager, SSP & SEAS

  • Guest
    Reply
    |
    Feb 3, 2018

    Using the word: "units"  I take that to mean other departments within an organization.  (Network admin, F5, Firewall support, etc. )   These groups are sometimes hard convinced to blocking specific IP's. (constant requests to block more and more.)

    It would be helpful to at least make it simpler for application admins to gather who is actually trying repeatedly to gain access to app software.

    Having this data accessible can also be used to set up an internal, host-basedOS, firewall blocks.  (iptables for UNIX)