DigiNotar Goes Bankrupt After Hack
twoheadedboy writes "DigiNotar, the Dutch certificate authority which was recently at the centre of a significant hacking case, has been declared bankrupt. The CA discovered it was compromised on 19 July, leading to 531 rogue certificates being issued. It was only in August that the attacks became public knowledge. Now the company has gone bankrupt, parent firm VASCO said today. VASCO admitted the financial losses associated with the demise of DigiNotar would be 'significant.' It all goes to show how quickly a data breach can bring down a company."
Adds reader Orome1: "This is unsurprising, since a report issued by security audit firm Fox-IT, who has been hired to investigate the now notorious DigiNotar breach, revealed that things were far worse than we were led to believe."
Businesses have a strong profit motive. The people who run businesses are greedy. They will sacrifice everything, including security related expenses in order to boost profits in some way.
I think this is simply obvious.
How do you go bankrupt before any charges have been laid, fines levied, etc.? Sounds like the parent company ditching them before they can be held liable.
So, if certs cannot be trusted, and this brings to the surface the whole concept of "trust", what are we to do? What should we use?
And why exactly Comodo isn't on the same boat? "Too big to fall" works even worse for security as it does for economy.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
Not that it repairs the fuckup, or that anyone else will learn from it, but at least the incompetent got what was coming to them, just this once.
Their only asset, their presence in the browsers' trusted CA lists, has been eliminated. Without that asset, they don't have a product. A company without a product goes bankrupt eventually.
"It all goes to show how quickly a data breach can bring down a company."
Well, yes, particularly if what you are selling is security and trust. A CA has two jobs - generate a random private/public key pair, and make sure it is only used to sign legitimate certificates.
The first one anyone can do in two minutes, including the time to download GPG.
Most companies would be damaged by a data breach, but are unlikely to go under so quickly. It's that their only valuable asset - trust - was destroyed.
With major browsers kicked its CA cert out of the trusted list, the CA by definition and practically could generate no profit...
What else do you expect, huh? Of course it could only get closed!
This can't be allowed to happen. The company needs to be propped up financially by a government.
If companies like this go bankrupt from revealing security breaches, it hugely increases the chance that other companies will cover up security breaches instead of revealing them.
Then who can you trust?
Lesson learned: if you are a CA, under no circumstances should you allow any breaches to become public.
My favourite part of the article:
We have strong indications that the CA-servers, although physically very securely placed in a tempest proof environment, were accessible over the network from the management LAN.
TEMPEST http://en.wikipedia.org/wiki/TEMPEST is a method where you intercept EM radiation from a computer and use that to reconstruct some information about what that computer is doing. For example the US government could supposedly read CRT monitors from a fair distance away.
However, worrying about TEMPEST protection when you not only have those system connected to systems that are connected directly to the net, but use a single management username and password combo for your entire network is just insane. Even if the system wasn't connected to the Internet the freaking janitor could have placed a key-logger and had access to the entire system.
It is far cheaper to bribe one employee then spend millions setting up a modern TEMPEST system. I guess even the Dutch practice security theatre.
========
CINC, 4th Penguin Legion
Amusing that they comment about weak passwords being used on a windows domain...
Once you have the ability to crack the passwords, ie the hashes, it doesnt matter how strong or weak they are since you can simply use the hashes without cracking them.
This is what happens when you pay IT like shit and/or hire under-skilled workers. This is very common, because there is no respect for IT. People ask what I do for a living, and they here anything about a computer, and they think they are capable of doing the same. No other profession is downplayed as much as server administration.
DigiNotar got what it deserved.
However, the real problem stays: There are hundreds of CAs out, which are trusted by default by your browser. You probably never heard about most of them. They operate in different countries - you cannot sue them easily from your country. All of them can (technically) also issue certs for all Web sites (even for Web sites that have an existing cert from somebody else).
The whole CA system in broken. I would rather like to trust only CAs that have earned the trust. E.g. CAs that have been validated by my bank for online payments (but not for my email).
Because of the way the intrusion was handled, responsible people had to remove DigiNotar from their certificates entirely, rather than just a few suspect certificates. Therefore, they were bankrupt in effect long before they were bankrupt in fact.
Some say Convergence is the answer. I haven't been able to make it work, personally, so it's probably not ready for prime-time. Also, I don't like the name.
Belief is the currency of delusion.
We have strong indications that the CA-servers, although physically very securely placed in a tempest proof environment, were accessible over the network from the management LAN.
It is at once hilarious and depressing that there are tech and security managers who take steps to shield equipment from electromagnetic detection and then leave that equipment open to remote access. Wrap your computer in tinfoil and then stick your password on the screen.
It all goes to show how quickly a data breach can bring down a company.
Especially if you're a company whose sole raison d'etre is to promise everyone you won't have a data breach!
A taco stand probably needs to worry far less.
Not really. It does cost more than NO security but not much more. Example, how much does it cost you to have a decent password instead of Password1?
Yes and yes. But that isn't the core of the problem. Greedy people can have the best security. They don't want criminals to take their money.
In some case you are probably correct. In other cases the company/person will increase the security to keep the assets out of the hands of the criminals.
In my experience, the problem with security is Pavlovian. ...
If you do something insecure, once, and nothing bad happens
Particularly if it was just a little bit easier to skip the security. Such as typing in a 5 character dictionary word rather than a 16 character password. It doesn't take much to be "easier".
And as long as nothing bad is happening, people will "learn" that they're "secure" and what they are doing is "right" and anyone who is advocating real security just doesn't understand the situation. That's Pavlovian. The reward is the slightly easier administration.
If management does not understand real security, there aren't many ways to get them to change. They already KNOW they're doing it "right".
Hence all the recent cracks.
I'm just amazed that you were able to get that concept through their heads. I've been in similar situations where "let us not make this too difficult" trumps real security every time.
How much does a decent password cost? Nothing.
How much does NOT using that same password everywhere cost? Nothing.
Yet we constantly see cracks where the crappy password was used on multiple, critical systems.
would be 'significant.'
I think they are filing for bankruptcy while they still have money in their pockets to avoid law suites as opposed to gone bankrupt. I believe "gone bankrupt" means they are broke and giving up.
Having to work for a living is the root of all evil.
I have said so many times that we are not strict enough on punishment for the cyber crimes that affect companies, this should prove as a perfect example why certain individuals that bring down a company due to their hacking ventures, should face proper penalties.
can fix. Also amazing how complex CA authority has become. The concept is fairly simple, but the niceties of the trust bits have become so arcane that Mozilla is having to fix erroneous understandings of the bits in their own code, without breaking legacy. Then the people working on security code have highly resistant personalities and so all kinds of nonsense gets frozen in for years.They sort of have to be that way, to keep their code gov't certified... what a mess. Crowd-sourced verification of self-signed certs is starting to sound better & better.
The practical results of the way the code works at least at Mozilla were mystified complaints about the fake revoked Digninotar certs put in Mozilla to block real fake certs! That is not a model for the future. They are working on it, but it's glacial.
Monopoly €1000 certs, that's a not a biz model you can fix. Someday I will understand Slashdot editing.
Which cost money to implement.
Which requires that either the person volunteer his personal phone for that or that the company issue him a company phone that supports that.
Again, which costs money.
It's not that the users aren't smart. It's that management and the people setting up the systems do not understand security.
On most modern systems, it costs nothing to go from crap security (allowing 5 character dictionary words as a password) to better security (16 character passwords with some complexity).
The problem is that it is always easier to go with the worse security. No matter how easy you make the better security.
And every day you don't get cracked (or know that you were) is reinforcement of the bad security practices.
which was carried out by the hacker-soldiers of the government of Iran for the purposes of identifying the 300,000 Iranians that radical fundamentalist Theocracy wants to muzzle. In other words, state sponsored terrorism.
Running with Linux for over 20 years!
First off, I can easily remember my passwords. Even the ones that are more than 16 characters long.
Secondly, if you cannot, what's wrong with writing them down and keeping them in your wallet?
No. The point was that it will ALWAYS be easier for the user to ignore the security (if that is an option).
Even if "easier" is as minor as having a 16 character password instead of a 5 character dictionary word.
As others here have noted, once you introduce "easier" you end up with situations where the janitor has keys to the secure area because it is "easier" that way than to take the garbage out yourself.
Or, more currently, when the CA was cracked because there was one password (easily cracked) used on multiple servers.
Yes, having one easily cracked password on multiple servers is EASIER than having multiple, complex passwords.
But it is also insecure. As was demonstrated.
yeah, that was most interesting thing I took from it too.
I wonder where their newfound interest in computer security came from...
Getting hacked wasnt their problem. Keeping quiet about for more than a month untill it was found out by someone else there was the problem. If you cant trust the CA, then they are gone. The end. The whole point of these CAs is that they are TRUSTED to sign things properly. If the major browser vendors remove that trust, then there is n o reason for their clients to buy or renew their certificates with them, they may as well sign their own for free.