Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Sep 16, 2020

Disallow ENDJRNPF by work with system security

add option to Work with System Security to disallow ENDJRNPF for files in User libraries. If set to NO, users with appropriate security settings may ENDJRNPF. If set to YES, no user (even *SECADM) may ENDJRNPF.
(maybe not applicable on *IBM libraries)


Use Case:

journalling data files is a vital function to run a validated environment where application owner must prove data changes. A malicious *secadm user might end journalling, run some changes and start journalling again. This action can be seen in the audit journal, but the data changes are not visible.


Idea priority High
  • Guest
    Reply
    |
    Dec 15, 2020

    concerning "establish a command exit point program for ENDJRNPF" - i then would trigger an RFE on how to avoid a *SECADM user to modify / change the exit point.

  • Guest
    Reply
    |
    Nov 23, 2020

    sorry my last comment was not complete. It might be a good approach but in my opinion we should be able to modify this level of security settings to same approach as stopping users from *sec related system values.

    We maybe can include Tim Mullenbach into that topic?

  • Guest
    Reply
    |
    Nov 23, 2020

    The Exit point solution might be a good approach.

  • Guest
    Reply
    |
    Nov 18, 2020

    IBM does not intend to provide a solution to this request at this time, so it is being closed. As CAAC pointed out, adding new controls won't necessarily stop a malicious user with elevated authority, and could lead to a false sense of security.

    One existing solution is to establish a command exit point program for ENDJRNPF or similar commands to monitor and/or restrict the actions of a highly privileged user.

  • Guest
    Reply
    |
    Nov 2, 2020

    The request to shift the security "problem" from a *SECADM user to a specially enabled DST user may be a regulatory request, as a system may have been configured to have multiple *SECADM but only one specially enabled DST user which has its own password which can be handled by "master-secofr".

  • Guest
    Reply
    |
    Oct 20, 2020

    The CAAC has reviewed this requirement and recommends that IBM not implement this request. The Use Case mentioned "a malicious *secadm user ", but any user can be malicious. Best practice is to grant appropriate level of authorities to all levels of users. Implementing this RFE would shift the security problem to a different arena instead of solving the problem.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager