iSeries security planning

Email Alerts

Register now to receive Search400.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • User being locked out by Windows share on iSeries

    Use the the iSeries QSYSOPR message to look for any errors in passwords when running a program on the iSeries that transfers data to a spreadsheet on a Windows share.

  • Controlling remote access on your IBM i

    To control remote access via network connections on the AS/400, the most secure solution is implementation of the exit point controls in the operating system. The server controls serve as gatekeepers to your iSeries, checking IP addresses of remote computers against a preset list of authorized users.

  • Checking in on your IBM i authorization lists

    Have you ever created an object on the AS/400 without making sure the necessary authorization list is attached? By using some common commands, you can secure your IBM i, and audit objects and fix mistakes. The necessary commands include DSPAUTLOBJ AUTL, DSPOBJD OBJ, and OUTPUT(*OUTFILE).

  • Expanded password rules available in System i/OS 6.1

    System i/OS 6.1 provides new password security tools that can tighten up security in your AS/400 shop. Rich Loeber shares his favorite new password security tools and describes their implementation.

  • How to tell if you're using the right security level

    When your company's CIO suggests that you should upgrade the security level of your AS/400 to 50, you might not think this is necessary, but where do you turn for supporting evidence?

  • Search400.com Products of the Year 2008

    Search400.com invites you to participate in its annual Products of the Year award nomination process. Nominate your favorite product or your company's product. Winning products will be featured in January 2009 on Search400.com.

  • Detecting system changes made by outside IP address

    If you suspect that changes are being made by an external source, you can use an exit point program to monitor the activity and trace the IP address.

  • System values on i: Setting them up and locking i down

    AS/400 system values define global, system-wide settings on your platform. Many of these pertain to system security implementation. Take a look at these settings and learn how to lock them down. Many system values are security-related and the operating system designers provided an easy way to review and work with the security settings: The WRKSYSVAL command.

  • A guide to System i security, Part 3: Digging in to the System i security environment

    The AS/400 provides many built-in tools to manage the security environment. Find out how to tighten up your System i, and ensure your system is protected from unwanted intrusion. A very important aspect is password settings, which can be the Achilles-heel of IT security.

  • Encrypting files or fields on the iSeries

    Encrypting files on iSeries is no trivial undertaking. Using vendor technologies such as those from Linoma Software and nuBridges may be easier than cobbling it all together with IBM tools.

  • VIEW MORE ON : Security Tools
  • Time for a security checkup for your i

    Conducting an annual system security checkup on your AS/400 will prevent you from discovering some unwanted New Year's surprises. Rich Loeber recommends steps including checking security settings, ensuring that your user profiles are up to date with employee rolls, and generating a query report of new files created since your last audit and checking their compliance with your security policies.

  • Recovering your AS/400 security configuration

    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 values, and user profiles.

  • A guide to System i security, part 2: Landing and establishing access

    Once you've developed a security policy for your System i environment, you need to define who will access it and how they will get to their data. The locks on the door include passwords, object security and group settings. Once those are set, it is important who gets which keys. Website settings, firewalls and soft settings are also important in your AS/400 security setup.

  • A guide to System i security: Descending into the heart of darkness of IT security

    Developing your company's System i security policy starts with taking a look at what needs to be accomplished. Communication and appropriate access for personnel to data centers are keys to a robust policy.

  • Learning guide: Steps to a secure System i

    This organized list will guide you along your way to maintaining a secure iSeries system. Undoubtedly, the iSeries is one of the most secure platforms out there, but don't be mistaken in thinking that it is untouchable. Address the basic security issues now and take the proactive steps needed to prevent having your system compromised.

  • Securing printed output

    In today's security conscious environment, most System i shops have already locked down their systems. Object level security is locked down and users are classified as to what they can and cannot do when they are logged onto the system. But, securing files is only part of the problem. If a user can't look at a file, but they can look at processed output sitting in a print spool file, then your hard work of locking up the files is for naught.

  • Are all of your System i (iSeries) doors closed? -- part 1

    Security expert Rich Loeber discusses the security risks of leaving doors open on the System i. In the "old" days, the only door you had to be concerned about was the computer terminal. That certainly is not the case today. Are all of your System i doors locked? Are you aware of all the different entry points into your system? If not, it's time to learn.

  • Can you trust all those trigger programs?

    Be wary of trigger programs on your system. Here is an easy way to check up on them.

  • Learning guide: Simple steps to a secure iSeries

    This organized list will guide you along your way to maintaining a secure iSeries system. Undoubtedly, the iSeries is one of the most secure platforms out there, but don't be mistaken in thinking that it is untouchable. Address the basic security issues now and take the proactive steps needed to prevent having your system compromised.

  • Creating your iSeries security policy

    In the past, the main security policy decision was whether or not to have locks on the doors to the computer room. That was it. In today's inter-networked world, security has become of paramount importance and your security policy is correspondingly more complex.

  • VIEW MORE ON : iSeries physical security