 |
|
Six common System i security lapses
Search400.com | 15 Apr 2008
TIP - Using the most secure processor available doesn't ensure a secure system. A recent survey identified six common System i security lapses, including a failure to change default passwords and a lack of audit journaling. |
|
System i security report roundup
Search400.com | 14 Jul 2008
TIP - The AS/400 System Security Attributes report is useful to review all of the system values and network attributes to make sure that they are still set to the value that you expect based on your security policy. Then, for... |
|
Tracking System i program object changes
Search400.com | 20 Oct 2008
TIP - It is inevitable that your shop will be audited by someone looking specifically at computer security arrangements. One control that all auditors hone in on, is proof that your System i program base is not tampered with.... |
|
Recovering your AS/400 security configuration
Search400.com | 12 Sep 2008
TIP - You need to have your AS/400 security plan built into your disaster recovery process. Step 1: Know the security objects and settings, and how and where they are saved. These objects include private authorities, system... |
|
System i security: Watch for hackers using FTP
Search400.com | 24 Jul 2007
TIP - While FTP over the System i can be an easy way to communicate between like or disparate systems, security can be compromised without appropriate measures. Here are a some FTP over System i security considerations. |
|
System i security: How much is enough?
Search400.com | 10 Dec 2007
TIP - A System i security strategy requires all the tools in your arsenal, including object security, exit-point security and a comprehensive identity access rights plan,
says Rich Loeber. |
|
Too much System i security?
Search400.com | 07 Jan 2008
TIP - System i security is always a compromise between operating efficiency and data integrity. This tip discusses how to find that balance. |
|
|
|
|
