3.1 What's New in Behavior Detection 8.1.2.11.0

New, changed, and deprecated features of Oracle Behavior Detection are described, with pointers to additional information.

Topics:

The following sections list the new features included in this release:

Anti Money Laundering

The following table describes AML-related new features/enhancements for OFS Behavior Detection Release 8.1.2.11.0:

Feature Description
Automated Audit Log On top of our existing mechanism that captures changes in thresholds, clients can now use an automatic audit log mechanism to record when a change in scenario implementation is loaded to the system. This automatically captures the following elements:
  • Date and Timestamp
  • Scenario ID
  • Scenario Name
  • Scenario XML (including scenario logic and thresholds)
Alert Suppression API Enhancement The enhancement supports additional displays in ECM about alert suppression rules.

Know Your Customer

The following table describes KYC-related new features and enhancements for OFS Behavior Detection Release 8.1.2.11.0:

Feature Description
Internal Watchlist Screening feature support for KYC Onboarding
  • The KYC application now supports internal watchlist screening as part of KYC real-time Onboarding requests. Clients can now use either EDQ or Internal watch list screening as part of the onboarding risk assessment process. Note that Watch list rule is already available as a risk parameter that can be used in scoring model namely Algorithmic scoring and business check.
  • The KYC application also supports watch list disposition feature for internal watch list matches as part of KYC Onboarding case investigation.
Data Model Changes COLUMN SIZE V_DOC_REF_NO AND V_DOCUMENT_ID FIELDS – Length of these 2 fields have been increased from 20 to 100 chars as part of KYC processing tables (CUST_ID_DOC_PRCSNG, CUST_ID_DOC_SNAPHSOT). These changes are in sync with stage data ingestion tables.
KYC Onboarding Case Enhancements For every watchlist match record, a new pop has been added to display all the watch list data attributes from external source list (like World check, Dow Jones etc.) for that respective watchlist record id. This feature helps KYC investigator view all the watchlist attributes for the given watchlist record in addition to those that are part of watchlist match.
KYC Admin UI Enhancements As part of KYC Configuration UI named “Risk Score for Parameter/Rule Value”, a new search criteria “Customer Type” has been added. This helps admin user to search the records by various customer types namely: IND, FIN and ORG.
Accelerated Re-review (ARR) based assessment for delta watchlist Changes A new task has been added “Get_Changes_In_Watchlist_Data” under batch “Load Customer Match Data from Oracle CS” which compares the customer watchlist matches for current batch against the previous batch run. All the customers who are not part of watchlist matches for current batch will be picked up for ARR based risk assessment.

Background: Say a customer is in a private watchlist marked as PEP on Day 1. The customer is picked up for KYC risk assessment and turns out to be high risk customer on day 1. On day 2, the customer is no longer a PEP and hence removed from the private watchlist. The customer should be risk assessed as Low risk on day 2. So, this task will help risk assess all those customers again as part of next batch run.

Other Noteworthy Changes

Note:

As of now, Behavior Detection 8.1.2.11.0 supports HTTPS 1.1 and does not support HTTPS 2.0.

Scenario Wizard is decommissioned with the 8.1.2.6.0 release. In the Scenario Wizard folder of the 8129 Installer Package, the associated configuration files are deleted. Due to deletion constraints, the Scenario Wizard folder can still be seen at path <$FIC_HOME/ficweb>. This will be removed in next major installer release.

If you are upgrading from 8.1.2.5.0 or an older version, Scenario Wizard will still remain in the deployed area. Since Scenario Wizard is no longer supported from 8.1.2.6.0, you must delete the Scenario Wizard war and jar files by following these steps:
  1. Navigate to: #deployed_area/SMLiteWeb and delete SMLiteWeb.war
  2. Navigate to: #deployed_area/SMLiteWeb/WEB-INF/lib and delete all the jar files
  3. Navigate to: #deployed_area/SMLiteWeb/lib and delete all the jar files