1. Analysing and Classifying Data at Rest
Simon Carlson 2 September, 2016

2. Security and risk (S&R) pros can’t expect to adequately protect data if they don’t have knowledge about what data exists, where it resides, how valuable it is to the firm, and who can use it.
March Rethinking Data Discovery and Data Classification Strategies

3. Today’s Organization
No longer is data isolated to a few users or even within four walls. We create it, upload it, share it, download it, and we send it to other users around the globe and to partners.
90% of world’s data created within last few years
Storage options increasing, costs to store decreasing
Ever increasing need to collaborate, across the office and across the world
More data being created, stored and shared
By people
By machines

4. Today’s Data
Add to the complexity of all that data being created the fact it’s not only your people creating data.
<BUILD> You also have system generated content.
How can you make sure that these files are protected if your users aren’t even involved in their creation? Additionally, wouldn’t you like to know something about the sensitivity of the files being created by your various systems?
<BUILD> This may be reports being generated out of Salesforce, Drawings out of SAP, you name it.

5. The Databerg Problem 14% Business Critical 46% 32% R.O.T.
Identified
32% R.O.T.
54% Dark Data
Use the example of lawsuits – many organizations are now choosing to settle rather than go through with e-Discovery, as the task is far too daunting, and would require too many resources (people and $$) to

6. “Everything here is my most important thing!”
Data Hording
“Everything here is my most important thing!”

7. Classify data in use
Custom
Metadata

8. Scan Data at Rest Identify What, where, who? Scan Content
Protect Sensitive Data
Classify with Metadata
Discover & Identify
Data at Rest
Analyze Data Sensitivity
Identify
What, where, who?
Scan Content
Identify PCI, PII, PHI, scan for Intellectual Property
<BUILD> Classify
Bulk classify data assets
Classify based on that PCI, PII, PHI, IP
<BUILD> Protect
Protect through applying RMS/encryption
Other means of “protection” via quarantining, moving, marking the files, etc.
<BUILD> Analyze
As Illuminate is performing its scans, it collects information about the files that you can later analyze and report against

9. Identify Dark Data
Owner
Sensitivity
Location
Zac Smith
PII
Human Resources/Updates
Jane Doe
PCI
Finance/Collections
PHI
So how do we answer those concerns? Through data discovery and subsequent analysis.
Discover, Classify, Protect, and Analyze your data

10. Reduce Data Liability Eliminate Redundant, Obsolete, Trivial (ROT)
Image needs updating to TITUS format…

11. Identification Before Migration
Metadata Policy Border
Classification / CASB / DLP
Starting with Data Identification and classification, you can make educated decisions on what to move to the cloud.
Additionally, given that Illuminate embeds the classification metadata, migration tools can read the information and only move the appropriate files.
Maybe you want to start with public files, and go from there? Maybe you’re comfortable with all but the most highly sensitive data being stored in the cloud?
Use Illuminate to identify all your data, and feel confident about what you’re migrating to the cloud.

12. Discover, Classify, Protect
Discover files anywhere
Identify sensitivity
Classify
Embed metadata
Protect where appropriate
Box
Dropbox
OneDrive
SharePoint
Cloud
On Premise
Let’s start with your on-premise files, your:
Network File Shares
SharePoint On Premise
WHAT is my data?
WHERE is my data?

13. Data Discovery Risk of Breach Data Awareness Data Liability
Cloud Storage Risks
Data ROT
Data Awareness