Job Scheduling Security

Security Coupled With Robust Compliance & Control Capabilities Addresses Auditors Requirements

---

Figure 1: Active Directory, ADAM And The Windows Security Model Fully Implemented Figure 2: ActiveBatch Objects With Full Audit History Figure 3: Compare And Contrast Modifications By Revisions

Enterprise applications, such as ActiveBatch® must provide a secure environment, which does not impose incremental costs of implementation and maintenance. ActiveBatch fully utilizes the Microsoft security model including Kerberos allowing an organization to make full use of their existing accounts and groups for the implementation and operational use of the job scheduling solution from day one.

Active Directory or Active Directory Application Management (ADAM) has become a core technology for IT security groups to manage and authenticate IT users. Active Directory controls access to applications and systems as well as allows the organization to comply with internal and external audit and control requirements. ActiveBatch fully integrates Active Directory or ADAM so that organizations can use an established approach to authentication without having to relearn and train staff on new approaches used by other solutions.

With ActiveBatch Enhanced Directory Services the installation and starting of the ActiveBatch Execution Agent on a Windows or Non Windows systems allow all of those systems to be visible through Microsoft’s Active Directory. This allows non-Windows systems, in particular, to have access to publishing and high-availability features that were previously only available on the Windows platforms.

ActiveBatch addresses audit and security requirements that seek to limit the risk of unauthorized changes with audits and advanced traceability, revision control and compliance functionality. Audits are an integral part of each ActiveBatch object and system and allow for the creation of policies that allow for the establishment of customized fields that can be set as mandatory or option on various modifications to the object. In an ideal world external or internal regulations would result in clearly defined requirements and policies for control. ActiveBatch, built for the real world, allows for the creation of audit trails, reasons for change, authorization ID’s or any requirement of the auditors.

ActiveBatch’s additional flexibility to compare the specific changes and approvals for each revision level to a previous or baseline change over time clearly identifies what has changed and the supporting documentation, such as approval levels, description of the changes etc. for each update.