Rocket Software z/OS z/VM

SirSafe Modernization Guide

DatabasesSecurity

SirSafe is a databases product by Rocket Software. Explore technical details, modernization strategies, and migration paths below.

Product Overview

SirSafe is a security application designed to enhance the security of Model 204 databases running on z/OS and z/VM mainframe platforms.

Without SirSafe, organizations may face increased risks of unauthorized access, data breaches, and compliance violations.

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 SirSafe do?

SirSafe is a security product designed to enhance the security of Model 204 databases. It integrates with mainframe security products through the SAF interface to provide access control and auditing capabilities.

Is this a system, application, or tool?

SirSafe is primarily a security application that enhances the security features of the Model 204 database. It provides tools for access control, auditing, and integration with existing mainframe security systems.

What types of organizations use this?

Organizations that use Model 204 databases and require enhanced security measures are the best fit for SirSafe. These organizations are often in industries with strict compliance requirements, such as banking, finance, and government.

When should we consider SirSafe?

A company should consider using SirSafe when they need to improve the security posture of their Model 204 databases, especially when facing compliance requirements or needing to integrate with existing mainframe security products.

What are the alternatives to SirSafe?

Alternatives to SirSafe include other mainframe security products that offer similar access control and auditing features. Examples include CA Top Secret, IBM RACF, and Broadcom ACF2. The key difference is SirSafe's specific focus on enhancing Model 204 security.

Technical

What infrastructure is required?

SirSafe requires a mainframe environment running z/OS or z/VM, along with a Model 204 database. It integrates with existing mainframe security products using the SAF interface.

For mainframe products: Does this run in an LPAR?

SirSafe runs within an LPAR on z/OS or z/VM. It is dependent on the presence of a Model 204 database and integrates with mainframe security managers via SAF.

How does SirSafe enhance Model 204 security?

SirSafe enhances the security of Model 204 databases by providing features such as access control, auditing, and integration with mainframe security products. It leverages the SAF interface for seamless integration.

How does SirSafe integrate with mainframe security products?

SirSafe integrates with mainframe security products through the SAF interface. This allows it to leverage existing security policies and user authentication mechanisms.

Business Value

What is the business value of SirSafe?

SirSafe helps organizations protect their Model 204 databases from unauthorized access and data breaches. This reduces the risk of financial loss, reputational damage, and regulatory penalties.

How does SirSafe help with regulatory compliance?

By enhancing the security of Model 204 databases, SirSafe helps organizations comply with industry regulations and data privacy laws. This reduces the risk of non-compliance and associated penalties.

Does SirSafe improve operational efficiency?

SirSafe can improve operational efficiency by automating security tasks and providing centralized management of access controls. This reduces the workload on security administrators and improves overall security posture.

Security

What authentication methods are supported?

SirSafe uses the SAF interface to integrate with mainframe security products, which handle authentication. Specific authentication methods depend on the underlying security product (e.g., RACF, Top Secret, ACF2).

What access control model is used?

SirSafe likely uses a role-based access control (RBAC) model, where users are assigned roles with specific permissions to access Model 204 resources. The exact implementation depends on the configuration and integration with the mainframe security product.

What audit/logging capabilities exist?

SirSafe provides auditing and logging capabilities to track user access and security events within the Model 204 database. These logs can be used for security analysis, compliance reporting, and incident investigation.

Operations

How is SirSafe typically deployed?

SirSafe is typically deployed on-premise in a mainframe environment. It requires integration with existing mainframe security products and Model 204 databases.

What level of technical expertise is required to implement it?

Implementing SirSafe requires expertise in mainframe security, Model 204 databases, and the SAF interface. Ongoing operational requirements include monitoring security logs, managing access controls, and performing regular security audits.

What are common implementation challenges?

Common implementation challenges include ensuring compatibility with existing mainframe security products, configuring access controls to meet specific business requirements, and training staff on the new security procedures.

Ready to Start Your Migration?

Download our comprehensive migration guide for SirSafe or calculate your ROI.

Calculate ROI