When you plan security, you must consider security requirements at each of the following network nodes: client, TRS, and mainframe. Your security plan for TRS must address the following issues:
Client permissions. Does the client have permission to log into the network? Can the client’s login information be stored and passed along to TRS for permission checking at that level? Can it be passed to the mainframe to support security systems in use there?
Adaptive Server permissions. If client requests are routed to TRS through Adaptive Server, which commands, data objects, stored procedures, and views does the client have permission to use? Will the client use long running transactions? (Long-running transactions can be sent through ASE/CIS.)
(LU 6.2 only) Mainframe connection permission. Does the client have permission to use a given LU 6.2 connection to the mainframe?
Mainframe transaction permission. Does the client have permission to execute a given mainframe transaction?
Mainframe data resource permission. Does the client have permission to access or modify the data in a particular file or database?
For information on client login and Adaptive Server security, see the Adaptive Server and Open Client and Open Server documentation. Sybase security at the mainframe is described in the Open ServerConnect Installation and Administration Guide for IBM CICS/MVS and MainframeConnect Installation and Administration Guide for DB2 UDB. You can find additional information about mainframe security in your vendor documentation.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
