Department of Post –Anti-Money Laundering

Department of Post

Anti-Money Laundering Admin Guide

© Internal Page 1

Page 1 of 45
 Department of Post –Anti-Money Laundering

Confidential Information
The information provided in this document including information disclosed in discussions to be
conducted pursuant to this document is confidential to Infosys Technologies Limited and Department of
Posts. This document contains information and data that Infosys considers confidential and proprietary
(“Confidential Information”).

Confidential Information includes, but is not limited to, the following:

 Corporate Information about Infosys

 Project experiences and Client experiences provided to illustrate Infosys capability
 Human resources and skills information provided in response to request for the same
 Details of current and future services and products, research and any and all intellectual
property and rights of Infosys
DOP FSI program related information.

© Internal Page 2

Page 2 of 45
 Department of Post –Anti-Money Laundering

Contents
I. INTRODUCTION ................................................................................................................................ 4
II. SCENARIO ADMINISTRATOR ....................................................................................................... 4
A. SCENARIO ADMINISTRATOR INTRODUCTION ................................................................................. 4
B. LAUNCH SCENARIO ADMINISTRATOR ............................................................................................. 5
C. WORKING WITH SCENARIO ADMINISTRATOR ................................................................................ 8
1. CONFIGURING OF SCENARIO PARAMETERS .............................................................................. 13
2. ROUTING OF ALERTS .................................................................................................................. 18
III. WATCH LIST UPLOAD .............................................................................................................. 20
A. WATCH LIST UPLOAD INTRODUCTION .......................................................................................... 20
B. INTERNAL WATCH LIST ................................................................................................................... 21
C. EXTERNAL WATCH LIST .................................................................................................................. 23
IV. USER REATION .......................................................................................................................... 26
A. USER ROLES INTRODUCTION ......................................................................................................... 27
B. NEW USER CREATION ..................................................................................................................... 28
1. TO INVOKE SAS MANAGEMENT CONSOLE ................................................................................ 30
2. NEW USER CREATION ................................................................................................................. 35
C. SYNCHRONISATION OF USER ......................................................................................................... 43
V. APPENDIX ........................................................................................................................................ 44
A. Putty Usage..................................................................................................................................... 44

© Internal Page 3

Page 3 of 45
 Department of Post –Anti-Money Laundering

I. INTRODUCTION

AML Admin Guide describes how to configure and administer Anti-Money Laundering Application. The
document explains in handling of the Scenarios through Scenario Administrator, Addition of the Watch
Lists and user creations for accessing of AML application. The intended audience for this document is
the Admin team, The System admin should have basic understanding of AIX commands, access to AML
servers and some Database knowledge.

II. SCENARIO ADMINISTRATOR

A. SCENARIO ADMINISTRATOR INTRODUCTION

The Scenario Administrator is metadata-driven application that captures and stores configuration
information of scenarios, and advanced routing rules.

 Headers: User can specify the data or programs required to execute scenarios. Most of
the scenarios can use Anti-Money Laundering Application standard headers, Headers analyze
transactions and events at the account or party level. Standard headers are defined as those
that are auto-generated as part of the alert generation process based on the data fields that
they use. The Headers provide Structure for creation of the scenarios.
 Scenarios: User can specify information such as categorization, status, suppression, and
parameter values. By adjusting parameter values, User can strike a balance between catching
the most likely suspicious activity and reducing the number of false positives.
 Create and edit advanced routing rules: User can create advanced rules to specify alert
routing.
 Risk factors: Risk factors describe more common, less suspicious behavior, so when they are
matched, instead of generating alerts, they raise the risk rank for an entity that also matched a scenario.
 Risk factors cannot be converted to scenarios and scenarios cannot be converted to risk factors
because Converting a risk factor to a scenario will generate a lot more alerts because a risk factor
describes more common, less suspicious behavior. This can cause duplicate alerts.

© Internal Page 4

Page 4 of 45
 Department of Post –Anti-Money Laundering

B. LAUNCH SCENARIO ADMINISTRATOR

1. To Open Scenario Administrator user needs to have Xming or Xmanager installed to the
Windows system.

Xming/Xmanager is used to display AIX/LINUX GUI.

On Clicking Xming we get Xming in Show Hidden Icons and its version as: 0.0 or: 1.0

Note the version of the Xming by hovering over it.

Fig 1 Xming Version

2. Load the server required to be opened in putty.

NOTE:Only load the server IP and donot click open

© Internal Page 5

Page 5 of 45
 Department of Post –Anti-Money Laundering

Fig 2 IP Load to putty

3. Expand SSH and select X11, select the checkbox “Enable X11 Forwarding, provide the X
display location as “:0”(as discussed earlier) and click open.

© Internal Page 6

Page 6 of 45
 Department of Post –Anti-Money Laundering

Fig 3 Xming Version

4. Log into putty using the credentials. Navigate to the path using the command
cd /sasconf/Lev1/Applications/SASAntiMoneyLaundering/5.1/BusinessUnit/custom/config
List down all the files in the location using ls command. Now run ./sasaml.sh .Opens Scenario
Administrator

© Internal Page 7

Page 7 of 45
 Department of Post –Anti-Money Laundering

Fig 4 Scenario Administrator Command

C. WORKING WITH SCENARIO ADMINISTRATOR

User can edit or modify the existing scenarios.

1. Select radio button “create, edit and Test Scenarios and risk factors “ and click “Next” from
Scenario Administration: Main Window.

Fig 5 Scenario Administrator Main Window

© Internal Page 8

Page 8 of 45
 Department of Post –Anti-Money Laundering

3. Clicking on “Next” directs to below screen “SAS Scenario Administrator Scenario Main
“Window.
 Here the Scenarios are displayed by category.
 The Green flag represents the ACTIVE scenarios and Red flag represents the INACTIVE
scenarios.
4. To edit the existing scenarios click “EDIT”.

Fig 6 Active and Inactive Scenarios

© Internal Page 9

Page 9 of 45
 Department of Post –Anti-Money Laundering

Field Description
Description The long description of the selected scenario.
Owner The username of the person who registered
or edited the scenario.
Effective date The last created/edited date of the scenario.
Edit button Navigates to scenario properties window.
Delete button Deletes the selected scenario.
New Button Navigates to Create window.
Close Button Closes the Scenario Administrator Main
Window.
Table 1 Active and Inactive Scenarios Description

5. Clicking on “Edit” directs to “SAS Scenario Administration :Scenario Properties” Window

Fig 7 Scenario Administration Scenario Properties

© Internal Page 10

Page 10 of 45
 Department of Post –Anti-Money Laundering

Field Description
Name Displays the name of the scenario selected.
Version The Scenario Administrator increments the
version each time the scenario is modified.
Short Description The short description allows up to 100
characters and is used as the label in the
Available Scenarios box on the Scenario Main
window.
Long Description The long description allows up to 255
characters and is displayed on the Scenario
Main window as well as in the Investigation
UI.
Category Displays all the categories present in the
scenario main window and highlights the
category in which the scenario belongs.
Status The status can be either Active or Inactive.
Active scenarios are scheduled for execution
in the scenario code generation module;
inactive scenarios are not.
Risk Factor Y indicates that this is a risk factor. N
indicates that this is a scenario.

Product Type Product Type is always Anti Money

Laundering
Frequency The frequency at which this scenario is
executed. Valid values are Daily, Weekly, and
Monthly.
Suppression (Calendar Days) The default suppression duration for this
scenario. Each alert generated from this
scenario is suppressed for the number of
calendar (not business) days entered.
Replication (Business Days) The number of business days of transactions
that is replicated to the Knowledge Center.
By default this is set to the same value as the
number of business days that the scenario
considers.
TF Bayes Weight The terror financing Bayes weight is the
percentage of terror financing suspects that
would engage in the behavior described by
© Internal Page 11

Page 11 of 45
 Department of Post –Anti-Money Laundering

the scenario. If they all do it, the value should

be 10. If it is a rare terrorist financing
scheme, the value should be 1. To remove a
scenario from the risk ranking process, assign
a value of 0.
Valid values are 0 ≤ TF Bayes weight ≤ 10. The
default setting is 5.
ML Bayes Weight The money laundering Bayes weight is the
percentage of money laundering suspects
that would engage in the behavior described
by the scenario or risk factor. If they all do it,
the value should be 10. If it is a rare money
laundering scheme, the value should be 1
Execution Probability The probability that a scenario or risk factor
will be matched with respect to the other
scenarios and risk factors. Valid values are 0
< execution probability < 1. The default
setting is .005.
Configure Scenario This button will navigate to configure
scenario window where you select the
header, point to the source code and
configure the scenario.
Initial Routing This button will navigate to Routing Window
where you can specify how the alerts should
be routed.
Test This button will navigate to Test Window.
Table 2 Scenario Administration Scenario Properties Description

© Internal Page 12

Page 12 of 45
 Department of Post –Anti-Money Laundering

1. CONFIGURING OF SCENARIO PARAMETERS

1. Click on “Configure Scenario” Button displays “Scenario Administration: Scenario
Configuration”Window.
2. Setting parameter values, the type of dialog box that User finds depends on the
parameter type.
3. Select a Parameter and click “Set” opens the Parameter Definition Window .

Fig 8 Scenario Administrator Configure Window

Field Description
Scenario Location of the scenario code.
Parameter Box Parameters that have been defined in the
source code.
Parameter Name of the parameter selected in
Parameter Box.
Description Description of the selected parameter.

© Internal Page 13

Page 13 of 45
 Department of Post –Anti-Money Laundering

Type Defines the selected parameter is numeric or

character or constant in type.
Value Value assigned to respective parameter.
Set Helps changing the selected parameter.
Replace Changes the existing parameter value to the
changed parameter value
Add To add new parameters to the source code.
Remove To Remove a selected parameter
Remove all To Remove all the parameters
Set To set or change the parameter values
Table 3 Scenario Administrator Configure Window Description

a) NUMERIC OR CHARACTER TYPE WINDOW

Fig 9 Numeric or Character Type Window

 Clicking on “Set” opens the below window for the selected parameter.
 Numeric and character radio buttons are used to find the entered values are numeric or
character list.

© Internal Page 14

Page 14 of 45
 Department of Post –Anti-Money Laundering

Fig 10 editing the parameter value Window

Field Description
Add To add a value
Rh Remove the Remove Remove the selected value
Remove all Removes all the values
Table 4 editing the parameter value Window Description

© Internal Page 15

Page 15 of 45
 Department of Post –Anti-Money Laundering

b) CHARACTER CONSTANT TYPE WINDOW

Fig 11 Character Constant Window

 Clicking Set Character value can be specified or edited in the below window.

Fig 12 Character Constant editing Window

© Internal Page 16

Page 16 of 45
 Department of Post –Anti-Money Laundering

c) NUMERIC CONSTANT

Fig 13 Numeric Constant Window

 Numeric value can be specified or edited in the below window.

Fig 14 Numeric Constant Editing Window

4. After setting or editing the required values the Replace button has to be clicked for the
replacement of the new values to the source code.
Note: Each time the value is changed the Replace button has to be clicked.

© Internal Page 17

Page 17 of 45
 Department of Post –Anti-Money Laundering

2. ROUTING OF ALERTS
 Use the Routing window to route the alert generated to required users or groups.
 Selecting a routing rule group in the Advanced Route box routs alerts generated by this
scenario to the users or groups as specified in that rule group. All other alerts are routed as
described in the Default Route box.
 If Advanced Route is set to none, then all alerts for this scenario are routed as specified
in the Default Route box. Our all alerts are set to none.
 The alerts can be routed to a particular group or individual.

Fig 15 Routing Alert Window

© Internal Page 18

Page 18 of 45
 Department of Post –Anti-Money Laundering

Fig 16 Routing Window

© Internal Page 19

Page 19 of 45
 Department of Post –Anti-Money Laundering

 On selecting individual we can route the alerts to the user created individually

Fig 17 initial Routing Window

III. WATCH LIST UPLOAD

A. WATCH LIST UPLOAD INTRODUCTION

A watch list is a set of individuals and organizations that have been considered as at risk for
money laundering or terrorist financing activity. We can choose to obtain watch lists from
WATCH LIST Providers globally or we might create its own watch lists.

Watch lists added in our systems are

1. External Watch lists (Specially Designated Nationals List (OFAC (Office of Foreign Assets
Control))
2. Internal Watch Lists

© Internal Page 20

Page 20 of 45
 Department of Post –Anti-Money Laundering

SAS Anti-Money Laundering provides scenarios that, when activated, generate alerts when a
name in your customer database matches a name on a watch list. It provides code that extracts,
transforms, and loads watch list data for the watch lists
Watch lists can be added at any time and it does not require any restart of SAS Services.

B. INTERNAL WATCH LIST

Bank can select some customers who are identified as fraudulent or have to be monitored
carefully for irregular financial activity can be added to internal watch lists.

Steps to Load Internal Watch Lists.

1. Make an entry of the fraudulent customer into Excel in path /sasaml/externalfiles/

WATCHLIST.xlsx

WATCHLIST.xlsx

2. Through putty navigate to /sasaml/batchfiles and execute ./WATCHLIST.sh Watch list logs
path /sasaml/logs e.g. (Watchlist_2016.08.23_10.49.56.log).
(Refer APPENDIX for opening putty sessions)

© Internal Page 21

Page 21 of 45
 Department of Post –Anti-Money Laundering

Fig 18 Internal Watch List

3. User can find the internal Watch list updated the UI.
Navigate to “query” Tab Select Watch List sub tab. Provide desire Name of Watch List as
“INTL”. Click “Show Matching” button to see the internal watch list.

Fig 19 Internal Watch List UI

© Internal Page 22

Page 22 of 45
 Department of Post –Anti-Money Laundering

4. Clicking on “Show Matching” displays the below screen of internal Watch List.

Fig 20 Internal Watch list display

C. EXTERNAL WATCH LIST

We can have any number of external watch list added as recommended by the bank. At present
we have OFAC Watch list added into external Watch lists.

Watch List Name Value: OFAC (Specially Designed Nationals list)

Steps to Load External Watch Lists.

1. OFAC Watch list data is to be downloaded from http://www.treasury.gov/ofac/downloads
Download sdn.csv, add.csv, alt.csv from the above link.

Fig 21 OFAC CSV Files

The CSV List data consists of three separate files:

a. The main SDN data file which contains primary entity names.
b. The ADD data file which includes entity location information.
c. The ALT data file containing alternate identities.

© Internal Page 23

Page 23 of 45
 Department of Post –Anti-Money Laundering

1. Place the csv files in /sasaml/externalfiles.

2. Through putty navigate to/sasaml/batchfiles and execute ./WATCHLIST_OFAC.sh. The
logs are generated in /sasaml/logs e.g. (wl_ofac_2016.02.05_13.27.49.log).
(Refer APPENDIX A)Putty usage for opening putty sessions)

Fig 22 External Watch List

Watch List Name Value Watch List

DFAT Consolidated List

HMT Consolidated List of Financial Sanctions

Targets
EUFS Consolidated List of Persons, Groups, and
Entities Subject to EU Financial Sanctions
NBCI Designated Terrorist Entities

© Internal Page 24

Page 24 of 45
 Department of Post –Anti-Money Laundering

DWJN Dow Jones Watch list

OSFI Terrorism Financing Lists of Names
UNSC The Consolidated List
WCHK World-Check Data-Files

Table 5 Watch List Names

3. User can find the external Watch list updated the UI.
Navigate to “query” Tab Select Watch List sub tab. Provide desire Name of Watch List
as “OFAC”. Click “Show Matching” button to view the external watch list.

Fig 23 External Watch List UI

© Internal Page 25

Page 25 of 45
 Department of Post –Anti-Money Laundering

4. Clicking on “Show Matching” displays the below screen of internal Watch List.

Fig 24 External Watch List UI Display

IV. USER REATION

Users and groups of users are defined in AML application to provide a means of routing alerts, cases, and
risk assessments and determining user permissions within the Investigation UI.

A user is an individual person or service identity.

A group is a set of users. Groups are created to simplify security management as follows:

• It is more efficient to assign permissions to groups than to individual users and manage role
membership by assigning groups to roles instead of assigning users directly to roles.

A role manages the availability of application features such as menu items. An application
feature that is under role-based management is called capability. Anyone who is a member of a
role has all of that role's capabilities.

• Roles determine which user interface elements (such as menu items or plug-ins) user can see
when uses an application.

• Roles and groups serve distinct purposes. User cannot assign permissions to a role or
capabilities to a group.

© Internal Page 26

Page 26 of 45
 Department of Post –Anti-Money Laundering

• Capabilities are always additive. Assigning someone to a role never reduces what that user can
do.

A. USER ROLES INTRODUCTION

There are three pre-defined roles for AML in DOP . As Below

a) System Admin
b) principal officer
c) Circle Managers

Roles in DoP Activities

System Admin Manage Users and assign different
capabilities to User
Access to Alerts tabs. View and take all types
of action possible like routing, suppress,
closed etc. on alerts.

Compliance Access to Query Tab to query AML system on

officer(principal officer)
Circle Managers
every available data present under query tab
Access to Summary to run different aml
provided reports
Access to Reports Tab and generate CTR/STR
as well as all other reports
Access to Alerts tab. View and take all types
of actions possible on alerts.
Take relevant actions on alerts routed to
individuals and close/suppress them
Access to Query Tab to query AML system on
every available data present under query tab
Ability to reactivate any closed and
suppressed alert

Access to Reports Tab and generate

exceptional reports and watch list insertion
Table 6 DOP Roles

© Internal Page 27

Page 27 of 45
 Department of Post –Anti-Money Laundering

System admin can create users, Manage Users and assign different capabilities to User. System
Admin can manage users using SAS Management Console.

Fig 25 Management Console

B. NEW USER CREATION

An individual SAS identity is established by coordination between two sets of identity

information:

• In an external system, a user account

© Internal Page 28

Page 28 of 45
 Department of Post –Anti-Money Laundering

• In the metadata, a user definition that includes a copy of the external account ID

To make new user, system admin need to following steps:

1.OS level user to be created.
2.Metadata user to be created using Management Console
3.Syncronisation between User and Metadata.
In Order to create a new user first OS level user has to be created.
a) Firstly, at UNIX level (OS level), Admin needs to create a UNIX level user.
b) Unix Team (DOP_IMS_AIX) has to be contacted for creating of the user
Requirement of UNIX Team :
1. User name (maximum eight characters can be alphanumeric)
2.Access Right Form to be atached PFB a Sample access rights form to be attached.

Access Rights
Form_New_UP_BIH_WB.doc

c) The newly created users will be added in the /home directory as shown below. User
created will have a separate username and password. Try logging into putty with the new
username and password provided and by default putty prompts for change of password. Change
the password and note down the new password for the username which will be used in forth
coming steps.

NOTE: User name can be maximum 8letters

© Internal Page 29

Page 29 of 45
 Department of Post –Anti-Money Laundering

Fig 26 OS Level Users

1. TO INVOKE SAS MANAGEMENT CONSOLE

1. Open SAS Management Console from Start Menu.

2. Create a new connection profile for the user to be logged in or if the user is already
registered select Open an existing connection profile.

© Internal Page 30

Page 30 of 45
 Department of Post –Anti-Money Laundering

Fig 27 New Connection in SAS Management Console

3. Connection Profile Wizard appears and click Next

Fig 28 Connection Profile Wizard

© Internal Page 31

Page 31 of 45
 Department of Post –Anti-Money Laundering

4. Provide any relevant name to the connection.

Fig 29 New Connection Name

© Internal Page 32

Page 32 of 45
 Department of Post –Anti-Money Laundering

5. Provide the HOSTNAME in Machine column

Port:8561
User ID:Same as OS level username
Password:Same as OS level password
Note:Username and password are case sensitive

click Next to navigate to next window.

Fig 30 Details of New Connection

6. Click “Finish” to enter to the connection newly created.

© Internal Page 33

Page 33 of 45
 Department of Post –Anti-Money Laundering

Fig 31 Completion of new Profile

Note:The above steps for creating a new profile would only be followed only once for registering
the admin user.Successive logins the Admin user can be selected from “Open an existing profile”

7. System admin can create users by using the SAS Management Console.
In SAS Management Console, Admin need to create the same user as created in UNIX box as
described earlier in the document.

© Internal Page 34

Page 34 of 45
 Department of Post –Anti-Money Laundering

2. NEW USER CREATION

The following steps need to be performed to create user in SAS Management Console
1. Login into the SAS Management Console using SAS Admin User Id

Fig 32 Login as Admin User

2. Navigate to User ManagerNewUser

© Internal Page 35

Page 35 of 45
 Department of Post –Anti-Money Laundering

Fig 33 Create New User

3. Enter the necessary details.

Name:Same as OS level user created and is case sensitive.
Display name:any name related to the user.
Job Title:designation of the user.
Description:A short description about the user.
Email:click on New and Email of the user to be entered. Type of EmailID is not specific it
can be either work or home.

© Internal Page 36

Page 36 of 45
 Department of Post –Anti-Money Laundering

Fig 34 User Details

NOTE:Email and Display name cannot be empty

Different Groups and Roles has to be assigned to different users depeding upon their roles and
capabilities.
1.Principal Officer
2.Circle Manager

© Internal Page 37

Page 37 of 45
 Department of Post –Anti-Money Laundering

Principal Officer:

Select Groups and Roles tab .Assign the below groups and roles to the Principal officer.

Fig 35 Principal Officer Role

© Internal Page 38

Page 38 of 45
 Department of Post –Anti-Money Laundering

Circle Manager:

Select Groups and Roles tab .Assign the below groups and roles to the Circle Manager.

Fig 36 Circle Manager Role

4. Select Accounts tab and provide authentication details clicking on New.

User Id:Same as OS Level User and its OS Level.
Password:Same as OS level Password.
Authentication Domain is DefaultAuth and Click OK
Note:The Username and Password are case sensitive

© Internal Page 39

Page 39 of 45
 Department of Post –Anti-Money Laundering

Fig 37 Credentials

© Internal Page 40

Page 40 of 45
 Department of Post –Anti-Money Laundering

Fig 38 Credentials Updated

© Internal Page 41

Page 41 of 45
 Department of Post –Anti-Money Laundering

5. Authorisation tab need not require any modification.

Fig 39 Authorization Tab

© Internal Page 42

Page 42 of 45
 Department of Post –Anti-Money Laundering

C. SYNCHRONISATION OF USER

After user creation, System Admin need to execute the amlusersync

code(aml_omr_sync_users.sas)

The process to execute this code is to execute the AMLSYNC.sh file present at
/sasaml/batchfiles.

Fig 40 Executing AMLSYNC.sh

System Admin is basically one of the system administrator from support team who has access to
SAS Management Console.

System Admin should have authority to get the OS level users created by UNIX admin and also
have authority for amlsync code execution when needed.

Note:Donot try copy pasting the Usernames or email IDs Some times it gives error while running
the AMLSYNC.sh.

© Internal Page 43

Page 43 of 45
 Department of Post –Anti-Money Laundering

V. APPENDIX
A. Putty Usage

Steps to open the AML server using Putty.

1. Provide the Server IP in the Host Name required to be opened and click “Open”.

Fig 41 Putty

© Internal Page 44

Page 44 of 45
 Department of Post –Anti-Money Laundering

4. Provide the Username and Password Login

Fig 42 Putty Login

© Internal Page 45

Page 45 of 45