SAS Fraud Management Modernization Guide
SAS Fraud Management is a administration product by SAS Institute. Explore technical details, modernization strategies, and migration paths below.
Product Overview
SAS Fraud Management is a real-time fraud scoring system designed for bank card authorization systems, developed in collaboration with HSBC.
The system exposes APIs for integration with authorization systems, potentially including REST or native APIs.
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 SAS Fraud Management?
SAS Fraud Management is a real-time fraud scoring system designed for bank card authorization systems. It leverages SAS OnDemand Scoring Engine and integrates with CICS and DB2 environments.
How does SAS Fraud Management integrate with existing systems?
The system integrates with CICS for transaction processing and DB2 for data storage. It uses the SAS OnDemand Scoring Engine for real-time scoring.
What are the main components of the system?
The system's architecture includes components such as the Scoring Engine, Data Integration Services, and a Rule Management Interface.
What authentication methods are supported?
SAS Fraud Management supports various authentication methods, including LDAP and potentially integration with other enterprise authentication systems.
Technical
What configuration files are used?
The system uses configuration files to define scoring rules, data mappings, and system parameters. These files are typically managed through a dedicated interface.
What types of APIs does it expose?
SAS Fraud Management exposes APIs for integration with authorization systems, potentially including REST or native APIs. Specific endpoint patterns depend on the implementation.
What protocols does it use for communication?
The system likely uses TCP/IP for communication between components. Specific port requirements depend on the configuration of CICS, DB2, and the SAS OnDemand Scoring Engine.
What are the main system components?
The main system components include the SAS OnDemand Scoring Engine, data integration services for connecting to DB2, and rule management interfaces.
Business Value
How does SAS Fraud Management provide business value?
SAS Fraud Management helps reduce fraud losses by providing real-time scoring of transactions. This enables banks to identify and prevent fraudulent activities before they occur.
How does it integrate with existing systems to maximize value?
By integrating with existing authorization systems, SAS Fraud Management minimizes disruption and allows for a seamless implementation.
How does the rule management interface benefit business users?
The system's rule management interface allows business users to easily update and maintain fraud detection rules, ensuring that the system remains effective against evolving fraud patterns.
Security
What authentication methods are supported?
SAS Fraud Management supports authentication methods such as LDAP, potentially with integration for multi-factor authentication depending on the configuration.
What access control model is used?
The system likely employs Role-Based Access Control (RBAC) to manage user permissions and access to sensitive data and functions.
What encryption is used and where?
Encryption is used to protect sensitive data both in transit and at rest. The specific encryption algorithms depend on the configuration of CICS, DB2, and the SAS OnDemand Scoring Engine.
What audit/logging capabilities exist?
SAS Fraud Management provides audit logging capabilities to track user activity and system events. These logs can be used for security monitoring and compliance purposes.
Operations
What administrative interfaces are available?
Administrative interfaces are available through a web console and potentially a command-line interface (CLI). The web console provides a user-friendly interface for managing the system, while the CLI allows for more advanced configuration and scripting.
How is user management handled?
User management is handled through the administrative interface, allowing administrators to create, modify, and delete user accounts and assign roles.
What monitoring/logging capabilities exist?
Monitoring and logging capabilities are provided through the SAS Environment Manager and standard logging mechanisms within CICS and DB2. These tools allow administrators to monitor system performance and identify potential issues.
What are the main configuration parameters?
Configuration parameters are managed through configuration files and the administrative interface. These parameters control various aspects of the system, such as scoring rules, data mappings, and system settings.
Ready to Start Your Migration?
Download our comprehensive migration guide for SAS Fraud Management or calculate your ROI.