Regulate the Use of File Editors in Production Environments
Safe-Update guards against unauthorized updates by dangerous programs – programs were not designed for the organization’s business rules and do not comply with them. With Safe-Update, administrators can implant a security layer in the files themselves which will resist unauthorized updates even if powerful users who have *ALLOBJ authority perform them. The specification is made by lists of programs that are allowed or prevented from updating programs. The editable list of blocked programs can include known file editors, DFU and the Start SQL command.
When the organization needs to update data with tools that are normally not allowed, Safe-Update implements a workflow that consists of work orders, created by management, that specify who can work with the data, the reason for the work, and the limited time during which the work order is valid. Based on the work order, the specified programmer can then open a ticket and perform the requested updates interactively or in batch. All work under the tickets is logged, even if the data files themselves are not journaled.
If an unauthorized update is attempted, a window appears requesting the entry of a ticket.
iSecurity Safe-Update Key Features
- Monitors and protects data against updates by unauthorized programs.
- Allows authorized users to create ad-hoc tickets, which are tracked in the same way as work orders.
- Work orders specify the programmer, the files, the updates required and the time frame.
- Tickets are automatically closed if inactive for a period of time.
- Allows updates to fields that are marked as insignificant.
- Subject to the organization policy, ad-hoc tickets might be permitted as well.
- Creates a record of updates, logging who updated the data, who authorized the update, and why it was done.
- Database journal information displayed by AP-Journal commands highlights updates made under Safe-Update permissions.
Safe-Update protects IBM i business-critical data against updates made using programming tools or programs which are not among those that are dedicated to update this data.
Security systems limit what users can do. Safe-Update adds a layer of security: it identifies the program that wishes to update the secured file and decides whether or not to allow it. The Sarbanes-Oxley Act and other regulations require that only authorized programs update critical data. Programs such as DFU, the interactive Start SQL (STRSQL) command, and third-party file editors are therefore considered potentially risky and are forbidden. Using such programs makes your systems unreliable and creates a huge risk of fraud.
Security systems that protect data by preventing the access of programmers to production environments are not enough. Occasionally programmers need to conduct some missions and temporarily get *ALLOBJ authority. As there is no way to restrict them to that mission, they became a potential risk.
Safe-Update’s new security layer ensures that only authorized programs are used to update business critical files.
Safe-Update is the latest component of Raz-Lee’s iSecurity suite.
Once set, Safe-Update protects all updates and ensures they are done by specified programs, by creating specified whitelists or blacklists.
A whitelist specifies the programs that can update a file. It contains multiple entries, each specifying generic program names and generic library names.
A standard blacklist of programs, specifying DFU, STRSQL and other known file editors, is provided with the product. It can be modified according to the organization needs.
Safe-Update implements a workflow for situations when there is a need to update data with tools or programs that are not normally allowed. The workflow is based on work orders, created by management. A work order specifies the reason it was opened, the programmer or programmers that can perform it, the file or files the programmer can update, the time frame that it remains active, and more.
When an assigned programmer is ready, he generates a ticket under the work order. The ticket instructs Safe-Update to allow his activity and trace it. All work is logged, even if the data files themselves are not journaled.
Some organizations may allow ad-hoc tickets. These tickets are not related to existing work orders. Instead, the tickets themselves contain all the relevant information.
- Monitors and protects updates to data according to the program used.
- Uses either a whitelist of allowed programs, or a blacklist of programs that are not allowed.
- Ensures that DFU, Start SQL and file editors are not used in production environments even when *ALLOBJ is in effect.
- Restriction of updates can be removed when the update is only for field marked in advance as “insignificant”.
- Programs that may not update data can read it. They will be stopped when an update is issued.
- Comprehensive workflow of management-approved work orders with tickets opened by preassigned programmers.
- Organizations may decide to also allow ad-hoc tickets.
- Additional permission may be requested in real time
- Ticket is opened for the current job or for the current user.
- Ticket opened for the current user, allows updates by batches jobs as well.
- Ticket become automatically invalid after few minutes of inactivity.
- Manages the full history of the activities.
- Creates full trace of updates even when the file is not journaled.
- When AP-Journal commands are used to display update information from the standard database journals, updates made under Safe-Update are highlighted.
- Possibility to undo updates.