The Immuta team is excited to announce our latest 2.1 release. Below are the highlights of the new features included in the release.
Support for Spark
Immuta can now enforce all the same policies historically available through Immuta while allowing massive scale processing in Spark. Why is this important? There’s no limit to how much data you can process, secure, and audit with Immuta policies. With this feature, the policies are enforced natively in SparkSQL during file access. In other words, SparkSQL is still doing it’s raw read from the HDFS files AND enforcing the Immuta controls. No Hadoop out-of-the-box tools exist to dynamically enforce this type of control to enable Spark in highly regulated environments.
For more technical details on this feature, please visit our 2.1 Spark blog and also check out our quick video on the feature below:
New to Immuta 2.1 is a report generation tool, this allows compliance and legal to generate common reports based on the Immuta audit logs rather than having to rely on IT to comb the audit logs. This is critical to prove compliance to outside auditors and regulations such as GDPR. The reports allow interactive building of reports that cover audits of who is touching what data, how often, for what purpose, what policies are applied where, who has access to what data, since when, etc. Once a report is generated, it can be visualized in Immuta or exported as a report that can be sent digitally.
Please watch a short 4 minute video on this feature:
Simplified Create Data Source Workflow
We completely overhauled how you expose data through Immuta to make it even faster for data owners to expose and protect their data. In addition to the workflow changes, we included features such as cloning configurations, policies, and users to new data sources.
Governance and compliance professionals needed to be able to visualize all the alerts and notifications Immuta sends in one place. Notifications are sent both in the app and over email, to critical activities occuring in the platform, such as entitlement workflow actions, policy changes, and new data being exposed. This feature allows single place to view, sort, and filter notification history.
WHERE Clause Policy
In addition to our many existing policies, we’ve added yet another way to enforce row level security beyond our existing capability which matches user attributes to data attributes for access decisions. The WHERE clause policy adds additional row level security flexibility by allowing the policy author to enforce a view dynamically based on a condition which references user attributes, groups, or roles. For example the below policy will filter out bank deposits from the state of Missouri for everyone except users that have a branch location in Missouri.
Additional Database Support
Based on customer demand, we’ve added support for both Azure Blob Storage and Netezza.
We couldn’t be more excited about our latest release. In particular the Spark functionality, which allows Immuta to span all data processing paradigms from pinpoint file-based controls in our virtual filesystem, to query-based controls in our virtual SQL layer, and now massive scale processing through native SparkSQL while enforcing all complex controls.