iSecurity Compliance Manager for IBM i

Security levels per object

Conpliance Management intrusion prevention system for ibm i

The challenge of securing both Native and Integrated File System (IFS) OS/400 objects is the basis for all IBM i security due to the unique object-based architecture.

The architecture of the operating system besides the fact that user-rights for accessing objects are checked for all operations, whether batch, interactive or over-the-web. Since OS/400 requires authorizations to be defined for each object in the system, this activity is cumbersome, error-prone and difficult to maintain.

Helps system administrators to secure IFS and Native object security

iSecurity Compliance Manager helps system administrators to painlessly secure IFS and Native object security. You can easily plan the desired security based on object name and type and to check for inconsistencies between actual and planned object security settings.

  • Reduces non-compliance with company defined security policy settings
  • Assures settings for object security are not changed and can be combined with iSecurity Audit
  • Assures audit and compliance that the data is secure
  • User-friendly green screen and GUI interfaces

iSecurity Compliance Manager comes integrated to our GUI for a User-Friendly Interface.

How Does it Works?

Advantages of using Compliance Manager

iSecurity Compliance Manager provides an easy facility to set system-wide objects rights in accordance with pre-defined templates and includes full reporting features.

  • Site-specific definitions for complex multi-site organizations
  • Set current security status to the planned definitions
  • Full reporting includes support for OUTFILE

iSecurity Compliance Manager Interface

Related Information

Key Features

  • Full control of all related parameters and resources: Owners, Authorization lists, User authorities, Primary Groups, Object auditing and more.
  • Specific user authorities can be added or can replace existing ones.
  • IFS object security plans are based upon object name, type, and attribute.
  • Native object security plans are based upon object type and generic names.
  • Multiple System (LPARs) definitions with exceptions can be entered to same repository
  • Easily Check and Display differences between current security definitions and the planned security definitions

Are you ready? Let’s talk.

Related Products

Action

Real-time security events, via triggers to Email, SMS, Syslog, SNMP, and CL commands.

Capture

Silent 5250 screen capture for end-to-end audit trails with Playback.

Audit

Report generator and scheduler. Monitor QAUDJRN, Reports and Security status.

Change Tracker

Changes to production automatically logged in IFS at object / source levels.