Cheque Book Management System
Cheque Book Management System
Cheque Book Management System
Version: 1.0
2019
Contact Information
Data Processing & IT System Management, IFIC Bank Limited, Head Office,
IFIC Tower, 61, Purana Paltan, Dhaka-1000, Bangladesh.
Table of Contents
Introduction:........................................................................................................................................................... 4
Functionality: .......................................................................................................................................................... 5
Type of Users:...................................................................................................................................................... 5
Functionality as per user role: .............................................................................................................................. 5
Administrator: ..................................................................................................................................................... 6
Branch Users ....................................................................................................................................................... 7
Service and Estate ............................................................................................................................................... 7
Security features:.................................................................................................................................................... 8
Authentication:.................................................................................................................................................... 8
Authorization: ..................................................................................................................................................... 8
Encryption: .......................................................................................................................................................... 8
Application activity logging: ................................................................................................................................. 8
User Specific Data Sources: .................................................................................................................................. 8
Web application firewall (if webapp): .................................................................................................................. 8
Application Security Testing:................................................................................................................................ 8
Interface requirements with other systems: ........................................................................................................... 9
Three types of interface can be defined ............................................................................................................... 9
The stages involved in identifying the interface requirements are: ...................................................................... 9
System Documentation: ....................................................................................................................................... 10
Installation Manual:.............................................................................................................................................. 11
User Manual: ........................................................................................................................................................ 12
Administrator (super) ........................................................................................................................................ 12
Menu: ............................................................................................................................................................ 12
Manage Service: ............................................................................................................................................ 13
Manage Vendor: ............................................................................................................................................ 15
Manage Branch.............................................................................................................................................. 16
Manage User ................................................................................................................................................. 18
Manager Account Type .................................................................................................................................. 22
Manage Prefix ............................................................................................................................................... 24
Manage Role.................................................................................................................................................. 25
Branch User ....................................................................................................................................................... 29
But it needs an administrator to manage Service, Vendor, Branch, User, Account Type, Prefix, and Roles
assigned.
The Cheque Book Management System displays different menu options to different users based on their
role.
10 Check Book Requests : Checker checks the Cheque Book Request Branch User/ Service
and Estate
12 Generate Report By : Generate cheque book reports by vendor Service and Estate
vendor
15 Bundle wise Cheque : Ensures after receiving Cheque books Service and Estate
Books
Ensures delivered from Support Service.
16 Cheque Books at Support : Service and Estate
Service
Activates the cheque books with Account
17 Contact Center : Number. Contact Center
Administrator:
Administrator can manage Service, Vendor, Branch, User, Account Type, Prefix, and Roles assigned.
Menu options for administrator are:
Manage Service: Here admin can ‘Add, Edit or Delete a Service’. To do that you have to provide
the 'Service Name' and 'Service Path'. Description of the service is also needed. Next step is to
choose if the status will be hidden or not and its security level. Furthermore admin can do the
Activation and add 'Account Type', 'Branch', 'Prefix', 'Request', 'Role', 'Service' and 'User'.
Manage Vendor: To add a vendor, you have to provide 'Vendor’s Name', 'Address' and 'Status'.
The page will also portrait a list of Vendors. Admin can also choose the number of entries that
will be displayed on this page. 'Vendor Search' is another properties of Mange Vendor.
Manage Branch: Again admin can ‘Add, Edit or Delete a Branch’. In that case, you have to
provide ‘Branch Name’, ‘Branch Code’ and ‘Description’. The page also portrays a list of Branches
with their Branch code, Name and Routing number. Admin can also choose the number of
entries that will be displayed on this page too. ‘Search’ is another properties of Mange Branch,
through which admin can search for any branch.
Manage User: Admin can ‘Add, Edit or Delete a User’. To Add a user, you have to provide the
‘User ID’, ‘User Name’, ’Branch Code’, ’Branch Name’, ‘Branch Mnmo’, ‘Email’, ‘User Type’ and
their ‘Roles Assigned.’. The Manage User page portraits a list of Users along with their ID, Name
and Current Location. ‘Search User ' is another properties of 'Manage User'
Manager Account Type: In Manager Account Type admin can ‘Add and Edit Account Type’. To
do that admin has to provide ‘Product’, ‘Account Type’ and ‘BB Transaction Code’. The page also
portrays a list of Account type with their BB Transaction Code. Admin can also choose the
number of entries that will be displayed on this page. 'Search' is another properties of this page
to search for an Account Type.
Manage Prefix: Similarly admin can ‘Add and Edit a Prefix’ here. To add a prefix admin has to
provide ‘Prefix’, ‘Product’, ‘Vendor’, ‘First Serial’, ‘Last Serial’ and ‘Sequence’. This page displays
list of Prefix with their respective ‘Product’, ‘Vendor’, ‘Sequence’ and ‘Status’. The number of
Manage Role: Admin can ‘Add, Edit and Delete, Role’ of a User here. To add a role admin has to
provide ‘Role name’, ‘Description’, ‘Security level’ and ‘Assigned services to the user’. This page
shows a list of Role with description along with an option ‘Actions’ that can be done on it.
Branch Users
Maker makes a Cheque Book request and then Checker checks the request.
Add New Request: Maker makes a chequebook request from here. To make a request maker
has to provide the ‘Account Number’ which will fetch all the necessary information of the
Customer. Maker has to provide some additional information like ‘Printing Name’, Deliver
Branch’, Cheque Book Leaf’, ‘No, of Book’, ‘Amount per leaf’ and whether it is ‘Urgent’ or not.
Check Book Requests: Checker checks the Cheque Book Request and accept them.
Authorization:
A. Application Access as per user role: Control application access on a per-user role, or
per-user basis. This typically includes a role-based menuing system, which displays
different menu options to different users based on their role.
B. Row-level (or multi-tenant) security: Multiple users can access the same
application, but only view the data they’re authorized to see.
Encryption:
After a user has been authenticated and is using the application, other security measures such as
Encryption can protect sensitive data from being seen or even used by a cybercriminal.
MS SQL Server
Database name
MS SQL Server
Database version
Database OS Windows
B. Configure Application
I. Create iSereis ODBC
II. Upload the application in the server as per the IIS configuration
III. Create Database and place the database information in the file web.config file.
Menu:
Log in with the referred Uniform Resource Locator (URL) into the application. The following
screen will appear. That is you have logged in as ‘Super Admin’. This screen shows all the menu
options based on ‘Super admin’s’ role.
Add a Service
To add a Service provide ‘Service Name' and 'Service Path' and ‘Description’. Then choose ‘Hidden’ and
‘Security Level’.
Delete Service
Go to ‘Mange Service’ from Menu, then click on ‘Actions’ beside a respective service and choose Delete to
delete a service.
Add Vendor:
To add a Vendor, provide ‘Name’, ‘Address’ and choose ‘Status’. Then click on add.
Add Branch
To add a Branch, provide ‘Branch Name’, ‘Branch Code’ and ‘Description’. Then click on add.
Delete Branch
Go to ‘Mange Branch’ from Menu, then click on ‘Actions’ beside a respective branch and choose Delete to
delete a service
Add Prefix
To add an Prefix, provide all the information that appears on the screen. Then click on add.
Manage Role
Click on ‘Mange Role’ from Menu, this screen will appear. Click on ‘Add’ to add a Role.
Courier Acknowledgement
Acknowledgement Files from Courier Service are uploaded from here.
The system administrator should document any actual emergency access for later audit & review.
Typically, a special audit trail is created to monitor such access. Standard access controls should
be established with sufficient rules to minimize the number of times break–the–glass needs to
occur.
Scope
An emergency access solution should be used only when normal processes are insufficient
Examples of situations when ‘break glass’ emergency access might be necessary:
Account problems:
o Forgotten Username/Password
o Locked Password
o No User Account
Authentication problems:
o Central Authentication System failure
o Smart Card or biometrics reader failure
Note: In cases where the authentication system fails, there should be an alternate
authentication mechanism such as username/password.
Authorization problems:
o An emergency situation thrusts an individual into a role where s/he lacks sufficient
access rights
Pre-staging Accounts
Emergency Accounts should be created in advance to allow careful thought to go into the access
controls and audit trails associated with them. The following factors should be considered:
Note: Ensure that the individuals who create the accounts are not the ones reviewing the
audit trails since this can be a source of abuse.
The ‘break glass’ accounts and distribution procedures should be documented and tested
as part of implementation.
Distributing Accounts
Pre–staged accounts need to be carefully managed to provide timely access when needed Some
distribution possibilities for break–glass emergency accounts include the following:
Kept behind glass in a cabinet, where access to the accounts requires literally breaking
the glass
Maintained within sealed envelopes, where a broken seal would be an obvious indication
that the accounts have been accessed;
Locked in a desk drawer that only specific people can access;
Sealed and taped to the side of a monitor visible to many so it will be obvious when it is
missing or damaged.
For cases where more than one person is needed to declare an emergency, locked in a
safe or cabinet where one person knows the combination or has the cabinet key and a
different person has the key to the room.
Documentation should describe the intended use of such accounts and the consequences of their
inappropriate use. It should be clear that all use of emergency accounts is closely monitored. A
periodic review and retraining of staff should be done to make sure the break–glass procedure
continues to be relevant.
Each use of an emergency account should be reviewed. The use of an emergency account may
be valid, or it might indicate a malicious act. Unacceptable use needs to be recorded and acted
upon. Frequent use may indicate problems with the normal user authentication mechanism.
Disable or delete the emergency account(s) that were used to prevent re–use now that
the password is known. Some systems may be capable of automatically deactivating
emergency accounts after first use or passage of a selectable period such as 8 hours or 1
day. Avoid disabling the account during the period of emergency use.
Reconcile the data acquired and audit trails to reflect the proper operator’s name.
Make entries in disclosures if appropriate Review activities performed including data
acquired/accessed
Determine if the emergency account procedure and operation worked effectively and
adjust if necessary