Progress Acquires MarkLogic! Learn More

All Posts By

Caio Milani

Caio Milani is Director of Product Management at MarkLogic responsible for various aspects of the product including infrastructure, operations, security, cloud and performance. Prior to joining MarkLogic, he held product management roles at EMC and Symantec where he was responsible for storage, high availability and management products.
Caio holds a BSEE from the University of Sao Paulo and a full-time MBA Degree from the University of California, Berkeley.

The common approach to mitigate linkage attacks is to anonymize data before exporting by removing PII-personally identifiable information such as ID, phones, etc. Unfortunately, this is not enough.
How do you find and control access to Personally Identifiable Information and sensitive information in a MarkLogic database?
 
In my previous blog about Brexit, I talked about using MarkLogic server roles and document-level permissions to create an adaptable security model, ready for regulation changes that might come as the United Kingdom exits European Union. But what if the piece of information that I need to assert access control is inside a document?
In preparing your security model for Brexit, MarkLogic administrators should start adopting granular permissions and a hierarchical role-based access control model. We demonstrate this with a simple use case based on document creation location.