Our self service customer portal is currently under maintenance and will be back soon! Sorry for any inconvenience this may have caused.
True or False: Implementing comprehensive and flexible security on NonStop requires complex security rules and configuration settings?
Ever increasing demands and requirements for higher levels of security are the norm for almost any business today. In the typical NonStop environments of financial services, payments and healthcare, these demands are even greater. Sensitive files, data and objects must be available to those applications and individuals that need it, but must be fully secured against those that do not.
Achieving this level of security for your NonStop server does not need to be complex or difficult. XYGATE Object Security (XOS) takes NonStop object access authorization to a whole new dimension.
Safeguard and OSS Security were developed in the 80’s and 90’s when security was less of a priority foroperating systems than it is today. Both have been improved over the years but still retain their original security infrastructure, and constraints, through the use of Access Control Lists (ACLs).
With NonStop systems rapidly growing, more data objects, and more users all needing some level of access to information, the task of setting and maintaining security with these ACLs grows exponentially to the point of being nearly impossible to achieve and impractical to accomplish. Not to mention the effective doubling when two unique operating systems (Guardian and OSS) are used, with vastly different security fundamentals.
XOS, on the other hand, takes a completely different and modern approach to securing NonStop objects. By using rules rather than ACLs, access is granted or denied based on a positive intersection of an object set rule with a user set rule.
Using the Safeguard Authorization SEEP (Security Event Exit Process) and the OSS Nameserver SEEP, XOS enables enforcement of security dynamically as requests are made for access to resources based on custom pre-defined rules according to your security policy.
The wildcarding and other configuration options for XOS ACLs allow for a greatly reduced number of Access Control records. One North American credit card company manages their entire network of HPE NonStop servers with XOS with less than 300 XOS Role Based Access Control rules. Previously, when using Safeguard, over a million Safeguard ACLs were required.
XOS includes a GUI interface to assist with creating and maintaining the simple user and object rules which govern it’s security implementation.