Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. 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 Planned for future release
Created by Guest
Created on Jul 28, 2025

Help required for closing discovered vulnerabilities for SSS3500 storage - Group 3 -Configure System Accounting & Uncommon Network Protocols

Our TEL team is working with Customer State Bank of India to operationalise one new SSS 3500 that we sold to customer to replace the existing Gen2 GLS2 SSS Storage.

As part of the internal security practices the State Bank of India runs their own scans on all their devices is asking the TEL team to help close the discovered vulnerabilities . For few of the changes sought the DEV team has requested the Tel team to help raise RFE for these so this configs can be tested in dev setup and post which the dev team can confirm if same can be implemented in customers SSS3500 storage.

There are multiple vulnerabilities noted , as per discussion with TEL & Dev team raising at high level 5 RFE where the related vulnerabilities are bunched


Control Objective - 2.15.1. Uncommon Network Protocols to be disabled

Control Statement - The Linux kernel modules support several network protocols that are not commonly used. If these protocols are not needed, it is recommended that they be disabled in the kernel.

Risk/Impact - If the protocol is not required, it is recommended that the drivers not be installed to reduce the potential attack surface.

Recommendations/ Implementation Steps -

Edit or create a file in the /etc/modprobe.d/ directory ending in .conf and add the following line: 
install dccp /bin/true
install sctp /bin/true
install rds /bin/true
install tipc /bin/true

Dev teams Comment - Please open an RFE so that we can investigate the ramifications of changing this.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Control Objective - 2.17.1. Ensure auditd is installed

Control Statement  - System auditing, through auditd, allows system administrators to monitor their systems such that they can detect unauthorized access or modification of data. By default, auditd will audit SELinux AVC denials, system logins, account modifications, and authentication events. Events will be logged to /var/log/audit/audit.log.

Risk/Impact - It is important that an appropriate size is determined for log files so that they do not impact the system and audit data is not lost.

Recommendations/ Implementation Steps -

Run the following command to Install auditd                         
# dnf install audit audit-libs                                                                
Run the following command to enable auditd: # systemctl --now enable auditd

Dev teams Comment - Please open an RFE so that we can investigate the ramifications of changing this.  


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Control Objective  - 2.17.2. Ensure events that modify the system's Mandatory Access Controls are collected

Control Statement - Monitor SELinux mandatory access controls. The parameters below monitor any write access (potential additional, deletion or modification of files in the directory) or attribute changes to /etc/apparmor and /etc/apparmor.d directories.

Risk/Impact  - Changes to files in these directories could indicate that an unauthorized user is attempting to modify access controls and change security contexts, leading to a compromise of the system.

Recommendations/ Implementation Steps -  

Edit or create a file in the /etc/audit/rules.d/ directory ending in .rules and add the following lines: 
-w /etc/selinux/ -p wa -k MAC-policy 
-w /usr/share/selinux/ -p wa -k MAC-policy

Dev teams Comment - SELinux is available today.  It is not the default.  Please open an RFE so that we can investigate the ramifications of changing this.  


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Control Objective  -2.17.1. Ensure auditd is installed

Control Statement - System auditing, through auditd, allows system administrators to monitor their systems such that they can detect unauthorized access or modification of data. By default, auditd will audit SELinux AVC denials, system logins, account modifications, and authentication events. Events will be logged to /var/log/audit/audit.log.

Risk/Impact - It is important that an appropriate size is determined for log files so that they do not impact the system and audit data is not lost.


Recommendations/ Implementation Steps -

Run the following command to Install auditd                         
# dnf install audit audit-libs                                                                
Run the following command to enable auditd: # systemctl --now enable auditd

Dev teams Comment - Please open an RFE so that we can investigate the ramifications of changing this.  


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Control Objective  - 2.17.2. Ensure events that modify the system's Mandatory Access Controls are collected

Control Statement - Monitor SELinux mandatory access controls. The parameters below monitor any write access (potential additional, deletion or modification of files in the directory) or attribute changes to /etc/apparmor and /etc/apparmor.d directories.

Risk/Impact  - Changes to files in these directories could indicate that an unauthorized user is attempting to modify access controls and change security contexts, leading to a compromise of the system

Recommendations/ Implementation Steps -

Edit or create a file in the /etc/audit/rules.d/ directory ending in .rules and add the following lines: 
-w /etc/selinux/ -p wa -k MAC-policy 
-w /usr/share/selinux/ -p wa -k MAC-policy

Dev teams Comment - SELinux is available today.  It is not the default.  Please open an RFE so that we can investigate the ramifications of changing this. 
 

 

Idea priority Urgent