CryptLib Modernization Guide
CryptLib is a application development product by XPS Software. Explore technical details, modernization strategies, and migration paths below.
Product Overview
CryptLib is a set of application programming interfaces (APIs) designed for z/OS and zVSE/VSEn environments.
CryptLib helps reduce the risk of data breaches and optimize storage costs.
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 CryptLib do?
CryptLib provides APIs for data encryption, decryption, compression, and uncompression. It enables applications to protect sensitive data and optimize storage on z/OS and zVSE/VSEn systems.
Is this a system, application, or tool?
CryptLib is a set of application programming interfaces (APIs). It is a framework that provides building blocks for developers to integrate encryption and compression functionality into their applications.
What types of organizations use this?
Organizations that handle sensitive data on z/OS or zVSE/VSEn platforms, such as financial institutions, healthcare providers, and government agencies, commonly use CryptLib. Any organization needing to secure data at rest or in transit on these platforms can benefit.
When should we consider CryptLib?
Consider using CryptLib when you need to add encryption or compression capabilities to applications running on z/OS or zVSE/VSEn. It is especially useful when compliance requirements mandate data protection.
What are the alternatives to CryptLib?
Alternatives to CryptLib include other encryption and compression libraries or hardware-based encryption solutions. Examples are IBM Integrated Cryptographic Service Facility (ICSF) and various open-source libraries.
Technical
What infrastructure is required?
CryptLib runs on z/OS and zVSE/VSEn operating systems. It requires the base operating system and a compatible development environment for application integration.
How is CryptLib deployed?
CryptLib is typically deployed on-premise, within the z/OS or zVSE/VSEn environment. It integrates directly into applications running in those environments.
What types of APIs does CryptLib expose?
CryptLib exposes native APIs for encryption and compression. These APIs can be called from applications written in languages such as COBOL, Assembler, and C.
What are some example API endpoint patterns?
While specific API endpoint patterns depend on the chosen functions, common operations include initialization, encryption, decryption, compression, and uncompression. Each operation has a corresponding API call with specific parameters.
Business Value
How does CryptLib provide business value?
CryptLib helps organizations meet compliance requirements by providing the tools to encrypt sensitive data. This reduces the risk of data breaches and associated financial and reputational damage.
How does CryptLib help reduce costs?
By compressing data, CryptLib can reduce storage costs and improve application performance. This is particularly beneficial for organizations dealing with large volumes of data.
What happens if an organization does not use CryptLib?
Without CryptLib, organizations would need to find alternative ways to encrypt and compress data, potentially using less efficient or less secure methods. This could lead to increased costs, higher risk, and compliance issues.
Security
What authentication methods are supported?
CryptLib supports various authentication methods depending on the underlying z/OS or zVSE/VSEn security infrastructure. This may include RACF, ACF2, or Top Secret.
How does CryptLib control access to data?
CryptLib leverages the access control mechanisms of the host operating system (z/OS or zVSE/VSEn). It integrates with existing security systems to control access to encryption keys and data.
What encryption algorithms are used?
CryptLib utilizes industry-standard encryption algorithms such as AES and DES. The specific algorithms used depend on the configuration and the requirements of the application.
What audit and logging capabilities exist?
CryptLib provides logging capabilities to track encryption and decryption activities. These logs can be used for auditing and compliance purposes.
Operations
What level of expertise is required to implement CryptLib?
Implementing CryptLib requires expertise in z/OS or zVSE/VSEn systems and application development. Familiarity with security concepts and encryption algorithms is also beneficial.
What are the ongoing operational requirements?
Ongoing operational requirements include monitoring the performance of encryption and compression operations, managing encryption keys, and ensuring the security of the CryptLib environment.
What are common implementation challenges?
Common implementation challenges include integrating CryptLib with existing applications, managing encryption keys securely, and ensuring compliance with relevant regulations.
Ready to Start Your Migration?
Download our comprehensive migration guide for CryptLib or calculate your ROI.