Why are security vendors faking digital certificates?

Davey Winder shares his thoughts on the tricky subject of using digital certificates

digital padlocks

Kaspersky Lab got in touch at the end of last week to say the number of untrusted digital certificates used to sign off malicious software had doubled in the last year, with its anti-virus database highlighting more than 6,000 of the things, just to put this into context. 

A little context is never a bad thing, as there are plenty of sysadmins who routinely trust digital signatures without any further investigation and are happy to install signed files on this flawed trust assumption, which is worrying. Especially when stolen or faked signatures have been used for donkey's years to fool users into thinking malicious files are the exact opposite. Remember Stuxnet, anyone?

There's plenty of evidence to suggest cybercriminals actively trade in stolen digital certificates within the dark market that exists online, and some (such as the Darkhotel folk) even appear to have access to the keys needed to create fake certs.

Kaspersky Lab suggests, quite rightly, that digitally signed apps from unknown software vendors are prevented from launching, and permission should not be granted to launch them without checking serial numbers and hash sums first.

Advertisement - Article continues below
Advertisement - Article continues below

It also recommends that certificates from unknown certification centres are not installed in storage and users' systems are kept patched (the Microsoft MS13-098 update will eliminate the error that allows additional data in the signed file without violating the file signature, for example).

There is a certain degree of irony in receiving this piece of security information from a security vendor, when you think about how security software (although I don't know if Kaspersky uses this method, but some leading vendors certainly do) analyses content for malicious activity from within a browser with an SSL connection.

The SSL has to be decoded on-the-fly, as it were, then re-wrapped and all in such a seamless way within the network layer that nobody knows. This is done, and here comes the irony bit, by squirting a Certificate Authority into your trust store and generating a 'fake' certificate for every site being visited and analysed.

It's clever, and web-content filtering is a must have if you want to stay protected, but using these on-the-fly certs added into the Root Certificate store in Windows and major browsers seems like being warned to watch out for what the bad guys are doing.

But, isn't it some kind of man in the middle attack, albeit that the man is wearing a white hat? Trust is a two way street, and mine is starting to get rather too full of potholes to negotiate safely.

Featured Resources

What you need to know about migrating to SAP S/4HANA

Factors to assess how and when to begin migration

Download now

Your enterprise cloud solutions guide

Infrastructure designed to meet your company's IT needs for next-generation cloud applications

Download now

Testing for compliance just became easier

How you can use technology to ensure compliance in your organisation

Download now

Best practices for implementing security awareness training

How to develop a security awareness programme that will actually change behaviour

Download now


internet security

Avast and AVG extensions pulled from Chrome

19 Dec 2019

Google confirms Android cameras can be hijacked to spy on you

20 Nov 2019
Business strategy

Adobe shuts down service to Venezuela

9 Oct 2019

Most Popular

data governance

Brexit security talks under threat after UK accused of illegally copying Schengen data

10 Jan 2020
Microsoft Windows

What to do if you're still running Windows 7

14 Jan 2020

Dell XPS 13 (New 9300) hands-on review: Chasing perfection

14 Jan 2020
operating systems

17 Windows 10 problems - and how to fix them

13 Jan 2020