Broadcom z/OS zVSE/VSEn

Auditor for z/OS Modernization Guide

Report Generation and ManagementAdministrationSecurity

Auditor for z/OS is a report generation and management product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Auditor for z/OS is a security analysis tool for the z/OS operating system.

It helps ensure compliance with industry regulations by providing a comprehensive view of the security posture of the z/OS environment.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does Auditor for z/OS do?

Auditor for z/OS analyzes z/OS system configurations and parameters to identify potential security vulnerabilities and exposures. It generates reports that highlight areas of concern, allowing administrators to proactively address security risks and maintain a secure z/OS environment.

Is this a system, application, or tool?

Auditor for z/OS is a tool set designed to analyze and report on the security posture of z/OS systems. It provides a comprehensive view of security-related configurations and settings, enabling administrators to identify and remediate potential weaknesses.

What types of organizations use this?

Organizations that rely on the z/OS operating system and require robust security auditing and compliance capabilities benefit most from Auditor for z/OS. This includes enterprises in industries such as banking, finance, insurance, and government.

When should we consider Auditor for z/OS?

A company should consider using Auditor for z/OS when it needs to proactively assess and improve the security of its z/OS environment, ensure compliance with industry regulations, or respond to audit requirements. It is particularly useful when changes are made to the system configuration or when new security threats emerge.

What are the alternatives to Auditor for z/OS?

Alternatives to Auditor for z/OS include IBM Security zSecure, and manually reviewing z/OS security settings. Each option has different capabilities for automated analysis and reporting.

Technical

What infrastructure is required?

Auditor for z/OS runs on the z/OS operating system and requires access to system resources and security subsystems such as RACF, ACF2, or Top Secret. It operates within an LPAR and leverages standard z/OS facilities for data access and reporting.

How is Auditor for z/OS deployed?

Auditor for z/OS is deployed on-premise within the z/OS environment. It requires a dedicated LPAR with sufficient resources to perform security analysis and generate reports. The implementation process involves configuring the product to access the necessary system data and defining the scope of the security audit.

What configuration files are used?

Auditor for z/OS uses configuration files to define the scope and parameters of the security analysis. These files specify the system resources to be audited, the security checks to be performed, and the format of the generated reports. The product also provides interfaces for customizing the audit process and tailoring the reports to meet specific requirements.

Does Auditor for z/OS have an API?

Auditor for z/OS does not expose public APIs. It primarily functions as a standalone tool for analyzing z/OS security configurations and generating reports. Integration with other systems is typically achieved through data exchange using standard z/OS facilities.

Business Value

What is the business value of Auditor for z/OS?

Auditor for z/OS helps organizations reduce the risk of security breaches and data loss by identifying and addressing potential vulnerabilities in their z/OS environment. By proactively monitoring security configurations and ensuring compliance with industry regulations, it minimizes the likelihood of costly incidents and protects sensitive data.

When should we consider Auditor for z/OS for compliance?

Organizations should consider Auditor for z/OS when they need to demonstrate compliance with security regulations such as PCI DSS, HIPAA, or GDPR. The product provides the necessary tools to assess the security posture of their z/OS environment and generate reports that document their compliance efforts.

What happens if we do not use Auditor for z/OS?

Without Auditor for z/OS, organizations may struggle to maintain a secure z/OS environment and comply with industry regulations. They may face increased risk of security breaches, data loss, and financial penalties. The manual effort required to perform security audits and generate compliance reports can be time-consuming and error-prone.

Security

How does Auditor for z/OS handle authentication?

Auditor for z/OS supports authentication through standard z/OS security subsystems such as RACF, ACF2, and Top Secret. It leverages these systems to verify user identities and control access to sensitive data and resources. The access control model is based on the security policies defined within these subsystems.

What access control model is used?

Auditor for z/OS uses the access control mechanisms provided by z/OS security subsystems (RACF, ACF2, Top Secret) to control access to data and functions. It analyzes existing security rules and configurations to identify potential vulnerabilities and ensure that access is granted only to authorized users.

What audit/logging capabilities exist?

Auditor for z/OS generates audit logs that record all security-related events and activities within the z/OS environment. These logs can be used to track user access, detect suspicious behavior, and investigate security incidents. The product provides tools for analyzing and reporting on the audit log data.

Operations

What level of technical expertise is required?

Implementing Auditor for z/OS requires expertise in z/OS security administration and a thorough understanding of the organization's security policies and procedures. Ongoing operational requirements include monitoring the product's performance, maintaining the configuration files, and reviewing the generated reports.

What are common implementation challenges?

Common implementation challenges include configuring the product to access the necessary system data, defining the scope of the security audit, and customizing the reports to meet specific requirements. It is important to carefully plan the implementation process and involve experienced z/OS security administrators.

What monitoring/logging capabilities exist?

Auditor for z/OS provides monitoring and logging capabilities to track its own performance and identify potential issues. The product generates logs that record all significant events and activities, including errors, warnings, and informational messages. These logs can be used to troubleshoot problems and ensure the product is functioning correctly.

Ready to Start Your Migration?

Download our comprehensive migration guide for Auditor for z/OS or calculate your ROI.

Calculate ROI