A Wealth of Data, and Nobody in Charge

Privacy advocates argue that academic institutions should hire full-time privacy officers to focus solely on privacy as "the job of security officers is to protect data that are already collected — not to ask whether the data should be captured and stored in the first place."

This article exposes a salient truth about the academic sector. In the past two weeks, I have come across two instances where academia has appeared clueless when it comes to data security and privacy. One is contained in the article below ("what's a CPO?"), the second was posted on the social networking site Twitter by a frustrated security professional who was dumb-founded to have to explain the term "penetration test" to a group of Computer Science PhDs.

Src: A Wealth of Data, and Nobody in Charge (Chronicle.com)

No comments: