The Ionic Platform allows any developer to add data trust services to their application with a few lines of code that provide a consistent approach to data visibility, control, and protection.
With our latest SDK release (v 1.4), we continue to add more flexibility to enable developers to apply the right security posture across structured or unstructured data and the context of their application.
Some of the more exciting enhancements in this release give a developer far more control over key management and applying context-based data protection. These features extend the core value proposition of using the Ionic Platform to be able to uniformly enforce contextual data security policies no matter the repository based on user, device, time, network, location — and ultimately data.
The Ionic Platform allows developers to associate a set of attributes with a key at the time of creation. Until recently, these attributes were fixed at the time of key creation — any change to a given attribute, like associating a different classification with some protected data — required the creation of a new key. It is now possible to define two sets of attributes when creating a key, a set of fixed attributes as before, and a second set of “mutable” attributes that can be modified by subsequent “update key” requests – based on Ionic’s powerful attribute-based access-control (ABAC) policies. This feature is now accessible from all supported languages.
Support for External Identifiers
It is now possible to associate external identifiers with Ionic keys, and to request keys based on their previously associated external identifiers (in addition to or instead of the key tags). These associations can be made at creation time via the ‘ionic-external-id’ attribute.
Additional details are available here.
“Shared Secret” Persistors
The Ionic SDK now supports a new interface for profile storage, SecretShareData (in addition to the many method supported already and shown here). Implementations of this interface are used to generate a cryptography key from data supplied by the implementation. This feature allows the information in a “secure enrollment profile” to be encrypted using information gleaned from the computing environment. By associating characteristics specific to a given environment, applications can be launched and configured without relying on manual or explicit parameter-based authentication.
Needing to secure files as they are created, consumed and shared across an organization or to external collaborators is one of the common ways that the Ionic Platform is used, whether that is the Ionic Secure Files solution, or using the Ionic Platform to secure files across the most popular on-premise and cloud applications. To support these use cases, the following changes were made to the SDK.
Custom Cover Pages
Applications written in C or Python (in addition to C++, C#, ObjectiveC, and Java 1.x which were previously supported) can now create secure documents in OpenXML (Word, Excel, and PowerPoint), PDF, and CSV formats that include the custom cover pages associated with a particular account. Support for Custom Cover Pages was initially introduced in an earlier version of the Ionic SDK, but was available only through select language bindings. Custom Cover Pages offer enterprises an ability to provide users who, for some reason, are not able to view a protected document, with explicit instructions on how to gain access.
These are some of the enhancements to the Ionic SDK in the latest release that benefit all users of the Ionic Platform. Learn more about the types of solutions our customers and partners are building with Ionic at https://www.ionic.com/platform/.
The Ionic SDK, v. 1.4, allows application developers to leverage the power of the Ionic Platform from a variety of programming languages including “C++”, “C”, “Objective-C”, “C#”, “Java”, and “Python”. Learn more and get started using the Ionic SDK at dev.ionic.com.