Security

External Article

Identifying PII Data to Lock Down in SQL Server - Part 1

  • Article

We're pretty confident that we have locked down and encrypted our financial data, but a lot of our customer's PII (Personally Identifiable Information) data is still held in unencrypted form. This data is able to be selected directly by read only business users on many of our downstream reporting, datawarehouse and standby servers. The rise of identity theft makes protecting this data imperative. DBAs are the custodians of this information and must protect it like we protect our own personal information. Recent publicity over the theft of Sony PSN data underscores both the economic and ethical importance of protecting personal data.

2011-07-14

2,864 reads

Blogs

How I Migrated to Azure PostgreSQL Flex from Single Server

By

I did a couple of posts previously on dumping/restoring Azure PostgreSQL databases and also...

Have a Plan for Your Personal Downtime

By

Most of us know that spending a lot of time on social media and...

Monday Monitor Tips: Lots of Postgres Options

By

Redgate Monitor is growing to include more than just Microsoft SQL Server monitoring. We...

Read the latest Blogs

Forums

Hash Joins IV

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hash Joins IV

How to Load a Fabric Warehouse: Data Engineering with Fabric

By John Miner

Comments posted to this topic are about the item How to Load a Fabric...

Adding the Right Value

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding the Right Value

Visit the forum

Question of the Day

Hash Joins IV

What is a hash bailout?

See possible answers