When assessing the success of a BI project, one of the most important KPIs to take into account is the usage of the BI solution being delivered. A high BI solution usage is always understood as a success of the BI project. So you need an easy way of tracking who is using the BI solution you just implemented.
On the other side, you also may want to know who is trying to access the system without being granted access. This may help you to discover malicious or unauthorized access attempts to your BI system.
On the other side, you also may want to know who is trying to access the system without being granted access. This may help you to discover malicious or unauthorized access attempts to your BI system.
In order to effectively track and measure successful and unauthorized attempts to your BI system, we are proposing you to apply the following steps:
- Create the database tabe (audit table) that will store all login access information you want to analyze.
- Create a specific Physical Database in the RPD including the audit table, with a Connection Pool that includes the INSERT statement into the audit table in the “Execute On Connect” script section.
- Build an Initialization Block to be executed before the Authentication Initialization Block, which captures in multiple Session Variables the information we want to store in the audit table.
- Build a second Initialization block that executes a dummy query using the new Connection Pool so that the INSERT statement is executed (this statement will use the variables populated in the previous Initialization Block).
- Build a star in the Business Model & Mapping Layer to map the data from the audit table.
- Create a Presentation Catalog based on the new star.
- Build the requests needed to using the new subject areas to analyze the stored login audit data.
Sample request showing user login audit information |