Exit Point Monitoring

Problem: The IBM System i allows users to access many system functions through industry-standard protocols, such as ODBC, FTP, SQL, and so on. With these ports open, the system is more vulnerable to intrusion.

Solution: Robot/SECURITY provides exit-point monitoring of IBM servers by object, user, and/or schedule, and maintains a historical database of exit point usage.

Security Monitoring

Problem: Security-related events on the System i can occur unnoticed. For example, security-related events might include:

• Suspicious events, including password violations, unusual attempts at access, and other events that appear to be "hacker"-related

• Authority changes, such as object-level authority changes

• Objects that have been added, duplicated, or copied

Solution: Robot/SECURITY allows the administrator to focus on events occurring against specific libraries and objects. It provides a robust, fully automated event escalation mechanism that can send a Robot/ALERT message, a Robot/NETWORK status, or a message to a message queue that is monitored by Robot/CONSOLE.

Reporting, Analysis, and Forensic Diagnostics

Problem: Because the System i can be accessed by a number of methods, security breaches can take many forms. Information about each security-related event might be stored in several different locations on the system.

Solution: Robot/SECURITY looks at QHST, QAUDJRN, QSYSOPR, and more, and allows the administrator to analyze them for security violations using a PC-based forensics analysis utility. The administrator can perform a detailed analysis of a particular job or user. A "Good-Morning" report provides a complete change log of modifications to the product.

System Security Audit

Problem: System i security configuration is complicated from initial setup to ongoing maintenance.

Solution: Robot/SECURITY provides a comprehensive audit of your system security configuration. The audit produces a report that compares the current system security settings to Help/Systems? suggested best practices, which are based on research derived from discussions with industry sources. The audit report serves as documentation to be used by an auditor. Products like this validate that companies are able to pass a SOX or CobIT audit. Additionally, the audit report alerts the administrator to security matters that need to be addressed on the system, allowing the administrator to focus on the exceptions.

Robot/SECURITY requires V5R3 or higher.

To register for an introductory Webcast today (Thursday, August 30) on Robot/SECURITY visit Introducing Robot/SECURITY.