Federal Use Cases for Dataguise Data-Centric Security

It is so easy in the software industry to jump headlong into the product's technical details, specific IP or new leading edge "thing".  But when you stand back from all the technical jargon, the customer has to have a basic use case to justify interest and time spend on evaluation.  This holds true for Dataguise.  In general, Dataguise enables the safe use of sensitive data but below are four use cases on why customers utilize Dataguise.   If you want more information on specific customer stories that support these, please email me at dave.devries@dataguise.com or visit www.dataguise.com 

1.) Addressing the Risk of Insider Threat: By employing a data–centric security model, Dataguise discovers and protects your sensitive data at the element level. By being able to offer users different levels of access to the sensitive data, you limit the risk of insider threat.

2.) Enabling the Collaborating and Sharing of Sensitive Data: By discovering and desensitizing all sensitive information, a user or agency could safely share their sensitive data, safely with vendors, partners, contractors because the sensitive data has been redacted.

3.)  Pre-Breach Assessment and Audit Compliance: Hadoop and database environments are becoming much more complex and it is becoming very hard to stay audit compliant.  By discovering all sensitive data, you can understand your environment better than the auditors.

4.)  Enabling In-Flight Declassification/Redaction of Data: Federal agencies have so much data flowing into the clusters, it is almost impossible to sort through all the data for redaction or cleaning.  With Dataguise, it's an automated process for identifying and desensitizing data as data is ingested so that when it reaches your environment, the information is already secure.