FILEGARD Modernization Guide
FILEGARD is a encryption product by Applied Software. Explore technical details, modernization strategies, and migration paths below.
Product Overview
FILEGARD is a software application designed to encrypt and decrypt datasets on z/OS mainframe systems.
It typically operates within an LPAR and integrates with z/OS security subsystems like RACF, ACF2, or 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 FILEGARD do?
FILEGARD is a software product that encrypts and decrypts datasets on z/OS systems. It protects sensitive data at rest, ensuring that only authorized users and applications can access it. This helps organizations meet compliance requirements and prevent data breaches.
Is this a system, application, or tool?
FILEGARD is an application designed to run on z/OS mainframe systems. It provides a set of tools and functions for encrypting and decrypting datasets, integrating with existing security systems and access controls.
What types of organizations use this?
Organizations that handle sensitive data on z/OS mainframes, such as financial institutions, healthcare providers, and government agencies, commonly use FILEGARD. These organizations need to protect data at rest to comply with regulations and prevent unauthorized access.
When should we consider FILEGARD?
A company should consider using FILEGARD when it needs to encrypt sensitive data stored in z/OS datasets to meet compliance requirements, protect against internal and external threats, and ensure data privacy. It is particularly relevant when dealing with personally identifiable information (PII) or other regulated data.
What are the alternatives to FILEGARD?
Alternatives to FILEGARD include Data-Crypt and SecureZIP for z/OS. These products offer similar dataset encryption capabilities for z/OS environments. The choice depends on specific requirements, integration needs, and existing security infrastructure.
Technical
What infrastructure is required?
FILEGARD runs on z/OS and requires a compatible mainframe environment. It typically operates within an LPAR and integrates with z/OS security subsystems. No other specific products are explicitly required, but it enhances existing security measures.
How is FILEGARD deployed?
FILEGARD is deployed on-premise within the z/OS environment. It requires technical expertise in z/OS systems and security administration for implementation and configuration. The deployment process involves installing the software, configuring encryption policies, and integrating with existing security systems.
How does FILEGARD integrate with existing security systems?
FILEGARD integrates with z/OS security systems such as RACF, ACF2, or Top Secret for authentication and access control. It uses APIs and interfaces to interact with these systems, ensuring that only authorized users and applications can access encrypted datasets.
What are the main components of FILEGARD?
The main components of FILEGARD include the encryption engine, key management system, and administrative interface. These components work together to encrypt and decrypt datasets, manage encryption keys, and provide administrative control over the encryption process.
Business Value
How does FILEGARD provide business value?
FILEGARD helps organizations protect sensitive data at rest, reducing the risk of data breaches and compliance violations. By encrypting datasets, it ensures that only authorized users and applications can access the data, enhancing data privacy and security.
What happens if an organization does not use FILEGARD?
Without FILEGARD, organizations face a higher risk of data breaches and compliance violations. Sensitive data stored in z/OS datasets could be accessed by unauthorized users, leading to financial losses, reputational damage, and legal penalties.
How does FILEGARD simplify data protection?
FILEGARD offers a centralized solution for managing dataset encryption across the z/OS environment. This simplifies the encryption process, reduces administrative overhead, and ensures consistent application of encryption policies. It also provides auditing and reporting capabilities to track encryption activities and demonstrate compliance.
Security
What authentication methods are supported?
FILEGARD supports various authentication methods, including integration with z/OS security systems like RACF, ACF2, and Top Secret. It uses these systems to verify user identities and control access to encrypted datasets.
What access control model is used?
FILEGARD uses an access control model based on the z/OS security system in place (RACF, ACF2, or Top Secret). It leverages the existing access control lists (ACLs) and security policies to determine which users and applications have access to encrypted datasets.
What encryption is used and where?
FILEGARD uses encryption algorithms to protect data at rest. The specific encryption algorithms used may vary, but commonly include AES (Advanced Encryption Standard). Encryption is applied to datasets stored on z/OS systems.
What audit/logging capabilities exist?
FILEGARD provides auditing and logging capabilities to track encryption activities, access attempts, and administrative actions. These logs can be used to monitor security events, detect unauthorized access, and demonstrate compliance with regulatory requirements.
Operations
What ongoing operational requirements exist?
Ongoing operational requirements for FILEGARD include monitoring encryption activities, managing encryption keys, and performing regular maintenance tasks. This requires skilled z/OS system programmers and security administrators.
What administrative interfaces are available?
FILEGARD provides administrative interfaces, including CLIs and potentially GUIs, for managing encryption policies, monitoring system status, and generating reports. These interfaces allow administrators to configure the system, monitor its performance, and troubleshoot issues.
What are common implementation challenges?
Common implementation challenges for FILEGARD include integrating with existing security systems, configuring encryption policies to meet specific requirements, and ensuring minimal performance impact on z/OS systems. Proper planning and testing are essential for a successful implementation.
Ready to Start Your Migration?
Download our comprehensive migration guide for FILEGARD or calculate your ROI.