GDPR COMPLIANCE GET THERE FASTER, STAY THERE FOR...

©2016 Dataguise, Inc. Confidential and Proprietary©2016 Dataguise, Inc. Confidential and Proprietary 1

GDPR COMPLIANCEGET THERE FASTER, STAY THERE FOR GOOD

Dataguise is the only vendor to provide end-to-end sensitive data protection to help you meet regulatory

requirements and maintain compliance as your business grows.

©2016 Dataguise, Inc. Confidential and Proprietary

Dataguise Quick Facts

2

Magic Quadrant

“Visionary” for Data

Masking

2015

Recommended for

Data-Centric

Security

2015

Recommended for

Protecting Big Data

in Hadoop

2015

2007-2010“Breakthrough”

Masking

Technology

2011-2013Pioneers of Hadoop

Data Protection

2014The “Essential” Solution

for Data Protection in

Hadoop


Trusted By World’s Largest Brands - 50 Billion Records Protected

3


The Road to GDPR… Step 1

4

Take the First Step: Sensitive Data DiscoveryIf you don’t know where all your sensitive data is, you can’t pass an audit.

• Why is this a hard problem?

1. Data can be in many different repositories, both on-premises or in the cloud

2. Data may be highly unstructured and hard to analyze

3. Volume of data is more than ever before and cannot be handled manually



How to achieve comprehensive visibility?

5

What you need to know about your sensitive data?

1. What data repositories are there? – Databases, Hadoop, File Shares, NoSQL…

2. Is there data structured or unstructured?

3. What databases or file types does the data reside in?

4. Where is the data stored and where is it accessed?

5. Who can access this data?


Unprecedented View of all Assets

6


The Road to GDPR…

7

Place appropriate protection controls

Why is this a hard problem?

1. Perimeter and access controls have been historically susceptible to

breaches

2. Because of multiple requirements of preserving and using data,

different users might require different granularity of access

to breaches

1. Because of multiple requirements of

preserving and using data, different users

might require different granularity of

access

YOU NEED THAT………AND *MORE!



Protection mechanisms to help with GDPR compliance

8

• Data-centric masking – One way transformation of sensitive data into realistic looking, but fictitious values

Useful for:

1. Preserving the look and feel of data

2. Sharing and/or publishing anonymized data

3. To perform analytics on parts of the data or complete data

4. Guaranteeing privacy

5. Test / Dev scenarios



Protection mechanisms to help with GDPR compliance

9

• Data-centric encryption – Two way transformation of sensitive data in garbage values, that can be converted back to the real values for the authorized users upon access

Useful for:

1. When the original values are required to be accessed


The Road to GDPR

Fully automated processes for sensitive data governance

10


1. Too many data repositories i.e. multiple flavors of Hadoop, relational databases, NoSQL

databases, File Shares, Operating Systems, etc.

2. Too many new versions of the existing products and many legacy systems.



Scope of impact and the scale of sensitive data governance

11

• Tools must be able to find and protect sensitive data, no matter where it exists

• Tools must be able to scan multiple petabytes of data

• Use tools that are easy to use and have licensed support system available 24/7


The Road to GDPR…

12

• Generate sensitive data reports continuously for data at rest and in motion


1. Need 1 tool to analyze data at rest and in motion

2. Need subject matter expertize on what sensitive data policies and

elements to detect, protect and monitor for GDPR compliance


The Road to GDPR

How can monitoring help with GDPR compliance?

13

• Fast and easy creation of sensitive data governance policies using pre-built or custom templates—no coding required

• Continuous monitoring of all attempts to access sensitive data and the results (

• Immediate alerting to atypical user behavior, based on profile analytics and machine learning

• Comprehensive coverage across on-premises and cloud environments, including Hadoop, Cassandra, Amazon S3, and Blob storage

• Dashboard views of alerts, policies, metrics, and trends to understand the extent of monitoring coverage and potential exposure of sensitive data types or sources



What information should these reports contain

1. The location and types of all sensitive data repositories

2. The location and quantities of sensitive data assets

3. How much of this data is exposed?

4. How much of this data is protected?

5. How much of this data is un-scanned?

6. How much of this data is being monitored?

14


Dataguise DgSecure Overview

15

DETECTWhere sensitive content is present in struct, unstruct, semi-struct data

AUDITWho has access to which sensitive data & identify misalignments and risk factors

PROTECTSensitive data at the element level–encrypt/decrypt with RBAC, mask, redact

MONITORBased on metadata, track how and where sensitive data is being accessed through a 360° dashboard

Across Hadoop, RDBMS, Files,

NoSQL DB

On Premises, in the Cloud,

or Hybrid


Take the first step

16

Learn more about Dataguise

Schedule a deep dive session for a free POC

Talk to us for more technical discussions

http://www.dataguise.com/

GDPR COMPLIANCE GET THERE FASTER, STAY THERE FOR...

Documents

Transcript of GDPR COMPLIANCE GET THERE FASTER, STAY THERE FOR...