Testing and Compliance

Overview

Our Test Environment Creation Utility (TECU) is a testing tool that facilitates rapid and focused testing of core banking systems. The tool creates a subset of the existing production or test environment while sanitizing the data to be in compliance with privacy and audit policies. In a test environment it is difficult to replicate the behavior of certain production accounts due to the interplay of many factors. Financial institutions overcome this difficulty by storing a complete copy of the production environment on the test system. The problem is then recreated and various solutions can be evaluated.

The gain in productivity is significant, both in terms of reducing test cycles as well as significantly reducing the requirement for disk space. By using less disk space, it is possible to have multiple scaled down environments coexisting in the test area. An online version of TECU is available which can be used to create smaller databases on a mirroredmachine. These smaller databases are created while maintaining application referential integrity.

TECU provides the ability to select a default number of customer records by customer type (personal/non-personal) or by customer segment such as:

• Checking
• Collateral
• Loan
• Time
• Savings
• Retirement
• Insurance
• Safe Deposit

Products

Rapid & focused testing, leading to better quality testing, shorter project durations and huge cost savings. Parallel dedicated testing environments saving time and cost.

• Customer privacy protectionThrough scrambling
• PCI Compliance for Credit Card Systems. (VPlus, Etc.)
• Less likelihood of appearing in the newspapers as a result of promoting poorly / untested software
• Creates the smaller database for the iSeries Core Banking / Cardbase system using a mapped object model on the generic TECU database.
• Scrambling & Optional PCI Compliance managed through file field level mapping and managed at customer level.

Overview

Our File Compare Utility is a reporting and testing tool that compares, tracks, and reports any changes to externally defined files on the IBM iseries, i.e. configuration file and security files. The capability exists to compare file settings between multiple environments thus minimizing the impact of any inadvertent changes in production. The tool can be used for pre-production validation prior to installing any software upgrades. The ability to add any file to be validated across multiple environments is inherent to the system. The option exists to include any of the financial institution’s customizations.

Work with Environment Library Lists

FCU defines the compare sequences. This allows for file extract definition from production if permitted per the financial institution policies. Up to a maximum of four environments may be compared by any one compare process.

Work with Common File List

FCU permits the financial institution to define files designated as configuration file or external files that need to be compared between environments. A standard Iist of core system files is provided. The capability exists for the financial institution to define its own files. The financial institution can activate and de-activate these files to track comparisons and changes.

Report Data

All file compare data is stored in internal formats on the iSeries. An API for data conversion is provided for the financial institution to convert data to generate internal reports. The data is held in an online repository for 50 calendar days and then moved to history. Data is purged from history after 12 months.

Products

• Value proposition to any bank using the product – Risk Mitigation, Audit & Compliance, Cost and Time savings
• Ability to monitor & track changes to critical files in production
• Auto update of changes from UAT to Production for implementation, upgrades and fix promotion
• Track changes to parameter / settings / common values in files within a single environment (ageing )
• Compare parameter / settings / common values between multiple environments – both dynamic and aged
• Eliminate inadvertent changes in production

Overview

How do you as a financial institution detect and stop fraud before it happens? The forensics of fraud management include tools such as MoadBus CIF Sentry. The CIF Sentry tool tracks all suspicious employee activity within the core banking system by tolerance level rules set by the bank and access to customer / account information. Every function that is accessed by any selected user to view or print any customer or account information is logged with all pertinent user details. This monitoring and logging is so extensive that even the summarized results from the work with customer and work with customer account screens that a user has been presented are logged, i.e. with user information and customer and account numbers.

Information from User Name, External ID, Internal ID, Workstation ID, Job Name, Job Number, IP address, System Timestamp, Internal System Date, Function Number, Application Number, CIF Number, and Account Number will be reported. Additional statistics that are provided calculate the number of customers and accounts a user has accessed on a daily basis. Any spike in activity beyond normal trends will help immediately flag potential suspicious activity. Inquiry functions by Customer/Account Number will provide a listing of all users who have accessed the customer information over a period of time in chronological order. There are multiple views provided with a subset feature by Customer/Account Number and Function/Username combination.

Reporting is provided for both daily and historical activity by customer and by account. The report lists (by user) any access to customer and account information. Similar reporting is provided by the user which lists the customer numbers and account numbers accessed by the user. The unusual activity report will provide a quick and easy method to spot any potential unwanted activity.

Products

Be in total control of the security of your bank

• ID Fraud Before it Happens
• Improve Security
• Track and Report Access to CIF
• Function, Screen, Account, User, Time/Date
• Unusual Activity Flagged and Reported
• Export to Data Warehouse