Re: Disable QSECOFR?

I have always kept QSECOFR disabled but I usually have at least 2 other
usrprfs that can enable it if it gets disabled.

You can still use it to submit jobs if disabled (but why?)

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Thu, May 6, 2021 at 2:05 PM Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:

I thought disabling QSECOFR was a very bad idea, but I came across a Help
Systems documents recommending the practice.

Is this a practical security measure?

Thanks


From:
Protect Your Administrator Accounts from Abuse
March 10, 2017
Use of QSECOFR

QSECOFR is the first profile hackers will try to abuse if they're randomly
trying to gain access to your systems. Limit the use of QSECOFR to only
system upgrades and, yes, the time when an irresponsible vendor requires
you to sign on to install or upgrade their product. The operating system
will prevent you from setting the QSECOFR password to *NONE, so, to further
protect this profile, set QSECOFR to status of *DISABLED. This requires you
to either sign on to the console to use QSECOFR or set it to status
*ENABLED prior to using it.

https://www.helpsystems.com/resources/articles/protect-your-administrator-accounts-abuse
--
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