Skip to main content

Add Robert Half to the Epsilon Breech Fiasco

Image
By
On my work e-mail:

Today we were informed by Epsilon Interactive, our national 
email service provider, that your email address was exposed due 
to unauthorized access of their system. Robert Half uses Epsilon 
to send marketing and service emails on our behalf. 

We deeply regret this has taken place and any inconvenience this 
may have caused you. We take your privacy very seriously, and we 
will continue to work diligently to protect your personal 
information. We were advised by Epsilon that the information 
that was obtained was limited to email addresses only. 

Please note, it is possible you may receive spam email messages 
as a result. We want to urge you to be cautious when opening 
links or attachments from unknown third parties. We ask that you 
remain alert to any unusual or suspicious emails. 

As always, if you have any questions, or need any additional 
information, please do not hesitate to contact us customersecurity@rhi.com. 

Sincerely,

Robert Half Customer Care 

Robert Half Finance & Accounting
Robert Half Management Recourses
Robert Half Legal
Robert Half Technology
The Creative Group

I did not ask to be on RH's e-mail list.
Labels:

Comments

  1. ax0nApril 5, 2011 at 8:37 AM

    RH is basically a "headhunter" type firm, and recruiters often shop around for firms with more leverage, and it's no surprise they often take their contact list with them. If you've ever talked to any recruiter that ever ended up at a Robert Half office, you're probably in Robert Half's database somehow.

    ReplyDelete
  2. Michael JankeApril 5, 2011 at 1:02 PM

    I'm sure that I'm in more databases than I can count (and I can count pretty high...)

    :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Cargo Cult System Administration

By
“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…
7 comments
Read more

Ad-Hoc Verses Structured System Management

By
Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to …
6 comments
Read more

The Cloud – Provider Failure Modes

By
In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…
1 comment
Read more