Thigpen Enterprises z/OS zVSE/VSEn

Dino-Protect Modernization Guide

EncryptionFiles and Datasets (VSAM)

Dino-Protect is a encryption product by Thigpen Enterprises. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Dino-Protect offers a method for encrypting VSAM data within mainframe environments.

Consider Dino-Protect if you have existing applications that require VSAM data encryption to meet compliance or security requirements.

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 Dino-Protect do?

Dino-Protect provides subroutines that applications can call to encrypt VSAM data. It supports applications conforming to standard System/390 linkage, including those written in COBOL and PL/1. For z/VSE environments, it includes a BACKUP/RESTORE enhancement for encrypting VSAM backups.

Is this a system, application, or tool?

Dino-Protect is a set of subroutines that applications use to encrypt VSAM data. It is not a standalone application but rather middleware that extends the capabilities of existing applications.

What types of organizations use this?

Organizations that rely on VSAM data storage and require encryption for compliance or security purposes use Dino-Protect. This includes enterprises in industries such as finance, insurance, and government that operate on z/OS or z/VSE platforms.

When should we consider Dino-Protect?

Consider Dino-Protect when you need to encrypt VSAM data to meet regulatory requirements, protect sensitive information, or enhance overall data security. It is particularly useful when you have existing COBOL or PL/1 applications that need to encrypt VSAM data.

What are the alternatives to Dino-Protect?

Alternatives to Dino-Protect include other VSAM encryption products, hardware-based encryption solutions, or re-architecting applications to use different data storage methods with built-in encryption. Examples include IBM Data Facility Encryption (DFE) and solutions from other security vendors.

Technical

What infrastructure is required?

Dino-Protect requires a z/OS or z/VSE environment with VSAM datasets. It integrates with applications through standard System/390 linkage, so no specific subsystems are required.

For mainframe products: Does this run in an LPAR?

Dino-Protect runs within an LPAR on z/OS or z/VSE. It does not have specific dependencies on other subsystems beyond the base operating system and VSAM support.

Does this extend/enhance another product?

Dino-Protect enhances existing applications by providing encryption capabilities for VSAM data. It does not replace or depend on any specific application but rather extends their functionality.

How does it integrate with applications?

Dino-Protect uses standard System/390 linkage conventions for applications to call its subroutines. The specific encryption algorithms and key management mechanisms are part of the Dino-Protect implementation.

Business Value

How does this product provide business value?

Dino-Protect helps organizations protect sensitive VSAM data, ensuring compliance with data security regulations and reducing the risk of data breaches. By encrypting VSAM data, organizations can maintain data confidentiality and integrity.

What happens if we do not use this product?

Without Dino-Protect, organizations face the risk of exposing sensitive VSAM data, potentially leading to regulatory fines, reputational damage, and financial losses due to data breaches. Unencrypted VSAM data is vulnerable to unauthorized access and theft.

When is this product NOT a good fit?

Dino-Protect is a good fit when you need to encrypt VSAM data in existing COBOL or PL/1 applications without requiring extensive code changes. It is less suitable if you are migrating away from VSAM or using a different data storage technology.

Security

What authentication methods are supported?

Dino-Protect supports authentication methods available on the z/OS or z/VSE platform. It uses an access control model based on the underlying operating system's security mechanisms.

What encryption is used and where?

Dino-Protect encrypts VSAM data using industry-standard encryption algorithms. The specific algorithms used are part of the Dino-Protect implementation and can be configured based on security requirements.

What audit/logging capabilities exist?

Dino-Protect provides audit logging capabilities to track encryption and decryption activities. These logs can be integrated with security information and event management (SIEM) systems for monitoring and analysis.

Operations

How is this product typically deployed?

Dino-Protect is typically deployed on-premise within the z/OS or z/VSE environment. The implementation requires technical expertise in mainframe systems and VSAM data management.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring encryption activities, managing encryption keys, and ensuring the availability and performance of the Dino-Protect subroutines. Regular maintenance and updates are also necessary.

What are common implementation challenges?

Common implementation challenges include ensuring compatibility with existing applications, managing encryption keys securely, and minimizing performance impact on VSAM data access.

Ready to Start Your Migration?

Download our comprehensive migration guide for Dino-Protect or calculate your ROI.

Calculate ROI