Name: Vanguard ez/Integrator
Availability: InStock

Question 1

What is Vanguard ez/Integrator used for?

Question 2

What problem does Vanguard ez/Integrator solve?

Accepted Answer

Vanguard ez/Integrator enables applications on distributed platforms to perform security validation using RACF on z/OS. It provides an API for secure access to mainframe security resources. This allows organizations to extend their security policies across heterogeneous environments.

Question 3

What platforms are supported by Vanguard ez/Integrator?

Accepted Answer

It addresses the challenge of integrating mainframe security with distributed applications. By providing a consistent security interface, it simplifies the process of authenticating and authorizing users across different platforms. This reduces the complexity and risk associated with managing security in hybrid environments.

Question 4

How does Vanguard ez/Integrator integrate with existing security infrastructure?

Accepted Answer

Vanguard ez/Integrator supports Microsoft Windows, UNIX, and System i (AS/400) platforms. This cross-platform compatibility allows organizations to leverage their existing security infrastructure while supporting a diverse range of applications and systems.

Question 5

What are the key benefits of using Vanguard ez/Integrator?

Accepted Answer

It integrates with existing security infrastructure by utilizing RACF on z/OS. The API allows applications to interact with RACF for authentication, authorization, and auditing. This integration ensures that security policies are consistently applied across all supported platforms.

Question 6

Is there a trial version available?

Accepted Answer

Key benefits include centralized security management, reduced development time, and improved compliance. It simplifies the process of securing applications, reduces the risk of security breaches, and helps organizations meet regulatory requirements by providing a consistent security framework.

Question 7

How is Vanguard ez/Integrator licensed?

Accepted Answer

Please consult with Vanguard directly to inquire about trial versions or proof-of-concept opportunities.

Question 8

What is the typical deployment architecture for Vanguard ez/Integrator?

Accepted Answer

Licensing details are available from Vanguard directly. Contact their sales or licensing department for specific information.

Question 9

What kind of support is available for Vanguard ez/Integrator?

Accepted Answer

The deployment architecture typically involves a component on the z/OS mainframe that interfaces with RACF and components on the distributed platforms that utilize the API. The specific architecture will vary based on the application and platform requirements.

Question 10

What are the system requirements for Vanguard ez/Integrator?

Accepted Answer

Vanguard provides support through various channels, including documentation, online resources, and direct support. Contact Vanguard's support team for assistance.

Question 11

What are the common API operations and their syntax?

Accepted Answer

The API supports operations such as user authentication, resource authorization, and security attribute retrieval. The exact syntax depends on the chosen API (e.g., REST, SOAP). Example: A REST call might use a URL like `/auth/user` with parameters for username and password.

Question 12

What configuration files or interfaces are used?

Accepted Answer

Configuration is typically managed through configuration files on both the z/OS and distributed platforms. These files define connection parameters, security settings, and API behavior. The specific format depends on the chosen API and platform.

Question 13

What types of APIs does this product expose?

Accepted Answer

Vanguard ez/Integrator exposes APIs for integration. The specific API types include REST and SOAP. Endpoint patterns vary based on the operation, such as `/auth/user` for authentication. Supported programming languages and SDKs include those compatible with REST and SOAP.

Question 14

What are the main system components and how do they communicate?

Accepted Answer

The main system components include the z/OS component, the API gateway, and the client libraries. These components communicate using protocols like HTTP(S). The z/OS component interacts with RACF, and the API gateway handles requests from distributed platforms.

Question 15

What security features are supported?

Accepted Answer

The product uses RACF for user authentication and authorization. It supports various authentication methods, including username/password. Access control is based on RACF profiles and permissions. Encryption is used for secure communication over HTTPS.

Question 16

What audit/logging capabilities exist?

Accepted Answer

The product supports logging of security events, including authentication attempts and authorization decisions. These logs can be used for auditing and security analysis. The specific logging mechanisms depend on the platform and API used.

Question 17

How does Vanguard ez/Integrator provide business value?

Accepted Answer

Vanguard ez/Integrator helps reduce the time and cost associated with developing and maintaining security integrations across different platforms. It provides a centralized security management solution, which simplifies administration and reduces the risk of security breaches.

Question 18

How does Vanguard ez/Integrator simplify security management?

Accepted Answer

By providing a consistent security interface, Vanguard ez/Integrator simplifies the process of securing applications across different platforms. This reduces the complexity and effort required for security integration, allowing organizations to focus on their core business functions.

Question 19

How does Vanguard ez/Integrator assist with regulatory compliance?

Accepted Answer

Vanguard ez/Integrator helps organizations meet regulatory requirements by providing a consistent security framework and audit trails. This ensures that security policies are consistently applied across all supported platforms, simplifying compliance efforts.

Question 20

How does Vanguard ez/Integrator improve security posture?

Accepted Answer

By centralizing security management, Vanguard ez/Integrator reduces the risk of security breaches. The consistent application of security policies across all platforms minimizes vulnerabilities and protects sensitive data.

Question 21

How does Vanguard ez/Integrator protect existing investments?

Accepted Answer

Vanguard ez/Integrator allows organizations to leverage their existing investment in RACF. By integrating with RACF, organizations can extend their security policies to distributed platforms without replacing their core security infrastructure.

Question 22

What authentication methods are supported?

Accepted Answer

Vanguard ez/Integrator supports authentication via username/password, leveraging RACF for validation. It also uses HTTPS to encrypt communication between components. Access control is managed through RACF profiles and permissions.

Question 23

What access control model is used?

Accepted Answer

Access control is based on RACF profiles and permissions. Users are granted access to resources based on their RACF group memberships and the permissions defined in the RACF profiles. This ensures that only authorized users can access sensitive data.

Question 24

What encryption is used and where?

Accepted Answer

Encryption is used for secure communication over HTTPS. This protects data in transit between the distributed platforms and the z/OS mainframe. The specific encryption algorithms used depend on the HTTPS configuration.

Question 25

What audit/logging capabilities exist?

Accepted Answer

Vanguard ez/Integrator provides audit/logging capabilities to track security-related events. These logs include authentication attempts, authorization decisions, and other relevant information. The logs can be used for security analysis and compliance reporting.

Question 26

What security best practices should be followed?

Accepted Answer

Security best practices include regularly reviewing RACF profiles, monitoring security logs, and keeping the software up-to-date. It is also important to follow the vendor's recommendations for securing the API and the communication channels.

Question 27

What administrative interfaces are available?

Accepted Answer

Administrative interfaces include configuration files and potentially a web-based console. User management is handled through RACF on z/OS. Configuration parameters include connection details, security settings, and API behavior.

Question 28

How is user management handled?

Accepted Answer

User management is primarily handled through RACF on z/OS. User accounts and permissions are managed within RACF, and Vanguard ez/Integrator leverages these existing user profiles for authentication and authorization.

Question 29

What are the main configuration parameters?

Accepted Answer

Main configuration parameters include connection details for the z/OS system, security settings for authentication and authorization, and API behavior settings. These parameters are typically set in configuration files.

Question 30

What monitoring/logging capabilities exist?

Accepted Answer

Monitoring and logging capabilities include logging of security events, such as authentication attempts and authorization decisions. These logs can be used for auditing and troubleshooting. The specific logging mechanisms depend on the platform and API used.

Question 31

What are the network requirements?

Accepted Answer

Network requirements include connectivity between the distributed platforms and the z/OS mainframe. The specific ports used depend on the chosen API and communication protocols (e.g., HTTPS). Ensure proper firewall rules are in place.

Share Your Product Experience

Vanguard ez/Integrator

Product Overview

Frequently Asked Questions

What is Vanguard ez/Integrator used for?

What problem does Vanguard ez/Integrator solve?

What platforms are supported by Vanguard ez/Integrator?

How does Vanguard ez/Integrator integrate with existing security infrastructure?

What are the key benefits of using Vanguard ez/Integrator?

Is there a trial version available?

How is Vanguard ez/Integrator licensed?

What is the typical deployment architecture for Vanguard ez/Integrator?

What kind of support is available for Vanguard ez/Integrator?

What are the system requirements for Vanguard ez/Integrator?

What are the common API operations and their syntax?

What configuration files or interfaces are used?

What types of APIs does this product expose?

What are the main system components and how do they communicate?

What security features are supported?

What audit/logging capabilities exist?

How does Vanguard ez/Integrator provide business value?

How does Vanguard ez/Integrator simplify security management?

How does Vanguard ez/Integrator assist with regulatory compliance?

How does Vanguard ez/Integrator improve security posture?

How does Vanguard ez/Integrator protect existing investments?

What authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

What security best practices should be followed?

What administrative interfaces are available?

How is user management handled?

What are the main configuration parameters?

What monitoring/logging capabilities exist?

What are the network requirements?

Related Products

More from Vanguard

Similar Products

Help Improve This Directory

Are You a Vendor? Claim Your Listing