I just got off the phone with 4 RSA reps.  Even under an NDA they wouldn't
disclose what was lost.  They are still claiming that any association
between a customer and a seed record was not taken.  That is the one thing
I'm not sure I believe.

They wouldn't disclose what tipped Lockheed off to an intrusion.  That I do
respect since it is a 3rd party.  However, reading between the lines and
innuendo, I think they admitted it was NOT logs within the RSA servers that
illuminated the intrusion.

I asked how confident they were that the initial intrusion had absolutely
been eliminated.  The response was that they had mounted one of the largest
forensic and security review of a company ever, that had included experts
from "multiple 3 letter acronym Federal agencies"

I then asked what steps they had taken to protect the seed records from any
future successful intrusion.  They wouldn't state everything
(understandable), but in essence the seed record database and manufacturing
are now air gapped.

Replacement tokens will only be free if the tokens still have >12 months
service remaining.  Soft tokens will likely be fast.  HW tokens will be as
fast as possible and "if necessary, priority will be given to the defense
sector".

Now I just need to decide if I stay or bail.

On Tue, Jun 7, 2011 at 12:24 PM, Bill Humphries <[email protected]>wrote:

> http://www.net-security.org/secworld.php?id=11122
>
> get your new tokens...
>
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to