RE: program authority audit.

Hello,

We have implemented object security here. We did go the way of specifying USRPRF(*OWNER) for all programs.
PRO:
- We don’t care about USEADPAUT. One less thing to check
- All programs are treated the same (we don’t ask ourselves if a program need USRPRF(*OWNER) or otherwise)
- If a program can be called by different programs, we don’t have to make sure than that in each case, there is a program up the stack with USRPRF(*OWNER) present
CON:
- We cannot have a program that present a command line

We have written utility program to check and fix program so it is easy to have them all setup correctly.

We do use a single profile that owns both program and files.

I hope this can contribute to the reflection.

Denis Robitaille
Chef de service TI – Solution Entreprise
Infrastructure et Opérations
Cascades Centre des technologies,
412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
T : 819 363 6130



-----Message d'origine-----
De : MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx
Envoyé : 20 janvier 2016 15:14
À : Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Objet : Re: program authority audit.

What's the advantage to that versus the chain and USEADPAUT(*YES)?
If I have to change the owner I then have to change 10,000 programs versus one.
Look at it this way,
I have one copy of BPCSMENU in library DIVISION1. It is owned by DIV1USER I have one copy of BPCSMENU in library DIVISION2. It is owned by DIV2USER All the rest of the 10,000 bpcs programs are identical.

Now see how the USEADPAUT chain beats out?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/20/2016 03:08 PM
Subject: Re: program authority audit.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



​You can have all the programs owned by the same profile.

Charles​

On Wed, Jan 20, 2016 at 2:48 PM, <rob@xxxxxxxxx> wrote:

They all need the same authority.
Brings nothing to the party.
Big whoopie if one is only an inquiry while one is an actual update. I
cannot change SSA from *ALL to *USE for this file. I am not going to
create 10,000 user profiles to match each program.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/20/2016 02:11 PM
Subject: Re: program authority audit.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

IMHO, the better solution is
OWNER(*USRPRF) USEADPAUT(*NO)

on every program.

Thus, each program adopts the authority needed. Rather than depending

on

authority to be passed down.

Regardless, you have to be careful if one of your infor program

provides

access to a command line. That particular program you'd want

OWNER(*USER)

USEADPAUT(*NO).

Charles



On Wed, Jan 20, 2016 at 1:59 PM, <rob@xxxxxxxxx> wrote:

Evaluating "program only access". This will allow only programs to

modify

data. The users may, or may not, continue to have "*USE" access to

the

data to facilitate queries.

In my understanding all this takes is some program near the top of the
chain to have USRPRF(*OWNER) and for all other programs in the chain

to

have USEADPAUT(*YES).
For example, in an Infor shop you might have BPCSMENU owned by SSA and

set

to USRPRF(*OWNER). Infor does a fine job of using USEADPAUT(*YES) on

all

of their remaining programs.

So some user may have *USE to BPCSMENU. They could call that and then

run

Infor (providing their Infor security is set up right) to their hearts
content. However, even if they did have have access to a command

line,

"Run SQL Scripts", etc they would not be able to use sql or anything

to

modify the data. If the data is *PUBLIC *EXCLUDE or some such thing.

I realize that this has no bearing on stream file data and that has to

be

handled with profile handles.

Now, I'd like to ensure that there are no programs that were modified

to

have USEADPAUT(*NO).
Doesn't seem to be a DSPPGM MYLIB/*ALL capability to an outfile.

There's no such SQL service, is there?

There's no IBM supplied security audit, is there?

Am I down to a list api, and a program API or two, to perform this

audit?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.