SANS ISC: GlobalSign back in operation - SANS Internet Storm Center

• SANS Site Network
  • Current Site
  • SANS Internet Storm Center
  • Other SANS Sites Help
  • Graduate Degree Programs
  • Security Training
  • Security Certification
  • Security Awareness Training
  • Penetration Testing
  • Industrial Control Systems
  • Cyber Defense Foundations
  • DFIR
  • Software Security
  • Government OnSite Training

SANS ISC InfoSec Forums

Fellow handler Lenny wrote about GlobalSign being named by a hacker claiming the DigiNotar and Comodo breaches and GlobalSign's response to it by stopping the processes of issuing certificates.

Today GlobalSign should be back in operation and they have kept a public track of their incident response. I suggest to read it bottom up as that way you get the timeline.

I see a number of very good ideas and actions in there. First off they stopped issuing certificates right after the claim, that's the containment you see in action: make sure it does not get worse. In fact if you look back at what's known so far of the DigiNotar case, had DigiNotar done that on June 19th when they detected the breach the first time, and then would have done a complete technical audit of their systems, DigiNotar would today not have had their entire reputation thrown away. Next GlobalSign contracted Fox-IT, the same company that has been/is analyzing the systems of DigiNotar.  The value of having somebody who's been dealing with similar incidents can more often than not proof to be invaluable.

I also see one worrying issue, and that's that their web server (the one serving www.globalsign.com) has signs it has been breached. GlobalSign claims it has always been isolated though.

Over the past few weeks we've had a number of request of GlobalSign customers that were wondering if they should migrate to other providers.

Let's analyze with what we know now:

• There is the anonymous claim of a hacker that he's hacked Comodo, Diginotar, GlobalSign and 3 more unnamed CAs.
• The hacker gives as proof a calc.exe signed by the by now well known rogue *.google.com certificate from the DigiNotar breach. It does proof somebody has the secret key that goes with the certificate, but it doesn't proof he's the one doing it all.
• From what we publicly can see, GlobalSign is reacting properly to it all.
• If you would change providers you risk changing to one of the 3 unnamed ones.

So what's smart to do ?

• Be ready to switch to another provider if you need to. Being ready can be done to different levels, but one can start with selecting (or setting up criteria), etc. This would be needed in two cases:
  • your current provider looses trust from the world at large (what DigiNotar did), or
  • your current provider sees itself compromised badly enough that it revokes its own intermediate certificates (what DigiNotar should have done) while it stopped issuing new certificates.
• If I were a GlobalSign customer, I would not migrate away from GlobalSign as it risks I'd end up with one of the 3 unnamed ones and be in a worse condition than I'm now.

--

Swa Frantzen --

Section 66