It’s one thing to set up a security framework for your entire application. But implementing new scenarios in an analytics setting often means redoing work that’s already been done.
Fortunately, working with an analytics development platform that has an adaptive security model means you can eliminate time-consuming and costly efforts. With the Logi platform, you can integrate analytics into your existing security infrastructure so you can deploy embedded dashboards and reports instantly and securely.
Here are our top three ways to keep your analytics safe:
1. Flexible Security Model
The beauty of Logi is that we use your security model. We realize our customers have already invested plenty of time and effort in their security. That’s why Logi applications are built to preserve all security throughout the dashboards and reports our customers build. This enables easier integration and administration, plus it eliminates any duplication of efforts on your end.
We leverage the “three A’s of security”:
- Authentication, to identify the user and establish their roles and rights
- Authorization, to limit access to reports and data, customize the user experience, and integrate with your existing security model
- Auditing, to monitor user activity and identify any suspicious activity or data breaches
However secure your three A’s already are, Logi will be able to take advantage of that. We won’t add extra security, but unlike many other analytics providers, we won’t expose you to any new areas of attack. So it’s important to ensure you already have a strong security framework in place to authenticate and monitor users.
2. SecureKey Authentication
Ideal for embedded analytics security, the Logi SecureKey model is an authentication method that integrates with your existing framework and lets you manage everything in one place. Your intranet, portal, or application does the authentication and passes it through to Logi Info, so we support single sign-on and users only need to log in once. This is great for user adoption because users don’t have to learn a new environment or create a new username/password—so they have no reason to leave your application.
In addition to SecureKey, we use these authentication methods:
- AuthNT is best for internal use or deployed applications. It allows automatic login for Windows users (via impersonation).
- Standard/database security is form-based authentication. It uses a standard login page where user information is checked against a database or file system to determine authenticity.
3. Security Granularity & Multi-Tenant Support
Logi has quite a variety of security granularity, meaning we can secure different parts of the application, workflow, and capabilities based on individual rights and roles. We can lock things down at the report level, the visualization or dashboard level, or all the way down to the data driving the application (the row or column level). This is very important for multi-tenant deployments because you want to ensure that client A does not have access to client B’s information.