IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/VM
Created by Guest
Created on Jun 28, 2023

RELATED IDEAS

DIRMAINT EXTENT CONTROL statements need to check with RACFVM for authorization with SECLABEL Mandatory Access Control

 We require DIRMAINT to respect RACF SECLABELS for DASD devices when working with MDISKs. Our directory and storage management is provided through DIRMAINT. DIRMAINT's EXTENT CONTROL is the single source of storage definitions. We need to have DIRMAINT confer with RACFVM before permission is granted to do storage administrator command on a volume, region or group. As  a RACF SECLABEL everywhere environment it is necessary to have the EXTENT CONTROL :REGION. and :GROUP. check before allowing. This will help us control the system administrator's work automatically. 

It will be useful in multi-cluster DIRMAINT and RACF z/VM data centres as both a security adjacent and a step saving command environment. It is also a security deficiency  loophole if a system administrator works on DASD that are not appropriate. The RACF check will benefit user, administrators and auditors.

Awareness level:

1. DIRMAINT is already a RACF SPECIAL user

2.It issues RACF commands to define and eliminate resources already.

3.There are exits in place for this now. However we have been running locally authored tools instead of IBM supplied tools. We have a mandate to reduce near to elimination locally authored code. An IBM solution is requested.

4.RACF provides the RACROUTE macro so CMS code can avail itself of RACF checking.

I have attached  a simple virtual machine topography of what it looks like among the virtual machines. It does not include DIRMAINT satellite machines.

Thanks!

 

flow_of_EXTENT_...
flow_of_EXTENT_CONTROL_request.pptx
Open full size
flow_of_EXTENT_CONTROL_request.pptx
Idea priority High
  • Admin
    Kerry Wilson
    Reply
    |     Aug 23, 2023

    This item is not under consideration at this time, and it may be possible use the customizable user exit to achieve what you're looking for. Please see the comment from the development team below and thanks for your submission:


    It should be noted that we currently provide for user customization in DirMaint through the use of user exits which are called directly from DirMaint. Specifically, the following user exit, DVHXDA, could be customized to issue any RACF checks necessary to make sure the user is authorized to obtain mdisk space from a particular volume, region, group, etc.

    DASD Authorization Checking (DVHXDA)

    The DASD authorization checking exit routine determines whether the originator is authorized to allocate space for the target user ID on the requested DASD volume. This supports distributed (departmental) administration and centralized (networking) administration. This exit will be called for all AMDISK, CMDISK, RMDISK, and ADD commands, because ADD generates AMDISK requests indirectly.

    This information is documented in the DirMaint Tailoring and Administration Guide beginning on page 152. In this instance we do not provide a sample framework for the user exit, but the DVHXUN user exit could be used as a guide.

    In addition, we also provide the AUTHDASD DATADVH file described on page 83 in the DirMaint Tailoring and Administration Guide. The AUTHDASD DATADVH file allows authorization for allocation requests by specific users based on either Volume, Region, or Group.

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.