Almost weekly, news comes out
reporting that a company, university, hospital, or government
has leaked private customer data, exposing their users to privacy
loss, fraud, or identity theft. These leaks can be very dangerous
not only to the individuals but also to the companies
themselves. One way a company can reduce the potential liability
for mishandling or exposing data is to limit the amount of
personally identi?¬?able information (PII) it stores.
PII is data that can be used to uniquely identify, link, contact, or
?¬?nd an individual. PII is not always instantly recognizable as
such when left uncorrelated with other data, and so some measure
of diligence must be applied to recognize it, in or out of
Privacy and Liability
///
public static string CalculateSiteSpeci?¬?cID(string ppid) {
int callSignChars = 10;
char[] charMap =
???"QL23456789ABCDEFGHJKMNPRSTUVWXYZ".ToCharArray();
int charMapLength = charMap.Length;
byte[] raw = Convert.FromBase64String(ppid);
raw = SHA1.Create().ComputeHash(raw);
StringBuilder callSign = new StringBuilder();
for (int i = 0; i < callSignChars; i++) {
//
// after char 3 and char 7, place a dash
//
if (i == 3 || i == 7) {
callSign.
Pages:
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434