OTS-1100

Online Terminal System 1100

Comprehensive Security for All Your Online Transactions

OTS-1100 protects your OS 2200 online transactions from unauthorized use by validating user credentials in relation to transaction functions. You can establish a secure transaction environment without changing your online programs.
You can also use OTS in conjunction with DPS to implement field-level security.

If you are able to modify your application programs, you can use the application interface (AI) in OTS to deliver authorization data to the executing program. That program can then make detailed decisions to permit or withhold individual transaction functions, based on the user’s security profile.

OTS-1100 provides flexible options for its installation and configuration. You choose the method most compatible with your site standards and existing online infrastructure.

OTS-1100 interoperates with Unisys’ offerings within their communications and transaction ecosystem:

TIP
DPS
MCB
SILAS
WebTS
CPComm / CPCommOS

Key Features

OTS implements a sign on transaction, compatible with transaction components in OS 2200, including DPS and TIP Session Control.

Unauthorized users are automatically signed off.

When a user exceeds a configurable maximum of sign on violations they are prevented from logging on.

Administrators set the expiration period for passwords. Users change passwords more often.

Administrators can set differential permissions at different levels of granularity.

Flexible options to implement user authorization.

Options to interoperate with DPS to implement screen field level authorization.

Application interface (AI) allows developers to modify programs to receive authorization profile and make highly specific security decisions.

Administrators organize transactions in groups to pool security levels for similar transactions.

Compatible with the UniAcess transction server.

Reports to inform and guide administrators.

Convenient methods to support development and testing environments.

Release Announcements

Product Description

For all your online applications

Implementation Options

You choose how to install OTS depending on the transaction deployment philosophy at your site.

Your systems administrators install an OTS-1100 modules in one or more components of your transaction infrastructure. The OTS module authorizes users based on their security profile and the requirements of the transaction they wish to access.

Each implementation option is briefly summarized below. For some sites, the best solution is a combination of methods.

For more information, click on the button “Product Description.”

MCB Implementation

You BUILD MCB with an OTS-1100 module included. When the user executes a transaction, MCB checks first with OTS to see if the user is authorized. If not, the user’s request is rejected. This method is highly efficient because an unauthorized attempt doesn’t even load the transaction.

TIP Implementation

You BUILD TIP with an OTS modification to the module INITAL. When the user executes a transaction, the transaction’s call to CINIT in the INITAL module first checks with OTS to see if that user is authorized. If not, the user’s request is rejected.

DPS Implementation

You BUILD DPS with an OTS modification to the modules ACOB/INTERFACE or UCS/INTERFACE. You can implement two kinds of protection.

You can configure DPS to authorize the user’s access to the entire screen.

You can use DPS’ built-in field level security to activate only those screen fields authorized via the user’s security profile.

OTS Application Interface (AI)

Programmers compile and link their transaction program with the OTS-1100 Application Interface (AI) module. When the user executes the program, it immediately calls OTS and obtains the user’s OTS security profile. The transaction can then make fine-grained decisions about which functions to authorize, based on the user’s profile.

Protect and manage your online applications.

Flexible implementation. Easy to use. Strengthens your enterprise security.