Download
1 / 50
500 likes | 645 Views
Authority on Demand Flexible Access Control Solution. The Challenge. Emergency access to critical application data and processes is a very common security breach which is uncovered in System i audits.
E N D
The Challenge Emergency access to critical application data and processes is a very common security breach which is uncovered in System i audits. Currently, manual approaches to this problem are not only error-prone, but do not comply with regulations and auditor’s often stringent security requirements. System i sites define user’s security levels and allocate security rights corresponding to the different job responsibilities in the organization.
AOD Features • Easy to Use - simplifies granting special authorities when necessary, and incorporates easy-to-use reporting and monitoring mechanisms. • Add/Swap Security Levels (unique to iSecurity AOD) - grants a new security authority level or adds additional security rights on request. • Authority Transfer Rules & Providers - enables pre-defining special authority "providers" and special authority transfer rules. • Safe Recovery from Emergency - enables recovering from different types of emergency situations with minimum risk of human error. • Full Monitoring Capabilities - logs and monitors all relevant activities, and sends audit reports and real-time e-mail alerts when employees request higher authority. • Part of End-to-End Solution - solidifies iSecurity's position as the most comprehensive security solution for System i environments. • Intuitive GUI Interface –suitable for non-technical staff. • Controlled Access – allows only relevant personnel to access critical data
Without Authority on Demand: Inefficient Work Mode Authority Request Rejected Richard Garner Busy IT Manager Sam Evans Programmer Has authorities for Test & Development Needs authorities for Production once a week Hi Sam… temporary authorities for the Production folder? Hmmm, I don’t have time now… maybe next week.
With Authority on Demand: Automatic Granting of Special Authorities Let’s define authority rules: When Sam Evens requests authority for Production Folder between 8AM-16:30PM, the system will automatically grant it… Uh, Richard, I need authorities for the Production folder again…
Requesting Special Authority… Now that we have AOD, I’ll request authority… Wow, this is so much easier than calling up Richard…
Instantly & Automatically Receiving Authorities Got the authorities!
Effective Monitoring of Special Authorities Finally, I don’t have to waste my time on granting special authorities… the whole process is automatic and I can see a full log of Sam’s authority requests and even screen captures!
Authority on Demand Log DANA start add authority of user QSECOFR in job 456789/DANA/QPADEV0003. Reason: Need to check problem in production system. Confirmation ID: 5634 Time: 11/03/08 22:40 Attachment 1 – Command entered Attachment 2 – Captured Screens Attachment 3 – DB Records changes DANA end add authority of user QSECOFR in job 456789/DANA/QPADEV0003. Time: 11/03/08 23:19 ID: 653 Command entered ID: 653, Attachment 1 Captured Screens ID: 653, Attachment 2 DB Records changes ID: 653, Attachment 3 * Other attachment options available (all QAUDJRN information, summary of changes made by Ad-Hoc utilities…)
Work with Authority Rules Select Authority Rule to modify.
Modify an Authority Rule Each field needs to be explained individually;“Add authority of Provider” is unique to AOD & ensures that logged info relates to requester .
Modify an Authority Rule Important note below .
Work with Authority Providers Select an Authority Provider to modify.
Request to obtain Authority (GETAOD) Requestor must enter the name of theAuthority provider and either a PIN Code (with Reason *BYPIN) or Reason text.
GETAOD was successful Feedback message below.
GETAOD was not successful Feedback message below.
Request AOD Console Messages Enter command.
Display AOD Log Entries Option 41 from the Main Menu is used to DisplayAOD log entries; can be filtered by requester or provider.
Sample AOD Log Entries Sample AOD Log Entries; F10 provides details.
Select type of AOD Log entries to Display Note the numerous possibilities for displaying AOD log entries.
Audit Log for one Get AOD request This is the QAUDJRN log for one AOD request.
Option 43: Print Log AOD log contains “pointers” (i.e. attachments) to the appropriate QAUDJRN log.
Print output of QAUDJRN This is the printed QAUDJRN log for a singleAOD request.
Showing “Captured” Screen Image This is an actual screen “Capture” of using AOD (back version).
Another “Captured” Screen Image This is one of the user screens “Captured”(frame 11 in the Capture log file).
AOD System Configuration Screen Option 81 from the AOD Main Menu.
General Definitions Configuration Screen Note various general definition parameters.
Exit Programs Configuration Screen AOD allows for site-specific exit programoverrides.
AOD Log Retention Configuration Screen Set the Log Retention period using this screen.
E-mail Definitions Configuration Screen An appropriate license must be signed witha local ISP.
SYSLOG Definitions SYSLOG attributes are defined using Option 8121 from the main menu.
SYSLOG Messages These are the SYSLOG messages writtenwhen authority was added.
Work with AOD Operators Select an AOD Operator to modify.
Modify AOD Operator Rights Full product usage, Emergency usage or useas an Auditor (read-only).
Emergency Operator Screen Current user has been defined as Emergencyoperator, only 1 rule can be modified.
Modify Rule by Emergency Operator Modify the rule which relates this Emergencyoperator; other rules cannot be modified.
Auditor Screen No changes may be made to rules.
Modify Authority Rules screen disabled All input fields are disabled in this mode.
Thank You! Please visit us at www.razlee.com
