Redvers Consulting z/OS z/VM zVSE/VSEn

Redvers Encryption Device Modernization Guide

EncryptionApplication DevelopmentCOBOL

Redvers Encryption Device is a encryption product by Redvers Consulting. Explore technical details, modernization strategies, and migration paths below.

Product Overview

The Redvers Encryption Device provides AES encryption and decryption for COBOL applications running on z/OS, z/VM, and zVSE/VSEn.

Configuration, such as the AES key length, is performed by modifying the COBOL source code directly.

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 is the Redvers Encryption Device?

The Redvers Encryption Device provides AES encryption and decryption capabilities for COBOL applications running on z/OS, z/VM, and zVSE/VSEn. It consists of two COBOL subroutines: RCENCRYP for encryption and RCDECRYP for decryption.

How is the Redvers Encryption Device integrated into COBOL applications?

The device is distributed as COBOL source code, allowing direct integration into existing COBOL applications. No external services or specialized hardware are required.

What are the main functions of the Redvers Encryption Device?

The primary function is to encrypt and decrypt data using the AES algorithm. This protects sensitive data at rest and in transit within COBOL environments.

Technical

How does the Redvers Encryption Device expose its functionality?

The Redvers Encryption Device exposes its functionality through two COBOL subroutines: RCENCRYP and RCDECRYP. These subroutines are called directly from COBOL programs.

What is the syntax for the RCENCRYP and RCDECRYP subroutines?

The syntax for RCENCRYP is CALL 'RCENCRYP' USING INPUT-DATA, OUTPUT-DATA, KEY. The syntax for RCDECRYP is CALL 'RCDECRYP' USING INPUT-DATA, OUTPUT-DATA, KEY.

Does the Redvers Encryption Device use any specific communication protocols or ports?

The device operates directly within the COBOL application's memory space. There are no external communication protocols or ports involved.

Business Value

What business value does the Redvers Encryption Device provide?

The Redvers Encryption Device protects sensitive data processed by COBOL applications, ensuring compliance with data security regulations. It minimizes the risk of data breaches and unauthorized access.

How does the Redvers Encryption Device provide flexibility and control?

By providing COBOL source code, the device allows organizations to maintain control over their encryption processes and customize the implementation to meet specific requirements.

Security

What encryption algorithm does the Redvers Encryption Device use?

The Redvers Encryption Device utilizes the AES encryption algorithm, a widely recognized and robust encryption standard. The key length is configurable within the COBOL source code.

What authentication and access control mechanisms are used?

The device relies on the security mechanisms provided by the underlying z/OS, z/VM, or zVSE/VSEn operating system. It does not implement its own authentication or access control mechanisms.

What audit logging capabilities exist?

Audit logging capabilities depend on the logging facilities provided by the COBOL application and the underlying operating system. The Redvers Encryption Device itself does not generate specific audit logs.

Operations

How is the Redvers Encryption Device deployed?

The Redvers Encryption Device is deployed by including the RCENCRYP and RCDECRYP COBOL source code into the application's build process. No separate installation is required.

How are configuration parameters managed?

Configuration parameters, such as the AES key length, are modified directly within the COBOL source code. Recompilation is required after making changes.

What monitoring and logging capabilities exist?

Monitoring and logging depend on the capabilities of the COBOL application and the underlying operating system. The Redvers Encryption Device itself does not provide specific monitoring or logging features.

Ready to Start Your Migration?

Download our comprehensive migration guide for Redvers Encryption Device or calculate your ROI.

Calculate ROI