Security News Brief: 10-22-08

8:42 am on October 22, 2008 | By Meghan Whelan | In data breach, laptop security, laptop theft | No Comments

Share/Save/Bookmark

 

Security News Brief: 10-03-08

9:43 am on October 3, 2008 | By Meghan Whelan | In identity theft, information security, laptop theft, security policy | No Comments

Share/Save/Bookmark

 

Security News Brief: 09-09-08

9:49 am on September 9, 2008 | By Meghan Whelan | In data breach, information security, laptop security, laptop theft | No Comments

Share/Save/Bookmark

 

Relying on user compliance is risky business.

7:28 pm on July 14, 2008 | By Cam Roberson | In laptop security, laptop theft | No Comments

 

Most of us have become desensitized to the almost daily reports of laptop loss or theft. Heck, I barely notice them anymore - and I’m in the industry! What blows me away though, is the boilerplate mantra from the spokesman of the at-fault company when defending their indefensible position with the media. Always well-rehearsed and nearly believable, those statements are derived from the now necessary PR outline, “CYA: Laptop Loss, What to Say to the Press”. I happen to have found this early version used in 2006 by a very large aeronautics manufacturer. It has been used and personalized hundreds of times since by companies big and small. Here it is:

“CYA: Laptop Loss - What to Say to the Press”

(note to spokesman: whenever possible try to assign the loss as a theft. A simple loss implies that the user may have been flippant, careless and/or negligent).

1.    (your company name) is very concerned about protecting the privacy of its employees customers and/or clients.

2.    (your company name) has no reason to believe that the laptop was stolen for anything other than the hardware value

3.    The laptop was protected with passwords

4.    The employee of (your company name) is being reprimanded (or terminated) for violation of data security policy. Cite one of these policy violations:

a.    employees are prohibited from taking sensitive data outside business walls on laptops

b.    employee shared or otherwise exposed passwords and/or login credentials

c.    (your company name) has selected, and is in the process, of deploying encryption but have not yet completed the rollout

d.   if possible, assign blame to a rogue contractor, vendor or service provider. This action tends to confuse readers as to whom is really at fault for the breach

5.    Reiterate that “because (your company name) is very concerned about protecting sensitive data,” better and more strict employee (or vendor/contractor) data policy will be effective (fill in reasonable time schedule).

Continue reading Relying on user compliance is risky business….

Share/Save/Bookmark