Risk Analytics can be used in a multi-environment scenario. Multi-environment allows for a single schema of Risk Analytics to be used in different contexts (e.g. different digital banking application and corporate banking application). The data and entire configuration of the environments are stored and presented in strict isolation, except for the Forensic Analysis page, which provides information about events that occurred in all the environments of the schema.
Risk Analytics isolates environments of a schema by ensuring for each record that is inserted into the database to have an attached Label Security identifier. When information is presented to a user who belongs to a given isolated environment, only the pending alerts with the associated Label Security identifier are presented. This is achieved by maintaining the table hierarchy inside the database, containing physical and logical tables.
Physical (PT_) and Logical Tables (LT_)
PT_ and LT_ tables contain the same metadata. Physical tables are the base tables of Risk Analytics. Logical tables are views that display the information contained in the physical tables. Pending alerts are allowed in these tables in accordance with a user’s Label Security identifier. Information that has been removed (i.e. that has been marked as deleted) is not displayed in logical tables.
Master administrators (i.e. users having ADMIN_ROLE in the first environment) can allocate the experience inside an isolated environment by emulating the corresponding environment. Once this emulated environment is assigned to the master administrator, they will experience the same system behavior as a user directly logged-in to that isolated environment.
Clicking Assign Environment emulates the relevant environment.
Only a master administrator can assign environments!
The indicator, if the currently used environment is emulated, is an @-symbol contained in the user name that is displayed in Risk Analytics Presentation Service. The name following the @ symbol is that of the emulated environment.
Creating an isolated environment
A completely isolated environment can be created directly in Risk Analytics Presentation Service A highly dynamic web interface that provides webpages for the user to intuitively interact with Risk Analytics. It is a Microsoft .NET 4.7.2 ASP.NET application hosted inside Microsoft Internet Information Services (IIS).. Adding an isolated environment does not result in any system downtime.
Only master administrators (i.e. users with the ADMIN_ROLE in the first environment) can create new isolated environments.
Once the master administrator has created a new isolated environment, e.g. Emulated_Bank1, they can provide the customer with the URL of Risk Analytics Presentation Service. The user logs on with the default login credentials for that new environment:
• Logon name: Name of the new environment, e.g. Emulated_Bank1
• Default Password: Name of the new environment, e.g. Emulated_Bank1
Immediately after the first login with these credentials the user will be prompted to change the default password.