Auditing Job Scheduling Operations | ActiveBatch Job Scheduler
Advanced System Concepts Logo
Site Map ArrowSite Map  


Home Home SeparatorSolutions Solutions SeparatorNews Headlines SeparatorCompanyCompany SeparatorServices Services SeparatorSupportSupport SeparatorContacts Right
Top Image

Auditing For Compliance & Control

Bookmark and Share Download POC Download Proof
of Concept
Pricing Info Pricing Info WebEx Demo WebEx Demo

"As IT and the business process become increasingly inseparable, IT Operations has to be in a position to provide necessary compliance information for regulations, such as Euro-SOX, Payment Card Industry Data Security Standards, Basel II and Gramm-Leach-Bliley. Thus job scheduling tools that automate some of these mission critical business processes should provide operational control and data to the businesses to demonstrate compliance."
    -  -  Milind Govekar, Research Vice President, Gartner, Inc.,

ActiveBatch® addresses emerging audit and security requirements to limit the risk of unauthorized changes with its implementation of new traceability, as well as revision comparisons, and restores.
ActiveBatch Mobile Displaying Job Properties and Audit Capabilities
Fig. 1: ActiveBatch Mobile Displaying Job Properties and Audit Capabilities
ActiveBatch Revision History
Fig. 2: ActiveBatch Revision History

ActiveBatch's audit architecture provides details on the creation, modification, triggering and more on each and every ActiveBatch object (e.g. Jobs, Plans, User Accounts, etc.). The audit history is secure and allows for modifications to be visually compared to other changes so that the "differences" are highlighted.

ActiveBatch allows you to select a previous object revision and designate that revision as the most current version of the object. ActiveBatch will then create a new version reference and store that as current reference so as to provide the proper integrity to the audit process.

ActiveBatch provides for critical "compliance and control" processes by supporting the creation of customized audit fields that can either be optional or mandatory in order to meet the specific requirements from internal and external organizations. ActiveBatch Audit fields can be required when objects within the ActiveBatch system are modified, triggered, updated, or added. Fields can be created to require a Description, approved by, authorization ID or any other policy requirement.