Reblog. Original (Nexor.com)
High Assurance products are needed where information or networks need to be protected from high end threat actors, and you need a high level of confidence that the solution will mitigate the risk.
Reblog. Original (Nexor.com)
For the last few years, the cyber security commentary has been if you focus on the basics, and do the basics well, you will prevent 90% plus of cyber security attacks. To many this has been interpreted as doing the “Cyber Essentials”.
Then the SolarWinds / Sunburst attack occurred. Doing Cyber Essentials will not have prevented this. This was one of the 10% attacks. So, is Cyber Essentials dead?
Reblog. Original (Nexor.com)
A CISO – Chief Information Security Officer – at an SME is responsible for security operations, securing the business, its technology, and its initiatives, and leading the business’s information security strategy. A CISO must liaise with different areas of the business including IT, HR, and C-level executives to ensure that their objectives are achieved.
There is no such thing as a typical day in the life of a CISO, but some activities are more common than others. The following breakdown gives you an idea of what to expect from a CISO, though each day will look very different.
Cyber Security Marketing – Please read your own messages?
I just received a marketing email entitled “Your Complete Guide to Phishing”.
All I had to do to get the guide was…
Oh the Irony. “Learn how not to click links and provide details, by clicking this link and giving us your details.”
If we are to protect people from mass phishing attacks, our industries marketing needs to do better.
When looking at commercial or consumer products how often do you seen the phrase “military grade security”, very often as the only nod to the security of the product?
The phase tells me two things.
So I won’t buy your product.
By saying “military grade security” you probably mean you have implemented an algorithm such as AES. This is not knocking AES, it’s a great algorithm, designed to protect routine confidential information. Yes, it may be used by the military to protect routine stuff, but it is not used for anything they consider particularly sensitive – in today’s climate they will, also certainly be using high-grade, quantum safe algorithms.
Algorithms such as AES are perfectly suitable for commercial grade products – but I don’t care. Rarely do security attackers break the encryption. They break the passwords or keys used by the encryption – it’s much easier to do! Alternatively they find a weakness in the software to gain access to the unencrypted data.
So please don’t tell me you use military grade encryption. Instead, please tell me how you protect the keys used, and the quality controls mechanisms you use to verify the software.
Reblog. Original (Nexor.com)
The term ‘Zero Trust’ was first coined by John Kindervag in 2010, building off a concept put forward by David Lacey at the Jericho Forum, an international group founded in 2004 that worked to promote deperimeterization.
Deperimeterization means to “protect an organisation’s systems and data on multiple levels, by using a mixture of encryption, secure computer protocols, secure computer systems and data-level authentication” (Wikipedia). Our Managing Security Consultant, Colin Robbins, has been discussing deperimeterization for over 5 years.
Over the past few years, the world has seen a period of digital transformation. The increasingly popular use of Cloud-based solutions and remote working are eroding traditional security boundaries. Network architecture is changing, as static work environments are being phased out in favour of letting employees work from any location at any time.
In this new world, the role of local networks and Intranet changes, it no longer poses a significant security boundary, as business data is now outside of that network on cloud services. Thus, the priorities of the local network have shifted to providing access, not security. The need for security has not been diminished and a replacement solution must be found – this is where Zero Trust fits in – it helps provide confidence that your users and devices are appropriately trusted to be able to access your (on premise and cloud-based) services.
Zero Trust is a term being (mis)used by some product vendors, to push their unique angle on it. To cut through this, the NCSC, along with techUK, are working toward a non-partisan view of the base principles.
As part of this, the NCSC has developed a series of principles that will help people understand and migrate to a zero trust architecture. These principles are still in development and they have recently reduced the 10 alpha principles down to 8 beta principles.
Like many, during lockdown I’ve been catching up on a number of Webinars. It’s given me the opportunity to do some catch up in the Identity Management field.
During the EEMA annual conference, a distinguished speaker observed “We are in danger of re-inventing the wheel, without learning from the past”, which caused me to reflect on the identity lessons from my identity management past. (Apologies to the speaker, I forgot exactly who made the comment).
My first reflection is:
Which is where the conundrum lies – the “next generation” see the current solutions as hard to deploy, and think there must be an easier way, and sure enough come up with an idea for “easier technology” – get momentum, then stall because scaling and deploying it is hard!
My second reflection is there are three domains of identity:
These are fundamentally different things, with different requirements and challenges. Don’t let your “solution” confuse them – you will fail. Yes, there are common technologies that will play a part, but the scalability and deployment challenges are fundamentally different.
My third reflection, I’ve probably been in the game too long to offer new solutions, it is time for the next generation – but please do study history, the challenges are not new.
The continuing Covid-19 house clearout led to me finding a pile of business cards…
|The first card, from 1990.
An X.400 email address, did anyone every think that would really catch on? Looks like we ran our own PRMD, unusual for a small business.
I wonder why our current meeting room is called the Enterprise?
|Steve joined the company and we started to bring a bit more colour into the re-designed logo.
Interestingly (for me anyway) is the ‘A= ‘
(yes that is a single space character after the = sign, if you didn’t put the space it would not work.)
|Whoops, time to change the name from X-Tel to Nexor (another company with a very similar name and logo noticed us, and the lawyers had a friendly chat!)… but we kept the same “look and feel”
Who were Mark400?
|Growing up in the World – a change of address as we moved off the university campus.
As well as turning sideways, looked like we changed X.400 ADMD service providers.
No Web address?
|By the time we moved to Rutherford house, looks like we had removed the graphics from the logo, and straightened the italics.
Looks like X.400 died, as did Nexor.co.uk, and we became a .com.
|In a word, ‘the pink era’…|
|Gosh, the scanner really can’t cope with the grey header.
LinkedIn made an appearance
|Initially available as black on white, but quickly changed.
Twitter makes an appearance.
If you have a black on white one it has rarity value – please send me an image!
|Bringing it right up to date.
Seem’s someone didn’t like the icons.
Twitter has taken a backseat too.
How many of these do you have in your collection?
This month marks 20 years since the ILOVEYOU virus hit computer networks. For me, it represented a milestone in my security career. Up until that point security was a technical challenge, solving challenges associate with the global distribution of public keys for secure email exchange. (Aside, I’ve blogged on this many times, it is a challenge still not resolved in a usable way today).
My first exposure to ILOVEYOU is when the Nexor CEO came into our office confessing he may have clicked something, and his computer was now behaving strangely. The remedy was fairly easy, disconnect from the network and rebuild the PC. To be honest, as a technologist, it was quite exciting at the time, seeing a real live virus in action.
The learning was more important. Security was about far more than technology. It’s also about people and process.
I could go on about how the CEO should not have clicked the link, but the last 20 years have shown those links will still be clicked no matter how much education we try. Don’t get me wrong. Education is still vital and will reduce the number of incidents, but incidents will still happen.
The more interesting part of the 20 year old incident, was the learning around incident response. We were able to contain the incident, be we (sort of) knew what were doing and took no risks – we went for a rebuild, despite the inconvenience to the CEO. What we had unwittingly created was an early example of an “incident response plan”. This was about process and relatively simple technical steps (rebuild a PC) and some post event briefings. It was not long after that I started to understand where emerging standards like BS7799, which became ISO 27001, fitted in the over all security story.
This month, 20 years later, I’ve just briefed on of my team who is creating an incident response plan for a customer. Who would have thought such a simple incident would have direct relevance 20 years later!