FIS Fraud Navigator Modernization Guide

FIS Fraud Navigator is a component of the FIS Payments system designed to assist in early fraud protection. It operates within the z/OS USS environment.

FIS Fraud Navigator primarily uses configuration files within the z/OS USS environment for setup and customization. Specific file names and formats are detailed in the product documentation.

The system exposes APIs, potentially including REST, for integration with other systems. Specific endpoint patterns and method names are detailed in the API documentation.

FIS Fraud Navigator supports standard authentication methods such as LDAP, potentially Kerberos, and possibly multi-factor authentication depending on the configuration.

The system components include the Fraud Detection Engine, the Rules Engine, the Transaction Monitor, and the Reporting Module. These components communicate through internal APIs and messaging queues.

FIS Fraud Navigator likely uses a relational database such as Db2 on z/OS for storing transaction data, rules, and fraud event information.

The product uses standard protocols such as TCP/IP for network communication. Specific ports depend on the configuration and the components involved.

The system supports integration via REST APIs. Specific API endpoint patterns and method names are detailed in the API documentation.

FIS Fraud Navigator helps reduce financial losses due to fraud by providing early detection and prevention capabilities. It enables real-time monitoring and intervention.

By automating fraud detection, the system reduces the manual effort required to identify and investigate suspicious transactions, improving operational efficiency.

The system's reporting module provides insights into fraud trends and patterns, enabling better decision-making and strategy adjustments.

FIS Fraud Navigator supports authentication methods such as LDAP, Kerberos, and potentially SAML 2.0 for single sign-on capabilities.

The system uses a role-based access control (RBAC) model to manage user permissions and access to sensitive data and functions.

Encryption is used to protect sensitive data both in transit and at rest. Specific encryption algorithms are detailed in the security documentation.

The system provides audit logging capabilities to track user activities and system events, aiding in compliance and forensic analysis.

Administrative interfaces include a command-line interface (CLI) and potentially a web-based console for managing the system. Specific commands are detailed in the administration guide.

User management is handled through the administrative interface, allowing administrators to create, modify, and delete user accounts and assign roles.

Main configuration parameters include database connection settings, API endpoint configurations, rule definitions, and security settings. These are typically managed through configuration files.

The system provides monitoring and logging capabilities, allowing administrators to track system performance, detect issues, and analyze fraud events. Logs are typically stored in a dedicated directory on the z/OS USS.