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

Vibe Coding a Login Tracking System

By

A customer was asking about tracking logins and logouts in Redgate Monitor. We don’t...

4 CPE Opportunity (Virtual) for Charity

By

Every year, the South Carolina State Internal Auditors Association and the South Carolina Midlands...

Data Céilí 2026 Call for Speakers!

By

Data Céilí 2026 Call for Speakers is now live! Data Céilí (pronounced kay-lee), is...

Read the latest Blogs

Forums

SQL Server audit with windows ad group

By pollando

I am trying to create a filter on a SQL Server audit to capture...

Deadlock graph anomaly

By Databae

I've come across what appears to be a strange deadlock anomaly. As seen in...

Stairway to Azure SQL Hyperscale Level 6: Backup and Restore Internals

By Chandan Shukla

Comments posted to this topic are about the item Stairway to Azure SQL Hyperscale...

Visit the forum

Question of the Day

Deprecated Feature Tracking

From T-SQL, without requiring an XEvent session, can I tell which deprecated features are being used on my instance?

See possible answers