What was the architecture of SecurAccess?

SecurAccess utilized a client-server architecture. The client component resided on the user's workstation, while the server component ran on the z/OS mainframe. Communication between the client and server used proprietary protocols.

What configuration files or interfaces were used?

The product used configuration files to store settings such as user mappings, security policies, and connection parameters. These files were typically managed through the administrative interface. The configuration files are no longer supported.

What administrative interfaces were available?

SecurAccess provided a command-line interface (CLI) for administrative tasks. Common commands included user management, policy configuration, and system monitoring. The CLI is no longer supported.

How did SecurAccess provide business value?

SecurAccess aimed to reduce the administrative overhead associated with managing user access across multiple systems. By providing a single point of authentication, it simplified user provisioning and de-provisioning processes. The business value is now provided by other solutions.

How did SecurAccess impact user productivity?

The product aimed to improve user productivity by eliminating the need to remember multiple passwords. This streamlined the login process and reduced the time users spent authenticating to different systems. The user productivity is now provided by other solutions.

How did SecurAccess improve security?

SecurAccess aimed to reduce the risk of unauthorized access by centralizing authentication and authorization. This allowed for more consistent enforcement of security policies and improved overall security posture. The security is now provided by other solutions.

What authentication methods were supported?

SecurAccess supported various authentication methods, including password-based authentication and potentially integration with external authentication systems. The authentication methods are no longer supported.

What access control model was used?

The product used access control lists (ACLs) to manage user permissions. ACLs defined which users or groups could access specific resources or perform certain actions. The access control is no longer supported.

What audit/logging capabilities existed?

SecurAccess provided audit logging capabilities to track user activities and system events. These logs could be used for security monitoring and incident investigation. The audit logging is no longer supported.

What administrative interfaces were available for operations?

Administrative tasks were performed through a command-line interface (CLI). This interface allowed administrators to manage users, configure security policies, and monitor system activity. The operations are no longer supported.

How was user management handled?

User management involved creating, modifying, and deleting user accounts. Administrators used the CLI to perform these tasks, including assigning permissions and managing group memberships. The user management is no longer supported.

What were the main configuration parameters?

The main configuration parameters included settings for authentication, authorization, and system behavior. These parameters were stored in configuration files and managed through the CLI. The configuration is no longer supported.

What monitoring/logging capabilities existed?

SecurAccess provided logging capabilities to record system events and user activities. Administrators could review these logs to monitor system health and troubleshoot issues. The monitoring is no longer supported.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

SecurAccess

Beta Systems Not Supported z/OS

Sharing Security

Vendor

Beta Systems

Product Overview

SecurAccess employed a client-server architecture. The client component, installed on user workstations, facilitated user interaction and authentication requests. The server component, residing on the z/OS mainframe, handled authentication, authorization, and policy enforcement.

Communication between the client and server utilized proprietary protocols. The core components included the SecurAccess Client, the SecurAccess Server, and the Configuration Manager. The Configuration Manager was used to manage configuration files.

The product did not expose standard APIs like REST or SOAP. Integration with other systems was typically achieved through custom scripting or direct interaction with the client-server components. The CLI provided administrative capabilities.

Common commands included `ADDUSER `, `MODIFYUSER `, `DELETEUSER `, `SETPOLICY `, and `STATUS`. Authentication was primarily password-based. Access control was managed using access control lists (ACLs).

Configuration files stored settings such as user mappings, security policies, and connection parameters. The product is no longer supported. Organizations should migrate to a modern SSO or PAM solution.

Frequently Asked Questions

What was the primary purpose of SecurAccess?

SecurAccess was designed to provide a single sign-on (SSO) solution for z/OS environments. It aimed to simplify user access management by consolidating credentials. The product's functionality is now provided by other solutions.

What is the history of SecurAccess and its ownership?

SecurAccess was originally developed by Blockade and later acquired by Proginet. Beta Systems acquired the product in 2008. The product is no longer supported by Beta Systems.

What systems did SecurAccess integrate with?

SecurAccess was designed to integrate with z/OS systems. It provided a centralized authentication and authorization mechanism for various applications and resources within the z/OS environment. The product's integration capabilities are now provided by other solutions.

How did SecurAccess improve the user experience?

SecurAccess aimed to simplify user access management by providing a single point of authentication. This reduced the need for users to remember multiple passwords and streamlined the login process. The product's user experience is now provided by other solutions.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Are You a Vendor? Claim Your Listing

SecurAccess

Product Overview

Frequently Asked Questions

What was the primary purpose of SecurAccess?

What is the history of SecurAccess and its ownership?

What systems did SecurAccess integrate with?

How did SecurAccess improve the user experience?

What was the architecture of SecurAccess?

What configuration files or interfaces were used?

What administrative interfaces were available?

What types of APIs did SecurAccess expose?

How did SecurAccess provide business value?

How did SecurAccess impact user productivity?

How did SecurAccess improve security?

What authentication methods were supported?

What access control model was used?

What audit/logging capabilities existed?

What administrative interfaces were available for operations?

How was user management handled?

What were the main configuration parameters?

What monitoring/logging capabilities existed?

Related Products

More from Beta Systems

_beta access admin

_beta access audit

_beta access easy

_beta access monitor

_beta doc|z plus

_beta doc|z transform

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta access monitor

ACF2

ActiVisor

Help Improve This Directory

Are You a Vendor? Claim Your Listing