Yurbi® was designed with security in mind. It includes multiple levels of both user and data security. Yurbi provides users easier access to information, but it also ensures that users only get access to the information that you deem necessary. And just like the rest of the Yurbi platform, applying security is easy and doesn't require any scripting or programming.
Yurbi follows a Role Based Access Control (RBAC) model. In the Admin tab of Yurbi, administrators can define security groups and assign individual users specific permissions related to their library folder and report permissions. Administrators also designate what Yurbi Apps a user has permission to access and what their functions are related to the App. User permissions are specific to each App, so a single user may have Building rights to one Yurbi App, but only have the ability to view pre-built reports from a second Yurbi App. Once applying user roles and permissions they apply throughout the entire Yurbi platform and secure all Apps, reports, dashboards, Virtual Apps, and even Linked Reports. Yurbi even supports a Guest/Anonymous mode for reports you want to share with the public.
When it comes to data security it's not enough just to limit who has access to the data. App Shield allows you to define security policies that determine exactly what portion of the data a particular user or security group can see. For example, a regional manager should be able to create reports for their region but not for other regions. With traditional BI tools this is achieved by hard-coding programming language inside each report or dashboard. This can cause a maintenance nightmare as one regional report turns into 10, 20 or more depending on how many regions exist within your company. With Yurbi App Shield you develop security policies, across multiple Yurbi Apps, to control exactly what information a user or group can see. App Shield policies apply to all aspects of the Yurbi Platform, from dashboards, to reports, to even Smart Prompts, and ensure that users can only see what they should. App Shield security constraints are applied at the database query level. So, that means if a person doesn't have access to see information, Yurbi never even pulls it from the database. This reduces the traffic over the network and improves the performance of the database and server.
When creating users in Yurbi you have the option of configuring PIN-based authentication or leveraging Windows Authentication to log into Yurbi. This model supports both internal and external users. Internal users can log in with their existing network password while partners, consultants, and even customers can access Yurbi using a PIN-based login. Yurbi has a component called a Security Provider, which can be installed on multiple servers and in multiple windows domains to provide cross-domain authentication if needed. Multiple Yurbi Security Providers also provide fault tolerance to ensure users will continue to have access to Yurbi, even if one of the security providers becomes inaccessible.
As a web application, Yurbi supports Windows® Internet Information Server (IIS) security methods, such as HTTPS SSL based access. For environments that require encryption of data between the Yurbi server and the data sources, Yurbi supports both Oracle®Security for Client Connections as well as Microsoft® SQL Database client security options. Yurbi also support Web Single Sign On applications, as well as Windows® IIS pass through authentication options. Even the ports that Yurbi uses for inter-product web services communication can be configured to match customer firewall policies.
