Immuta Data Security Platform

Our use cases are for data access control and data access control provisioning. We also use it for roles and policies. 

Immuta was pivotal for us in making sure that only people who should be accessing specific datasets, get access to the datasets, and to make sure that those that should not be seeing private data, get that data mask. 

All features available are good.

We have had some challenges with their support when we were migrating to the cloud version. We we had some issues, and it took us several attempts to get a proper responses as part of that migration.

I have been using Immuta for one and a half year.

The solution is highly stable. I rate the stability a ten out of ten. 

It is a scalable solution. Presently, hundred thirty users are using the solution. I rate the scalability an eight out of ten.  

I have seen ROI as there has been Increased security and compliance.

My advice would be to make sure that the data and security requirements of the organization are complex and sophisticated enough to call for the rollout of the tool. 

There is certainly overhead to maintaining it and rolling it out and sort of there needs to be complexity to the data or data access use cases before one gets down the path of that third-party solution versus standard out of the box. I rate the overall solution an eight out of ten. 

We use the product for data governance management. It helps us to create policies and restrict sensitive data. 

The tool's most valuable feature is restriction. 

Immuta is behind in updating upgrades and software releases. 

I have been using the product for the last three years. 

Immuta is stable. 

I rate the product's scalability a seven point five out of ten. 

Immuta's deployment is simple. 

Immuta's pricing is expensive. 

I rate the product a seven out of ten. 

The primary use case predominantly revolves around data governance. Our customers manage data across various data centers, especially within Europe, where GDPR and other privacy regulations necessitate strict data control. Immuta enables us to enforce these policies, restricting user access to data from different regions and implementing data masking for sensitive information. Furthermore, we utilize role-based security to control access at a granular level. For instance, specific users may only view items with a price exceeding five hundred. In essence, our primary focus is on data governance.

Immuta offers two main components: subscription policies and data policies. Data policies align with use cases involving role-level security, ensuring that users access data according to their roles. Subscription policies, on the other hand, enable users to subscribe to specific data subsets based on their region. For example, someone in France wouldn't be able to access data from a California team, and vice versa. Immuta enforces these policies at the database level, providing users with a sense of abstraction. You see a certain set of data, which you perceive as a complete picture, but you're actually limited to specific portions, akin to viewing just one sheet in an Excel file while being unaware of the contents of the other sheets. Immuta ensures users always see the data they need, abstracting the complexities associated with region-specific data access.

Another valuable feature of Immuta is automatic data tagging and PII discovery. Instead of manually tagging data, Immuta’s auto-discovery capability identifies sensitive information, such as country labels, gender information, and other personal data. It self-tags this data, allowing you to enforce appropriate policies. For example, if someone doesn't want to disclose their gender or age, Immuta’s self-discovery helps ensure this sensitive information is handled with care. Immuta alerts you about the detected data that should be handled cautiously.

Immuta has room for improvement in several areas due to its relatively new platform. One critical aspect is the integration with databases, which is still in its early stages. Currently, Immuta can read data from the database but doesn't send the processed metadata back to the database. This disrupts the data chain, as the database must generate its own metadata to simulate what's done in Immuta. While Immuta is working on addressing this issue, the development is expected to be available next year.

Another complexity arises from setting up users directly in Immuta. Immuta creates its own data syncing patterns for users from an organizational directory, like an active directory, and these patterns don't align with the database's patterns. As a result, database administrators or data governance consultants have to manually delete users from both Immuta and the database, which is an overhead task. If Immuta could automate this process by reading user information from the database, it would greatly simplify user management. This area needs improvement as well.

I have been using Immuta for five months.

In terms of stability, Immuta has been quite reliable, provided that it remains up and running. They regularly release system upgrade patches, and they are proactive in communicating these updates to all stakeholders. These patches have not caused any significant stability issues so far. Therefore, I would rate Immuta positively in terms of stability.

In our case, we have a small setup with around 25 people, so I might not be the best person to evaluate scalability. Our data volume is minimal, and the system has been working well without any issues so far.

There have been instances where the demos were overly technical and not presented in a business-oriented way. It's important to remember that the tool is used by business users, and the presentations should cater to a non-technical audience. Many attendees at data governance conferences are not well-versed in technical jargon, so it's essential to present information in a way that's accessible to everyone.

Neutral

The implementation process with Immuta was quite challenging, primarily due to issues related to database handling and the syncing of user groups. Initially, the setup involved creating a service account, which was complicated because it required authorizing based on the directory. This authorization process was questionable at times. However, over time, the setup has become more efficient and is working smoothly.

Regarding usage patterns, syncing patterns, and metadata automation, everything is currently handled within the Immuta platform, and no additional automation tools have been deployed. Immuta takes care of data governance comprehensively.

The implementation process took approximately four or five days, and involved five or six people.

We conducted a successful proof of concept with Immuta, and one of the key factors contributing to our choice was its compatibility with our database. This compatibility was a significant advantage for us.

It's important to prepare a checklist and not rush into decisions. Create a checklist that outlines your specific requirements and prioritize them. Consider factors like data classification, sensitivity, and the potential impact on your business. Understand the consequences of exposing sensitive data and evaluate whether Inmuda aligns with your needs. Doing your homework and assessing your requirements thoroughly is essential before choosing Inmuda.

I would rate it a seven out of ten.

I primarily use Immuta  for data governance, employing global policies to enhance efficiency in data processing while also prioritizing data security. This method not only boosts data efficiency but also strengthens security measures. Also, I use it for scanning and simple ping functionality to monitor activities.

What I appreciate the most is its user-friendliness.

There is room for improvement in enhancing the monitoring capabilities.

I have been working with it for three years.

In terms of stability, I would say it is generally good, and I would rate it seven out of ten. There have been occasional challenges with configuring the emulator for specific data sources and implementing access control policies. Setting up data connectors in the meter and defining data policies has also presented certain complexities. Additionally, integrating with our existing infrastructure has posed its own set of challenges.

Currently, in my organization, we have a significant number of data analysts and data security analysts who rely on Immuta  for their work. It is used to manage the data for over a thousand users. It provides excellent scalability capabilities and I would rate it nine out of ten.

The initial setup was straightforward.

The deployment process took approximately fifteen days to complete.

I would certainly recommend this product and I would rate it eight out of ten.