11/11/2008

Time to build an unique update process

Let us see the pc's and servers as camps we have to hold or conquer. So what do you do when you are under heavy attack ? You send in fresh troops and armements in the hope they will hold. But how can you make the PC's and servers immune if all the different new defences for each function of the PC have to come from different sources and have to be distributed in another way.

Why not say that all the anti-monopoly stuff against Microsoft had the negative by-effect that we can't set up a total-defense strategy and that we are every week scrambling to organise the updating of so many new applications and services on the PC that we don't know if it even matters anymore. The way this is going, you can as well, take all the documents and files off the computers and store them on highly secured installations and make every so many days a new image with all the updated software and re-install that. Otherwise how many antizeroday, code, vulnerability, upgrade and other defensive software and appliances are you going to buy, install and maintain ?

Maybe Microsoft should have the possibility to integrate other software updates in its update process. That process seems to work quite fine (if you remember how it was before with Microsoft and see how it still is with for example Joomla or Adobe).

The unsecurity of the weakest link breaks the strongest link.

19:06 | Permalink | Comments (0) | Email this | |  del.icio.us | | Digg! Digg |  Facebook

Post a comment