1 Security Management

This topic explains how to define and maintain the security of the banking system in terms of user access and roles.

Controlled access to the system is a basic parameter that determines the robustness of the security in banking software. In Oracle FLEXCUBE Universal Banking, we have employed a multi-pronged approach to ensure that these parameters are in place.

Table 1-1 Security Management Parameters

Security Management Parameters Description
Only Authorized Users Access the System First, only authorized users can access the system with the help of a unique User ID and a password. Secondly, a user should have access rights to execute a function.
User Profiles The user profile of a user contains the User ID, Password, and Functions to which the user has access.
Restricted Number of Unsuccessful Attempts Define the maximum number of unsuccessful attempts after which a User ID should be disabled. When a User ID has been disabled, the administrator should enable it. The password of a user can be made applicable only for a fixed period. This forces the user to change the password at regular intervals thus reducing security risks. Further, define passwords that could be commonly used by a user as Restrictive Passwords at the user, user role, and bank level. A user cannot use any password that is listed as a Restrictive Password at any of these levels.
Restricted Access to Branches Indicate the branches from where a user can operate in the Restricted Access screen.
All Activities Tracked An extensive log is kept of all the activities on the system. The user can generate reports on the usage of the system anytime. These reports give details of unsuccessful attempts at accessing the system along with the nature of these attempts. It could be an invalid password attempt, the last login time of a user, etc.
Audit Trail Whenever a record is saved in the module, the ID of the user who saved the record is displayed in the Input By field at the bottom of the screen. The date and time at which the record is saved are displayed in the Date/Time field. A record that is entered should be authorized by a user, bearing a different login ID, before the EOD is run. Once the record is authorized, the ID of the user who authorized the record will be displayed in the Authorized By field. The date and time at which the record was authorized are displayed in the Date/Time field positioned next to the Authorized By field. The number of modifications that have happened to the record is stored in the field Modification Number. The status of the record whether it is Open or Closed is also recorded in the Open check box.

The topic contains following sub-topics: