Re: Object authority

Not to rehash, but I saw an article that seemed like it might apply.

The last paragraph:
True mandatory access controls are the only real exclusionary access method available and should be implemented as much as possible to provide least privilege necessary for a particular user or users access requirements (Implementing resource security – IBM Documentation <https://www.ibm.com/docs/en/i/7.4?topic=strategy-implementing-resource-security>).


Original article:
https://www.itjungle.com/2022/06/27/guru-the-finer-points-of-exit-points/ <https://www.itjungle.com/2022/06/27/guru-the-finer-points-of-exit-points/>

—
Bryan

On Jun 9, 2022, at 1:42 PM, smith5646midrange@xxxxxxxxx wrote:

We are having problems with developers "installing" new objects outside of
the change management software and also renaming existing objects and
creating new versions of them.



We are an IP based company so we rely heavily on adding and removing PF and
LF members.



Is there a level of security that I am overlooking that will allow us to
lock down a library to prevent the creation of new objects and the renaming
of existing objects yet still allow the ADDPFM/ADDLFM and RMVM commands?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com