Definition of Target Security Levels per Object & Type
iSecurity Compliance Management gives administrators the ability to plan and define security levels per object based on name and type.
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 of the operating system and 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 per each object in the system, this activity is cumbersome, error-prone and difficult to maintain.
iSecurity Compliance Management solution helps system administrators to painlessly secure IFS and Native object security. It allows to easily plan the desired security based on object name and type and to check for inconsistencies between actual and planned object security settings. It also provides an easy facility to set system-wide objects rights in accordance with pre-defined templates and includes full reporting features.
- Reduces non-compliance with company defined security policy settings. More productive and efficient way to manage security settings
- Assures settings for object security are not changed and can be combined with iSecurity audit to automatically restore settings that were changed and send an alert of the activity.
- Assures audit and compliance that the data is secure
- User-friendly green screen and GUI interfaces
- 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 Systems (LPARs) definitions with exceptions can be entered to same repository
- Easily Check and Display differences between current security definitions and the planned security definitions
- Site-specific definitions can be planned for multi-site, complex organizations
- Set current security status to the planned definitions
- Full reporting includes support for OUTFILE