Commentary

Rob Preston
VP & Editor in Chief, Informationweek  

6 Steps Toward Ensuring Data Privacy

U.S. companies and other organizations that handle lots of employee and customer data (isn't that just about everyone?) need to view privacy as a formal practice, to the point where it can become a competitive differentiator, according to one of the nation's leading privacy executives.

U.S. companies and other organizations that handle lots of employee and customer data (isn't that just about everyone?) need to view privacy as a formal practice, to the point where it can become a competitive differentiator, according to one of the nation's leading privacy executives.Speaking Monday evening at the Society for Information Management's SIMposium in Orlando, Fla., Dr. Kenneth Washington, who was named Lockheed Martin's first "chief privacy leader" in May, laid out a six-step process for U.S. organizations to consider in ensuring data privacy in this age of hyper-connectivity and ever-more-sophisticated information security threats:

• Conduct a privacy assessment or audit. Know what information your organization is gathering, where it's kept, who has access to it, why you're gathering certain types of information, and what you're doing with it all.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

• Pick an accountable person to oversee privacy. That responsibility doesn't have to fall to a chief privacy officer -- in this day and age, few companies have the budget for yet another c-suite czar. Opinions differ on whether that person should live in IT, HR, legal, compliance, or some combination. Washington previously served as CTO of Lockheed Martin Enterprise Information Systems and also chaired the company's IT Architecture Council. And he has a Ph.D. in nuclear engineering -- probably not a prerequisite for the privacy job.

• Create a comprehensive privacy program that includes governance policies and procedures, as well as employee education and training and a plan to regularly communicate policies, to customers as well as employees. That program should also include a breach response plan -- few episodes are as embarrassing as a company scrambling to get its act together on the fly.

• Use a risk-based approach to privacy, stressing prevention (see comprehensive program above).

• Anticipate changes to the legal and regulatory landscape -- though good luck with that one. Washington noted that 43 states now have distinct information privacy laws, and laws vary country by country. Then there are the industry regs (Gramm-Leach-Bliley, HIPAA, etc.) and the content-specific one (Can-Spam).

• Apply successes "to create differentiated value." In other words, all else being equal, customers value companies that respect their privacy more than companies that don't. So do potential employees -- especially the younger generation.

Washington concedes that "complete privacy is out of the question. Now it's a matter of degree." But he exhorts companies to start drawing some lines.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links