|
|
|
Overview
|
Screens
|
iSecurity Native Object Security
Definition of Target Security Levels per Object & Type
The challenge of securing native OS/400 objects is the basis for Power 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.
And, since OS/400 requires very technical definitions per each object in the system, this activity is cumbersome, error-prone and hard to maintain.
The Native Object Security solution enables system administrators to easily define target security levels per object and object type, and to check for inconsistencies between actual and planned object security settings. The product also enables using generic object names, and includes full reporting features.
View Native Object Security Screens
Native Object Security Features
|
- Full control of all related parameters and resources: Owners, Authorization lists, User authorities, Primary Groups and more.
- Native object security plans are based upon object type and generic names.
- Easily Check and Display differences between current security definitions and the planned security definitions
- Set current security status to the planned definitions.
Native Object Security Planning & Setup Features
- Plan security definitions using generic names, reducing the number of rules required to maintain.
- Check plans with current status and show inconsistencies.
- Set to the current status to the planned definitions.
- Sets Owner, Authorization List, Primary group, Specific user authorities (Add/Replace)
- Product can also can set Audit value and Reset usage count for objects.
- Full reporting includes support for OUTFILE.
Learn about related iSecurity products:
Replication
Action
Assessment
System Control
|
| |
Action