Skip to main content

Information Security: Time for a Different Approach

This last few weeks have seen, yet again, some pretty significant hacks (namely the Evernote hack).  Large amounts of user data, including passwords, were released into the wild.  The situation could have been worse in the Evernote case, but at least the passwords were salted and hashed.  Evernote's response, has been to perform a mass password reset on it's user base, in a proactive damage limitation style exercise and no doubt several internal streams of investigation will be looking for the who, what and why behind the attack.

Security is Reactive
I've blogged on the topic of reactionary security on a few occasions recently ("Protection Without Detection", "Preventative -v- Detective Security") and it seems the approach is still pretty much the default  (Or perhaps security is only really questioned and tested after an event?).  There are of course, lots of 'pro-active' components to security.  Hashing a password could be seen as one for example, but many of these activities are often small tactical steps at the implementation level, not the strategic level.  Audit is obviously detective, with an audit response proactive in some sense, but really only proactive to get you back to the status-quo of reactive.  Big data for security, ("Security Analytics: Hype or Huge?", "Big Security Data to Big Security Intelligence") is another example in my mind or purely reactive security.  The big data promise is based entirely on scale and speed.  Scale obviously (the word big might help there), with regards to aggregating and correlating multiple data sources and speed, for trying to develop queries and analytic steps to identify root causes, patterns and so on.  Longer term, the results of the big data analytical steps could of course be proactive in nature.

A Different Approach
In my mind a different approach is needed.  I'm not advocating what that approach should be, but the panacea would of course be to get security so embedded, it seamlessly integrates with revenue generating business focused practices within an organisation.  The gap between security and convenience, needs to be minimized to as close to zero as possible.  Security really needs moving up the organisational food chain, away from the bigger, faster, shiny implementation level approach, which will constantly chase (and lose) an attackers tail, to be a default stance with all business related policy decisions.  This is difficult of course, but in the longer term will help move away from a reactionary standpoint to something resembling security by default.

@SimonMoffatt


Popular posts from this blog

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…

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.

Online-ification: The Role of Identity

The Wikipedia entry for Digital Transformation, "refers to the changes associated with the application of digital technology in all aspects of human society".  That is a pretty broad statement.

An increased digital presence however, is being felt across all lines of both public and private sector initiatives, reaching everything from being able to pay your car tax on line, through to being able to order a taxi based on your current location.  This increased focus on the 'online-ification' of services and content, drives a need for a loosely coupled and strong view of an individual or thing based digital identity.