Skip to main content

Does Older Mean More Secure?

It's an interesting thought.  Most operational security plans will promote the constant need for operating system and application software to be running the most recent stable release.  Patching and roll out platforms are big business and take up a significant portion of a system administrators time.  Keeping mobiles flashed, operating systems patched, router firmware updated and the IPS/NGFW/AV/Blacklist (delete as applicable) at it's most recent signature release, is a constant cycle of automation and checks.  But is it worthwhile?

A new release of any piece of software would (should) have gone through rigorous QA and UAT before being released and made available for roll out.  The maker of the said software will nearly always promote that the customer roll out the most recent release, as it makes their support processes easier to manage and getting everyone onto the same (or similar) version as soon as possible, helps with bug management and security issues.  This is a pretty fair assumption.  Unless you're an application vendor delivering a service via an online site where everyone uses the same version regardless, managing multiple versions of client software installed and configured on different platforms can be a complex process.

A newly released version or patch, on one hand fixes known issues, bugs and security loopholes, but is also open to newer attacks which have yet to be identified and patched by the vendor - the dreaded Zero-day scenario.  The other issue with newly released software, is that generally it will have fewer users, meaning that bugs and stability issues may still exist.  So whilst the chances of encountering a bug/security vulnerability or stability issue may increase in the short term, the speed and quality of a vendor response will likely increase.

But what if we look at this process from a few steps back?  What are the most attacked platforms and applications today?  Android?  Chrome browser? Flash or Javascript based vulnerabilities?  Windows 7 bugs and issues?  All are relatively recent developments, but are they attacked due to inherent flaws, or is it more likely because they're popular and well used?  An exploited vulnerability will have a bigger impact as the target user space is large.  So should we therefore all use unpopular applications, browsers and operating systems?

The strong argument for Linux based operating systems is that they are inherently 'more secure'.  Yes, the number of virus's is lower than say Windows and the basic approach to things like non-root running is a strong concept, but are they simply attacked less as they're used less?  How many Cobol and Fortran vulnerabilities are being identified and attacked?  Perhaps that is an unfair comparison as vulnerabilities for older platforms do exist and in the appropriate environment are identified, patched and make the head lines.

Sometimes security isn't about patching and controls though, it can be about doing things differently and counter acting potential attacks in a subtle and diversified manner.

(Simon Moffatt)

Popular posts from this blog

Customer Data: Convenience versus Security

Organisations in both the public and private sector are initiating programmes of work to convert previously physical or offline services, into more digital, on line and automated offerings.  This could include things like automated car tax purchase, through to insurance policy management and electricity meter reading submission and reporting.

Digitization versus Security

This move towards a more on line user experience, brings together several differing forces.  Firstly the driver for end user convenience and service improvement, against the requirements of data security and privacy.  Which should win?  There clearly needs to be a balance of security against service improvement.  Excessive and prohibitive security controls would result in a complex and often poor user experience, ultimately resulting in fewer users.  On the other hand, poorly defined security architectures, lead to data loss, with the impact for personal exposure and brand damage.

Top 5 Security Predictions for 2016

It's that time of year again, when the retrospective and predictive blogs come out of the closet, just before the Christmas festivities begin.  This time last year, the 2015 predictions were an interesting selection of both consumer and enterprise challenges, with a focus on:

Customer Identity ManagementThe start of IoT security awarenessReduced Passwords on MobileConsumer PrivacyCloud Single Sign On
In retrospect, a pretty accurate and ongoing list.  Consumer related identity (cIAM) is hot on most organisation's lips, and whilst the password hasn't died (and probably never will) there are more people using things like swipe login and finger print authentication than ever before.

But what will 2016 bring?

Mobile Payments to be Default for Consumers

2015 has seen the rise in things like Apple Pay and Samsung Pay hitting the consumer high street with venom.  Many retail outlets now provide the ability to "tap and pay" using a mobile device, with many banks also offer…

The Role of Identity Management in the GDPR

Unless you have been living in a darkened room for a long time, you will know the countdown for the EU's General Data Protection Regulation is dramatically coming to a head.  May 2018 is when the regulation really takes hold, and organisations are fast in the act on putting plans, processes and personnel in place, in order to comply.

Whilst many organisations are looking at employing a Data Privacy Officer (DPO), reading through all the legalese and developing data analytics and tagging processes, many need to embrace and understand the requirements with how their consumer identity and access management platform can and should be used in this new regulatory setting.

My intention in this blog, isn't to list every single article and what they mean - there are plenty of other sites that can help with that.  I want to really highlight, some of the more identity related components of the GDPR and what needs to be done.

Personal Data On the the personal data front, more and more org…