|
|
|
|
|
|
|
|
Security Stopgaps are filled by XEC in a Dynamic way Who needs XEC Datavault? No financial institution can afford data security failures. With the ever-increasing use of work station platforms interfacing with host applications, screen-scraping applications, online banking and the enormous acquisition activity causing cross-company confidentiality concerns, banks need to be adamant in their pursuit of tight security structures. Not all security breaches are malicious. Mishaps occur regularly when users have inappropriate access for their job functions. Errors of both kinds can cause great financial loss. Who can put a price on a bank's damaged reputation? Ask yourself...Where are our weaknesses? Consider these quotes from security experts: "More common than hackers is employee theft" "Security breaches always occur at the weakest link - technology or people" "Executives should think about the huge losses already attributed to weak security, and do what they can to prevent that particular element of history from repeating itself." "Aim for single sign-on across applications" "If you're not willing to go it alone and customize your own security solution, pressure vendors to come up with products" We at Securis Corporation have the product. We have the solution! A full comprehensive security solution has been cost prohibitive to develop in-house. Hogan managers have had to use alternate means of getting by. Review some of the limitations experienced by these alternatives to true data security and how XEC Datavault offers resolution to them all. Methods currently used no longer hold up to the sophisticated systems in place. Each of the following methods contains pitfalls that need to be avoided. 1. Transaction Level Security is too global to serve the needs of Hogan users. It cannot secure sub-functions with the multiple maps. For example, transactions like UMB, HCIS, DDMU, TDMU, PAS. XEC complements transaction level security by securing activity in greater depth (maps, screen actions, fields, field content) 2.
Function Processing System (FPS) is useful for departmental access
within FPS driven applications however, security rules and the operator
Ids are controlled within the application instead of by the enterprise
data security system. Custom programming is required within the applications
to fully utilize FPS security. 3. Release Control System (RCS) is often used for data security. RCS is a change management system and is controlled within the Hogan environment. Once an operator has access to a change control number, he may update any item within the application ownership, not just the intended item. XEC can provide update access to specific items while protecting all other items within the application family. 4. Application code edit checks are often performed to make security decisions. (One example, a program table of IRA department terminal IDs that is checked to allow only these terminals access to IRA functions.) This takes control outside the E.S.S. and leaves banks vulnerable. Security breaches are difficult to track since these did not go through the E.S.S. Additionally, changes are cumbersome to make since security checks are embedded within the application programs. XEC requires no Hogan application code changes to secure data. 5. You no longer need alternate views of PCDs for security. Banks have resorted to developing alternate views of delivered PCDs so that fields may be hidden or protected from user access. This additional development is not necessary with XEC. XEC can hide or protect fields dynamically based on the user signed on, leaving Hogan maps and PCDs vanilla. This is good news indeed. XEC can provide inquiry access to PCDs while limiting updates to those who need it. Without XEC, if you have inquiry access, you also have update capabilities. You no longer have to take away all production access from your systems support staff to protect data from updates. XEC allows you to give your team members inquiry to PCDs for research but prevent any updates from occurring. Your EDP Auditors will be relieved. 6. Workstation Platform: Downloading security profiles to the workstation platform assists in workflow presentation; however, host data is still vulnerable as messages access the application databases for either update or inquiries. XEC provides the means to secure the PASS messages at the host with the enterprise security system coming both to and from the host. XEC secures access to the PASS messages from the general functionality of the message down to the field level. What can XEC do for you? Your transactions are secured. How about your... • Maps? • Actions? • Fields? Secure access from your 3270 terminals, PASS messages from and to your work station platforms, and even from screen scraping applications. PCDs and CDMF formats can be secured from any online device, including programs. XEC provides the path to your enterprise security system at each of these junctures. How Secure is XEC Datavault? XEC Datavault puts your enterprise data security system in control - where it should be. No longer will security calls need to be made from your application programs. XEC control records are housed on a unique CDMF that is secured independently by your enterprise data security system. XEC code is completely outside the Hogan applications, interfacing with Umbrella. XEC supports single sign-on, controlled by your enterprise data security system. Auditing: |
