Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

How to hide sensitive data in SQL 2000 table Expand / Collapse
Posted Sunday, October 20, 2013 10:53 AM



Group: General Forum Members
Last Login: Today @ 4:22 PM
Points: 38,553, Visits: 35,560
homebrew01 (10/20/2013)
We were allowed to store CC numbers, but had to have various safeguards in place to be PCI compliant.

When you say you "were allowed to store CC numbers", do you mean in clear text? Also, what were those "various safeguards"?

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Favorite Quotes:
"Has anyone ever told you that a query you have written runs too fast?" - Dwain Camps - 6 Mar 2014

Helpful Links:
How to post code problems
How to post performance problems
Post #1506484
Posted Sunday, October 20, 2013 12:26 PM



Group: General Forum Members
Last Login: Monday, September 28, 2015 7:58 AM
Points: 2,874, Visits: 8,757
Definately NOT clear text. The numbers were encrypted, and the database with the encryption key was in a separate database that was on an encrypted drive with only admin permissions. And all the other safegaurds imposed by PCI over the whole IT infrastructure.

Post #1506494
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse