Kadeck 5.2 - Enhanced data policies, Apple Silicon support, and more

Empowering Data Control with New Features and Enhancements

We’re excited to launch Kadeck 5.2, packed with major updates to our data protection policies, data catalog, and core architecture. This version enhances our Data Protection Policies and adds supports for Apple Silicon and ARM for both Kadeck Desktop and Kadeck Teams.

Enhanced Data Protection Policies

Our customers rely on Kadeck to manage and analyze data streams containing sensitive info like account numbers and personal identifiers. We’ve had Data Protection Policies for this, but now we've made them even better.

While most employees should see masked data fields to meet privacy rules, teams like Fraud Detection and Compliance need full access to unmasked data to do their jobs.

In this release, we’re introducing the ability to exclude specific groups from certain Data Protection Policies.

Field nesting in Data Protection Policies

Let's imagine your sensitive fields have the following schema:

Now, you can easily write card_no.string in Kadeck’s Data Protection Policy editor to mask this field in your data stream.

‍

Key Highlights of Kadeck 5.2

Apple Silicon & ARM Support

• Kadeck Desktop and Kadeck Teams now fully support Apple Silicon and ARM architectures. This will improve the performance on new devices by up to 12x according to our internal tests.

Enhanced Kafka Data Streaming Client

• We’ve improved our underlying Kafka data streaming client. We have fixed a critical issue with offset calculations that previously hindered the loading of all records in certain scenarios.

Refined Schema Registry Integration

• Protobuf codecs dependent on the Schema Registry will no longer initialize for connections without a Schema Registry.
• Fixed the inclusion of codecs with negative priority in auto detection.

Advanced Data Policies

• Introduced support for JSON paths as data protection fields. For instance, specifying "card_no.string" will now only affect "string" fields within "card_no".
• You can now specify groups that should be excluded from a data policy.

Improved Data Catalog

• Added backwards compatibility for owner assignments in the Data Catalog from old versions.

‍