IBM Security Guardium Ideas Portal

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

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 notification 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.

Post an Idea

To post a new idea - click on the "Add a new idea" button and select the appropriate capability area this idea relates to. Do provide requested information to allow us to get a better understanding of your request. If 'Guardium Data Protection' capability is selected, you will be prompted to select the category/product the idea relates to. If you are not sure of the category/product your idea would fall under, then select 'IBM Guardium Other' in the drop down list and proceed from there.

Please note: The purpose of the Ideas Portal is to tap the creativity of the Guardium Data Protection community so that we can enhance the product for everyone! If you need to report a defect or get help, please use our normal support channel. Click here to open a support ticket.

For IBMers, click here to submit an idea on behalf of a customer, if the customer prefers to keep their use case and idea private.

"Guardium port requirements" documentation

The Knowledge Center web page with this title ( lacks some needed information and some information is repeated. It is difficult for the new customer to interpret.

For example:

a) Quick Search:

  • TCP 8983 - SOLR, incoming SSL (Bidirectional?; which devices?)

b) Duplicate/overlapping

    • DB Server - Collector: TCP 8443 - open from DB server to collector (isn't this encrypted?)

    • Enterprise load balancer: TLS 8443 - S-TAP load balancer - This is needed for UNIX/Linux S-TAPs to communicate instances to the collector. However this port is also used for the Central Manager load balancer. The S-TAP initiates a request to Central Manager (load balancer) on 8443 sending HTTPS message, if installation indicates to use Enterprise load balancer. Between the database server and Central Manager, there will be the capability to use a proxy server, if customer doesn't want an open port directly from database to Central Manager. (Is this Unix only? ; if S-TAP => collector, should there be another line for S-TAP => CM or S-TAP => load balancer; confusing)

    • Default Ports Used for Guardium Application Access: 8443 TCP The port is used for: * Web browser access (https) to the Guardium user interface. * Registering a managed unit to a central manager. * Checking connectivity between aggregators or central managers and collectors (has multiple from-tos i.e. browser=> appliance, appliance =>Manager and Manager => MUs])

c) Duplicate/overlapping (devices?)

  • File Activity Monitoring: TCP/TLS 16022/16023: Universal Feed. 16022 (FAM monitoring, unencrypted) and 16023 (FAM monitoring, encrypted) both need to be open bidirectionally

  • Default ports used for other features: 16022/16023 TCP/TLS Universal Feed - File Activity Monitoring (FAM0

  • System - Mainframe: TCP 16022 – connects S-TAP to DB2 z/OS, S-TAP IMS, S-TAP VSAM (S-TAP Data Set) AND TCP 16023 - TLS connections, specifically IBM‘s Application Transparent Transport Layer Security (AT-TLS)

  • Ports for connections to z/OS database servers : 16022 TCP Connects to S-TAP for DB2 z/OS, S-TAP for IMS, S-TAP for Data Sets AND 16023 TCP TLS connections, specifically IBM's Application Transport Layer Security (AT-TLS)

I would suggest a single table of port requirements with columns for:

  • Device From - the one device type that initiates the connection

  • Device To - the one device type being connected to

  • Port - the TCP/IP port on the to-device

  • Protocol - the connection protocol, i.e. TCP or UDP, with or without TLS

  • Bidirectional - whether the to-device will also initiate connection to the from-device

  • O/S - the operating system of the from-device, i.e. Unix/Linux, Windows or either

  • Function - whether this is a base requirement or only needed when this functionality is enabled; description of what the connections are used for.

Example entries:

Device From

Device To






DB Server






S-TAP communication with sniffer

DB Server






when CAS enabled

DB Server






Listener GIM


SMTP server





email using Simple Mail Transfer Protocol (SMTP) for alerts and other notifications

  • Guest
  • Mar 25 2021
  • Future consideration
  • Admin
    3 Sep, 2021 10:18pm

    Hello - thank you for your feedback. We are considering the changes requested around documentation. We will keep you posted on support timelines.


    Product Management Team

    IBM Data Security / Guardium

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.