Dell Computer Corporation z/OS

NC-Pass Modernization Guide

Application/Application EnviromentSecurity

NC-Pass is a application/application enviroment product by Dell Computer Corporation. Explore technical details, modernization strategies, and migration paths below.

Product Overview

NC-Pass is a security application designed for z/OS environments that enhances the security of VTAM applications.

This adds an extra layer of security, protecting sensitive mainframe data from unauthorized access. NC-Pass integrates with existing z/OS security systems such as RACF, ACF2, and Top Secret.

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 NC-Pass do?

NC-Pass is a security application that runs on z/OS. It restricts user access to specific VTAM applications and can enforce multi-factor authentication using personal tokens. This helps organizations control access to sensitive mainframe resources.

Is this a system, application, or tool?

NC-Pass is an application that enhances the security of existing VTAM applications on z/OS. It is not a system or a toolset, but rather a security layer that integrates with existing mainframe infrastructure.

What types of organizations use this?

Organizations that rely on VTAM applications on z/OS and need to restrict user access based on application or require stronger authentication methods would benefit from NC-Pass. This includes financial institutions, government agencies, and any enterprise with sensitive mainframe data.

When should we consider NC-Pass?

A company should consider NC-Pass when they need to limit which VTAM applications users can access, or when they need to implement multi-factor authentication for mainframe access. This is especially important when dealing with sensitive data or compliance requirements.

What are the alternatives to NC-Pass?

Alternatives to NC-Pass include other mainframe security products that offer access control and authentication features. Examples include IBM Resource Access Control Facility (RACF) and Computer Associates ACF2. These products provide broader security features, but NC-Pass focuses specifically on VTAM application access.

Technical

What infrastructure is required?

NC-Pass runs on the z/OS operating system and requires VTAM to be active. It operates within an LPAR and integrates with existing security systems like RACF, ACF2, or Top Secret. It needs access to user authentication databases and token management systems.

How is NC-Pass deployed?

NC-Pass is deployed on-premise within the z/OS environment. It requires technical expertise in z/OS, VTAM, and mainframe security. Implementation involves configuring access rules, integrating with authentication systems, and testing the configuration.

Does this replace or enhance VTAM?

NC-Pass enhances the security of VTAM applications. It does not replace VTAM, but rather adds a layer of access control and authentication. It works in conjunction with VTAM to provide a more secure environment.

How does it integrate with existing security systems?

NC-Pass integrates with existing security systems on z/OS, such as RACF, ACF2, or Top Secret. It uses these systems for user authentication and authorization. It can also integrate with external authentication systems via standard protocols.

Business Value

What is the business value of NC-Pass?

NC-Pass helps organizations reduce the risk of unauthorized access to sensitive mainframe applications and data. By limiting access to specific VTAM applications and enforcing multi-factor authentication, it prevents data breaches and ensures compliance with security regulations.

What happens if we do not use NC-Pass?

Without NC-Pass, organizations are more vulnerable to unauthorized access to VTAM applications and sensitive data. This can lead to data breaches, compliance violations, and financial losses. NC-Pass provides a critical layer of security to protect mainframe resources.

What is the typical licensing model?

The licensing model for NC-Pass is typically based on the number of users or the number of VTAM applications protected. The total cost of ownership includes the licensing fees, implementation costs, and ongoing operational expenses.

How does this integrate with enterprise ecosystems?

NC-Pass integrates with enterprise ecosystems by leveraging existing security systems and authentication protocols. It can integrate with LDAP directories, SIEM platforms, and other enterprise security tools to provide a comprehensive security solution.

Security

What authentication methods are supported?

NC-Pass supports authentication methods such as password-based authentication, multi-factor authentication using tokens, and integration with external authentication systems. It uses an access control model based on roles and application assignments.

What encryption is used and where?

NC-Pass uses encryption to protect sensitive data in transit and at rest. It supports standard encryption protocols such as TLS/SSL for communication and encryption algorithms for data storage. Specific encryption methods depend on the configuration.

What audit/logging capabilities exist?

NC-Pass provides audit logging capabilities to track user access to VTAM applications, authentication attempts, and configuration changes. These logs can be used for security monitoring, compliance reporting, and forensic analysis.

What access control model is used?

NC-Pass uses an access control model based on roles and application assignments. Users are assigned roles, and roles are granted access to specific VTAM applications. This allows administrators to control which applications users can access based on their job function.

Operations

What ongoing operational requirements exist?

Ongoing operational requirements for NC-Pass include monitoring the system for security events, performing regular maintenance tasks, and managing user access. This requires skilled personnel with expertise in z/OS, VTAM, and mainframe security.

What administrative interfaces are available?

NC-Pass provides administrative interfaces such as a command-line interface (CLI) and potentially a web-based console. These interfaces allow administrators to configure access rules, manage users, and monitor system activity.

How is user management handled?

User management in NC-Pass is typically handled through integration with existing security systems such as RACF, ACF2, or Top Secret. User accounts and roles are managed within these systems, and NC-Pass leverages this information for access control.

What are common implementation challenges?

Common implementation challenges for NC-Pass include integrating with existing security systems, configuring access rules to meet specific business requirements, and ensuring that the configuration does not disrupt existing VTAM applications. Thorough testing is essential.

Ready to Start Your Migration?

Download our comprehensive migration guide for NC-Pass or calculate your ROI.

Calculate ROI