Difference between revisions of "Security Basics"

From MidrangeWiki
Jump to: navigation, search
m (Sky View)
 
(20 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
[[Category:Security]]
 
[[Category:Security]]
See [[General Computer Security]] for info and links about Security outside of the 400.
+
See [[General Computer Security]] for info and links about Security outside of the IBM i community.
 +
== Security Tools ==
 +
* GO SECTOOLS
 +
* GO SECBATCH
 +
== Security Wizard ==
 +
* Access via [[Operations Navigator]]
 +
** Warning ... while this is for administrators new to IBM i or Security, before changing any security settings, it is advisable to consult with the most experienced IBM i security professional on-site.
 +
** You can change security settings, but while they are changed, they affect how objects function, including how they function after you change settings back again.
 +
== Security [[Commands]] ==
 +
* Most functions of Security Commands, can also be done with [[Operations Navigator]]
 +
=== User Profile ===
 +
* GO CMDPRF
 +
* GO CMDUSR
 +
* [[CHGPRF]]
 +
* [[CHGUSRPRF]]
 +
* [[CRTUSRPRF]]
 +
* [[DSPUSRPRF]]
 +
* [[DSPAUTUSR]]
 +
* [[WRKUSRPRF]]
  
== Security 400 Professionals ==
+
=== Password ===
 +
* GO CMDPWD
 +
* [[CHGPWD]] change password
 +
* [[CHKPWD]] makes user re-enter password that was used to sign onto the system
  
=== Wayne Evans ===
+
=== Object Authority ===
 +
* GO CMDAUT
 +
* [[GRTOBJAUT]]
 +
* [[RVKOBJAUT]]
 +
* [[GRTUSRAUT]]
 +
* [[EDTOBJAUT]]
  
* Wayne O. Evans http://www.woevans.com/ is a former IBM 400 Security Architecture specialist http://woevans.freeyellow.com/WOEBIO.html who now has his own 400 Security Consulting firm
+
=== Objects Owned ===
** He designed many of the security features of the 400 and its predecssor machines, also many 400 features in addition to security
+
* GO CMDOWN
** He advises us to get a more secure web browser than Microsoft IE
+
* [[CHGOBJOWN]]
** He does 400 Security columns and seminars
+
* [[WRKOBJOWN]]
*** He has a book out with a collection of his 400 Security articles
 
** OS/400 Security Education and Training
 
*** Security/400 FAQ
 
http://woevans.freeyellow.com/Qst_Ans.pdf
 
**** Biggest threats to overall 400 security
 
**** Best Practices
 
**** What can be done at the Sign On Screen
 
**** How secure are 400 passwords
 
**** Why security level 40
 
**** Security 400 auditing
 
**** [[Client Access]]
 
**** [[Operations Navigator]]
 
**** Exit Programs
 
**** Authorization Lists
 
**** ODBC
 
**** [[Encryption 400]]
 
**** How evaluate security software vendors
 
**** VPN interesting factoid
 
***** The use of VPN (Virtual Private Network) causes all traffic over the VPN to be encrypted.
 
***** [[User:Al Mac|Al Mac]] notes that this may not help if Spyware gets onto the PC of the person using VPN to access the 400
 
**** and lots more
 
  
*** Other downloads available http://www.woevans.com/My_Homepage_Files/Page3.html such as
+
=== Authorization List ===
**** step by step instructions to improve your 400 Security
+
* GO CMDAUTL
**** sample Security Policy
+
* [[ADDAUTLE]]
**** Security related software
+
* [[CRTAUTL]]
**** History of 400 and predecessor machines
+
* [[DLTAUTL]]
** OS/400 Security Review Audit
+
* [[DSPAUTL]]
** OS/400 Security Training
+
* [[DSPAUTLOBJ]]
*** NetQ PentaSafe Training
+
* [[EDTAUTL]]
** His links to Security 400 user groups, discussion forums, and related info http://www.woevans.com/My_Homepage_Files/Page1.html
+
* [[RMVAUTLE]]
*** 400 user groups in gneral http://www.woevans.com/usergroups.html
+
* [[WRKAUTL]]
  
=== Milt Habek ===
+
=== Adopted Authority ===
 +
* [[DSPPGMADP]] Display Program Adopt
 +
** Specify a user profile and get a list of the programs that adopt that user's authority.
 +
* [[PRTADJOBJ]] Print Adopting Objects
 +
** Specify a user profile, *ALL or generic user(QP*) and get a printout of objects that adopt user's authority.
  
Milt is CEO of UPI which markets many security solutions for the 400
 
  
=== Sky View ===
+
=== Spooled files ===
 +
The scenario: want to stop programmers from using a production OUTQ.
  
http://www.skyviewpartners.com/java-skyviewp/index.jsp
+
If the developers have either *JOBCTL or *SPLCTL, and the OPRCTL(*YES)
 +
parameter is specified on the OUTQ, the developers will be able to use
 +
and work with the OUTQ.  One way to correct this is to turn the OPRCTL
 +
parameter on the OUTQ to *NO.
 +
 
 +
Assuming programmers have *JOBCTL, here is what I would do....
 +
 
 +
# Make the OUTQ *OPRCTL(*NO)
 +
# Create a Group Profile for all developers
 +
# Add the Group Profile to the OUTQ with an authority of *EXCLUDE
 +
# Give the authorized user Group(s) *CHANGE (authorized users could be *PUBLIC now that the programmers are excluded.)
 +
# If there are any *JOBCTL or *SPLCTL users (SysOpers?) who you want to be able to manage the OUTQ, give them *CHANGE authority as well.
 +
 
 +
Thanks to John Earl via Midrange-L 21 Apr 2010
 +
== Security System Values ==
 +
WRKSYSVAL SYSVAL(*SEC)
 +
Working with system values dealing with security should be done carefully.  One should read the latest information at the IBM Knowledge Center at [http://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzarl/rzarlsysval.htm Security system values]
 +
=== QPWDMAXLEN ===
 +
In addition to the information available at [http://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzarl/rzarlmaxpwd.htm Maximum Length of Passwords (QPWDMAXLEN)] one should be aware of these considerations when going above 8 characters:
 +
* [http://www-01.ibm.com/support/docview.wss?uid=nas8N1012710 Configuring the IBM i SSH, SFTP, and SCP Clients to Use Public-Key Authentication]
 +
* There were some things dealing with "File Transfer Subroutine" (QY2FTML) but try to find documentation on that.
 +
* If you find any other concerns, then by all means, please update this page.

Latest revision as of 18:52, 24 August 2016

See General Computer Security for info and links about Security outside of the IBM i community.

Security Tools

  • GO SECTOOLS
  • GO SECBATCH

Security Wizard

  • Access via Operations Navigator
    • Warning ... while this is for administrators new to IBM i or Security, before changing any security settings, it is advisable to consult with the most experienced IBM i security professional on-site.
    • You can change security settings, but while they are changed, they affect how objects function, including how they function after you change settings back again.

Security Commands

User Profile

Password

  • GO CMDPWD
  • CHGPWD change password
  • CHKPWD makes user re-enter password that was used to sign onto the system

Object Authority

Objects Owned

Authorization List

Adopted Authority

  • DSPPGMADP Display Program Adopt
    • Specify a user profile and get a list of the programs that adopt that user's authority.
  • PRTADJOBJ Print Adopting Objects
    • Specify a user profile, *ALL or generic user(QP*) and get a printout of objects that adopt user's authority.


Spooled files

The scenario: want to stop programmers from using a production OUTQ.

If the developers have either *JOBCTL or *SPLCTL, and the OPRCTL(*YES) parameter is specified on the OUTQ, the developers will be able to use and work with the OUTQ. One way to correct this is to turn the OPRCTL parameter on the OUTQ to *NO.

Assuming programmers have *JOBCTL, here is what I would do....

  1. Make the OUTQ *OPRCTL(*NO)
  2. Create a Group Profile for all developers
  3. Add the Group Profile to the OUTQ with an authority of *EXCLUDE
  4. Give the authorized user Group(s) *CHANGE (authorized users could be *PUBLIC now that the programmers are excluded.)
  5. If there are any *JOBCTL or *SPLCTL users (SysOpers?) who you want to be able to manage the OUTQ, give them *CHANGE authority as well.

Thanks to John Earl via Midrange-L 21 Apr 2010

Security System Values

WRKSYSVAL SYSVAL(*SEC) Working with system values dealing with security should be done carefully. One should read the latest information at the IBM Knowledge Center at Security system values

QPWDMAXLEN

In addition to the information available at Maximum Length of Passwords (QPWDMAXLEN) one should be aware of these considerations when going above 8 characters: