
Ooh la la! Horreur Wi-Fi en France! Some folks have experienced the drawbacks of Web 3.0 as their NFTs are stolen, and should computers own the copyright over the art they produce?
All this and much more is discussed in the latest edition of the award-winning “Smashing Security” podcast by cybersecurity veterans Graham Cluley and Carole Theriault, joined this week by Mark Stockley.
Plus don’t miss our featured interview with Sean Herbert of baramundi.
Show full transcript ▼
This transcript was generated automatically, probably contains mistakes, and has not been manually verified.
My name's Graham Cluley.
And our little dog, bless it — you have to imagine I'm running down the garden path.
The chickens are making all sorts of weird noises they've never made before, which is obviously just their way of saying, oh my God, there's a fox trying to pull us through the cage.
And you've got to imagine I'm running down the path, I'm basically dressing myself as I run down the path barefoot, and this little dog just runs into the darkness barking its head off to go and fight off whatever the thing is that's causing the chickens problems.
And whatever it is, the dog is tiny, so whatever it is is going to be 10 times bigger than the dog, and it just ran fearless at the problem. Aw, Daisy girl.
All this and much more coming up on this episode of Smashing Security.
So something odd was going on in Messanges, and the residents of Messanges. They were complaining. They were grumbling. Oh my goodness.
They were moaning to their mobile phone operators all the time. They're saying, for goodness' sake, why are our mobile phone connections keep on disappearing?
Why can't we get a signal? Why is not even the Wi-Fi working?
All kinds of problems, different times a day, recording the podcast.
You know, when kids come out of schools and they go on their video consoles or their smartphones, my internet disappeared. And I've now had to get satellite links via Starlink.
There's no problem at all." Which I have to say was the response I was getting from Vodafone on the many times when I made contact with them.
I mean, if you've ever worked in a company with an IT department, you will know that the front desk of the IT department's job is basically to find out why your problem isn't their problem.
And so these aggrieved residents of Messanges in southwest France, they called in the big guns. They called in the ANFR, the French Agence Nationale des Fréquences.
So for the last 18 months, I've been getting letters from the TV licensing people telling me you don't have a TV licence. Our van is definitely coming round.
And so they send me letters constantly saying, you don't have a TV licence. It's like, I do. I do. I want them to show up.
All I know is they apparently doorstop you and will try and come in and use many, many different techniques to try and enter the premises to do their checks.
But the thing is that every time I try and call them up or contact them electronically, ironically to say, "I do have a TV licence," I can't get through to a human to explain I do have one.
So I want them to come round because then they will stop sending me letters. Yeah, okay.
"What on earth is going on here?" So, can you locate the jammer?
Maybe it became stronger as he, you know, hotter, colder, you know, maybe, anyway. He had a little time on his hands.
Mon Dieu.
But by this point it was 1:30 in the morning. He couldn't go barging into the house. He had to return in the morning with a member of the gendarmerie to assist him, right?
You can't just go clouting in and saying, what on earth's going on?
He was fed up with his kids using their smartphones rather than sleeping at night. And so he had acquired a jammer to completely knock out all mobile phone signal.
And so he went on the internet as to how can I jam the signal?
And he now faces a fine of up to €30,000 and 6 months in jail as a consequence because—
So I think just owning one can actually give you a penalty.
But obviously he knocked out— and there's a serious problem because if you knock out the radio signals, if there were low-flying aircraft, for instance, it can apparently interfere with them and all kinds of things by just blasting out this really strong radio signal to drown out everything else.
So think Facebook, Amazon, things like that. Okay. So that's Web2 and exists broadly speaking, because people don't want to run their own stuff.
So everything is kind of centralized around Amazon Web Services and, you know, Facebook owns social media. Anyway, so that's Web2. We're going to talk about Web3.
I'm going to start my story with something that I think will tickle you, Graham, because I have noticed that there's nothing that you love more than a chuckle about an amusing name.
So I'm going to start my story with one of the best names in information security. Mr. Moxie Marlinspike.
He's also the former head of security at Twitter. So basically he's a man whose opinions about security and cryptography are worth listening to.
And on the 7th of January, he published an article that sort of beautifully exposed some of the nonsense that people say about Web3 called "My First Impressions of Web3." And because he's a very clever chap, he didn't just go and read about Web3.
He actually built some stuff. So he built some distributed apps and he made an NFT in order to learn about it, to sort of form an opinion.
And then his opinion is written in this article.
Because people don't trust companies like Facebook, Google, or Amazon and that sort of thing with their stuff. It's Web 3.
It's all built on blockchains, which are distributed, and so it's resilient and immutable and free from those large players that get to dictate the game.
So the paper's well worth a read, but the main argument goes something like this, okay?
So things that are decentralized evolve very slowly because you have to get everybody to do the same thing. You have to convince every individual they want to do the same thing.
And things that are centralized evolve very, very quickly. And if you want to win in technology, then you have to quickly.
And that is why people spend millions and millions of dollars on things like agile development and DevOps and DevSecOps and stuff like that.
And you may have noticed that Web3 is actually evolving very quickly.
And in fact, there's a layer of things underneath those webs and apps, which is also very, very Web2, in fact. And those are the things that are evolving.
It went from not having end-to-end encryption to having end-to-end encryption because all that needed to happen is that WhatsApp needed to decide that that was a thing.
Whereas with email, every SMTP server in the world and every email client in the world all had to adopt the same form of encryption, which is why it's really hard.
According to Marlin Smite, almost all distributed apps, which are sort of Web3 apps, actually interact with the blockchain, the distributed bit, by using just one of two services called Infura and Alchemy.
So they're these giant central points of failure, but also fantastic places to track people if you want to, and also quite useful places to attack if you wanted to.
So the whole sort of resilience from being distributed doesn't exist if you just channel everything through one gatekeeper.
Similarly, the Web3 poster child, you've probably heard of non-fungible tokens.
But I just want to dwell for a second on the fact that the decentralized Web3, in its nascent decentralized ecosystem, has a property worth $13 billion.
Anyway, not only is everything NFT-related, almost everything NFT-related flowing through OpenSea, but OpenSea is even filling in some of the missing functionality that doesn't exist in the slow-moving Web3 bit.
So some of the functionality around things like paying royalties.
Basically, some of the functionality that you think you're getting from the Web3 bit, you're actually getting from OpenSea, which means that your NFT is completely tied to the existence of OpenSea.
And in fact, because this is the upside-down world of NFTs, nobody can even agree if what happened was actually theft.
In the beginning, the rumor mill was insistent that the attacker had exploited a vulnerability in a new type of smart contract that OpenSea was asking everyone to upgrade to.
Because we're in that sort of weird Web3, Web2, neither one nor the other space, they couldn't just upgrade everyone.
They want everyone to upgrade, but they couldn't just upgrade everyone by pressing a button. And they had to get everyone to agree to upgrade their NFTs.
But because it's their kind of Web 2, it's like, okay, you have to upgrade your NFTs because it's distributed.
But if you don't upgrade your NFTs, you can't be on our website because we're the £800 gorilla and we get to decide what's going on.
And we've been spoonfed that for, I don't know, 5 years at least, you know, strongly. And at the same time, we're saying, yeah, but centralized is way faster.
So according to an analysis of the attack about a month ago, an attacker created a smart contract which was designed to steal other people's NFTs, and then they sent phishing emails with links to fake websites that told those users to sign a message that would help them to migrate to the new type of smart contract.
So I guess OpenSea must have trailed the fact that they were going to do this. But in actual fact, what those people were signing was a private sale of their NFTs to the attacker.
So they were effectively signing a Web3 blank check. People who send phishing emails these days, they're pretty good at fooling people.
And I'm not at all surprised that people fell for this, because as you say, it's all brand new technology.
So when OpenSea announced on their blog that users had a week to upgrade, the attacker executed the smart contract and that transferred ownership of all the victims' NFTs without payment.
And it pulled in about, as we said, between $0 and $1.7 million worth of NFTs depending on your valuation.
So some people are saying, well, why didn't they sort of try to freeze the wallets that were involved and stuff.
And as you will recall from our last conversation, stuff on OpenSea can all be listed automatically by bots and it gets sold if somebody— you know, there are bots looking for bargains, and if they think they find one, it'll just get bought.
So the expensive NFTs are gone. At first it was thought that there were 32 victims, there were 32 people who interacted with it.
There were actually 17 victims, so there weren't many people who were affected by this. But you know, there's 254 NFTs.
The most interesting thing about it though, for me, was the range of responses that you see.
So OpenSea itself and other sort of responsible players were very concerned with the affected users. You know, are they okay?
Because whatever you think of NFTs, those people have lost a lot of money. Not everybody was that kind.
Within the sort of Web3 culture, there's this idea that code is law, meaning that if the code allows a thing to happen, then that's perfectly okay.
And so if you're dumb enough to click, yes, I'm going to sign this blank check, then, you know, essentially all the people who are attacked gave the attacker permission to steal their NFTs, in which case was it—
And then there's a lot of, I want to talk to the manager. And suddenly the idea of a central authority becomes very, very attractive.
And then the other one, we have a sun-dappled train track covered with, I don't know, wisteria, vines, I don't know, stuff. Mm-hmm. Mm-hmm. So any thoughts on these?
And according to Artsy.net, they shorten the legalese in the US to copyright gives artists who have created fixed tangible works a bundle of rights.
The rights provide the artist protection and ensures the artist can profit from what they've made.
So for example, with a painting I did, I could create copies or create prints, postcards, whatever, and make them available to people for profit.
So if you bought it, that would not mean that you'd have permission to take pictures of the piece, make postcards of it, and sell my piece to anybody. Right. Okay?
So the painting of the train tracks is having trouble establishing copyright. And the problem is weird because we know who the creator is. We know that the image is an original.
We know that it exists. It's not just an idea or a thought, you know, an idea to do something in the future. And the problem is because the creator is not human.
Back in 2018, Stephen Thaler filed an application to register a copyright claim in this work, the work that I showed you, the train tracks.
And the author of the work was identified as the AI algorithm Creativity Machine. That's the name of the AI algorithm.
And Thaler listed himself as the claimant alongside a transfer statement of ownership of the machine. And the reason he wants to do this is for this concept of work for hire.
So you do work for a company, you make original work, and then the company owns that because effectively in your contract you're saying, yeah, you can profit from my work as an organization.
So effectively that's what Thaler was trying to get. He wanted to be able to, I guess, sell images of this wonderful painting or make money off it.
In his application, Thaler left a note for the office stating that the work was autonomously created by a computer algorithm running on a machine, and he was seeking to register this computer-generated work as a work for hire for the owner of the creativity machine.
Okay, so that all makes sense.
In 2019, a year later, the Copyright Office registration specialist refused to register the claim, finding that it lacks the human authorship necessary to support a copyright claim.
Okay. Now, we've kind of talked about this. You might remember that Banksy got himself into a similar pickle.
So he has images that a greeting card company basically took and started making cards to sell. And he was like, hey, those are mine. And they're like, well, who are you, Banksy?
You need to register yourself. We need to know who you are to prove that you own the copyright.
But because he was this kind of anonymous character, he wouldn't come forward and claim the works.
Therefore, they were just operating in this weird bubble because they were saying, Banksy, you can't go and complain about this by using the laws that you've complained about not to register any of your stuff.
We had a macaque who a nature photographer said grabbed his camera and took his own selfie. And then he was trying to make money off this picture.
And PETA went after him saying, how dare you?
You have infringed the monkey's copyright by releasing The Wildlife Personalities, the self-published book of photography that included the famous monkey selfie.
And he's not been successful.
So a few days ago, he was told for the third time, no, you can't do this, because they concluded that the work lacked the required human authorship necessary to sustain a claim in the copyright.
'Cause he provided no evidence or sufficient creative input or intervention by a human author in the work. So basically they're saying there's no human.
Because where's the evidence that Da Vinci or someone else like that— he might have just used a printer out or something.
I mean, I'm sure that's what's driving him rather than owning the actual copyright.
And then as soon as it develops the ability to understand money and use it, it can do something with the money it's earned. I've got a question for you.
If I make a pencil and then you draw a picture with the pencil, can I claim that the pencil is the originator of the artwork?
I don't know. I was thinking more like if it could get itself to the courthouse and argue its case.
For example, with Baramundi JOBS, you can control and monitor all tasks in the management suite, including software deployment, automation, and operating system installation.
Baramundi also offer vulnerability detection and patch management, so you're ready to deploy updates and patches for Microsoft and third-party applications.
And you can centrally manage any number of devices, no matter where they're located. And that means you can distribute all the necessary updates to smartphones, tablets, notebooks.
Excited to check it out? Well, we don't blame you. Our pals at Baramundi are offering Smashing Security listeners a 30-day full version free trial.
Check it out at baramundi.com/smashing. That's baramundi.com/smashing.
Kolide is perfect for organizations that care deeply about compliance and security but don't want to get there by locking down devices to the point where they become unusable.
So instead of frustrating your employees, Kolide educates them about security and device management while directing them to fix important problems.
Sign up today by visiting smashingsecurity.com/kolide. That's smashingsecurity.com/kolide.
Enter your email when prompted, and you will receive a free Kolide goodie bag after your trial activates.
You can try Kolide with all of its features on an unlimited number of devices for free for 14 days. No credit card required. Try it out at smashingsecurity.com/kolide.
That's smashingsecurity.com/kolide. Smashingsecurity.com/kolide.
It could be a funny story, a book that they've read, a TV show, a movie, a record, a podcast, a website, or an app. Whatever they wish.
It doesn't have to be security related necessarily. Better not be. Well, my pick of the week this week is a little bit sort of security related.
I switched on Netflix and I found a documentary, a lovely documentary about a beautiful romance of how a Norwegian woman working in London finds a guy on Tinder and she thinks, oh, I like the look of him.
So she swipes right, I think is the direction and it turns out that he is Simon Leviev, who is a wealthy jet-setting son of a billionaire diamond dealer.
It's oh, too good to be true. But she meets him for a lunch date at a posh London hotel, and he's romantic, he's funny, he's charming, he's very, very rich.
And later that day, she jumps into his chauffeur-driven Rolls-Royce and is whisked off in his private jet to Bulgaria. And it sounds like a beautiful romance.
But it's not actually a beautiful romance because things take something of a turn for the worse in this Netflix documentary, which is called The Tinder Swindler.
And I was watching it agog. My jaw was down on the floor going, oh my goodness. Why didn't I think of that? This is too much. Have either of you seen this? No. No.
Well, apparently it's quite popular on Netflix at the moment. I would recommend it, particularly if you're interested.
It was initially brought to my attention by a friend of the show, Ray Redacted, who tweeted about it.
Anyway, it is a story with plenty of twists in the tale, and it's quite astonishing what occurs. Is it worth watching? Yes, it is worth watching.
I think anyone who enjoys Smashing Security will enjoy the Tinder Swindler. So that is my pick of the week.
I don't know which one. I'm sure there's somebody out there that will enjoy this as much as I did. And so this is for you, whoever you are.
But the really wonderful thing about the internet and YouTube in particular is that whatever you are interested in, whether it is the effect of COVID vaccines and 5G mind control or insect herbivory, there is stuff for you.
And if you're into insect herbivory, there is a presentation by a guy called Thomas Dykstra, Dykstra with a Y. And he has rethought why insects eat plants.
He has rethought— this is his life's work, right? Is to research why do insects eat plants. And his conclusion is that insects only eat unhealthy plants.
And different insects eat different plants based on how unhealthy they are.
So if you've got locusts eating your plants, then your plants are healthier than if you have got scale insects eating your plants.
And basically there's an hour and a half of this stuff, and he goes on to explain why if he's right, then kind of everything we think we know about insects is wrong.
And it has all sorts of interesting things to say about—
And he's done another presentation where he talks about citrus growing in Florida, because there are records going back over 100 years.
And he sort of charts the decline of the citrus industry in Florida through the different waves of insect attacks that have happened to it.
But, you know, there are probably only 3 of us in the world.
So my pick of the week actually comes from a rock-solid recommendation from my mother-in-law, and it's a TV show or a documentary on iPlayer called Eye of the Storm, and it's on for the next 8 days only.
Okay, so it's a documentary of acclaimed Scottish artist James Morrison. He was born in 1932 and recently passed away at the start of the pandemic.
And near the end of his life, the BBC spent two years with him, you know, on and off documenting his last days as a painter.
He is an extraordinary landscape painter, and a lot of his work focuses on skies. I sky work as well, so— and I really love his stuff. It's sublime.
And you'll see many, many of his works in the documentary. But what's just so heartbreaking is that he's losing his sight.
And he is becoming, you know, he's 92 near the time of his death, right?
So he's getting weaker and weaker, and he can no longer go outside and paint, which is what James Morrison did most of his life. And he can't see as much.
And, you know, there's all these talks of, you know, Matisse used to have to paint on the walls from bed when he was too weak to get out of bed, or Monet continued painting even though he lost his own sight, or Beethoven composed while deaf.
So it's a beautiful way of someone coming to terms with losing the thing that they love most. And I found it touching, but also very beautiful.
So it's called The Eye of the Storm on BBC iPlayer. And it's a story of James Morrison, Scottish painter.
He's Baramundi's UK Country Manager and a trusted advisor when it comes to managing and securing organizational networks from threats. Thanks so much for talking to us, Sean.
Thank you very much for having me. So first, maybe we should start with you telling us about Baramundi, a name I love to say, by the way. It just rolls off the tongue so beautifully.
Hey.
We're a unified endpoint management provider, so it's all about the control of all of your endpoints in your environment, regardless of where they are.
You know, first step to being able to control or secure anything is knowing where it is and what's actually out there. And that's fundamental to what we do.
And within it, we're a modular setup.
So there's plenty of different bits and bobs, whether it be inventory, deploying of software applications, patch management, vulnerability scanning, MDM, all of that is within the UEM scope.
And that's what we do at Baramundi.
Well, you know, that's— and that's a very quick and easy way of measuring the worth of a company is how they treat their employees during what can fundamentally be the hardest times.
And Baramundi really, really excelled at that. There was no furloughs, nothing. It was just, you know, push on forward.
So maybe we can talk first about patching vulnerabilities because it remains a key vector for much of the bad stuff that's hitting us.
And I'd love to know what your take is on this issue.
And a lot of the time, those gaps are advertised, you know, patches aren't secret and the vulnerabilities that they are patching aren't secret either.
So as an entry point, they become a lot easier as an attack vector.
And I've always looked at patching as the fundamentals, what you should be doing first and foremost before you're doing anything weird and wonderful on top of that, or particularly massively innovative from a security standpoint.
If you have all of these incredibly innovative products and you're not doing the bare basics like patching, for instance, it's essentially like leaving the house, turning on the lasers and CCTV camera, but leaving the front door unlocked and wide open.
That's essentially what patching is — lock the windows, lock the doors before you're even thinking about anything else.
But essentially, it's to what degree they're doing it that really differs across different companies.
Now, what you tend to find is the bare minimum, or you'd hope the bare minimum, is that people have auto-updaters on.
And I say bare minimum because it's not what I would consider best practice by any stretch of the imagination, but patching something is better than patching nothing at all.
But you find a lot of companies are using WSUS and handling the Microsoft side of things.
But what tends to get overlooked a lot of the time is the third party patching world, the Adobes, the Googles, the Javas of the world, which are consistently adding new patches to the vulnerabilities that are found.
And that really counts towards things like the Cyber Essentials framework and those sorts of things that people really need to have in place.
So, do you feel that C-levels really force this issue home, talk to people about patch management and kind of say, what's going on? What are we doing here? Talk to me about it, guys.
Finance, sales tends to be where the CEOs lay, and certainly the CFOs who are holding the purse strings a lot of the time.
So being able to communicate why you need toolsets in place to be able to do these things, that can be difficult.
Myself, I'm lucky enough to understand the requirement for patching and the requirement for good tools to be able to help to do that.
But being able to translate that to language that is understood by somebody who's essentially not a techie for something that is also essentially not particularly sexy.
It's not a super sexy thing to talk about the patching aspect. You know, it doesn't light people's hearts up and that sort of thing.
So finding a way to be able to communicate that effectively to those people who aren't techies is key.
I've done speaking slots in the past at places like DTX or IP Expos— it used to be— and I really put an onus on trying to do that as well.
So putting different scenarios in people's minds to be able to understand it, not just the C-level, but also for those techies, those IT managers and those network admins to be able to understand that actually I need to frame this in a way that somebody who isn't me, who isn't qualified the way I am, understands it.
So I've done talks where I've likened it to the Death Star. Oh, really? How do you do that? Talk to me. Essentially what I did was remind people of the story.
Now, most people in the tech world, I'm sure, don't need to be reminded of the story of the initial Star Wars, where the Empire built a big old weapon that was designed to destroy planets, but the designer created a flaw in that, and those designs were stolen, and the rebels then were able to manipulate that flaw in order to then destroy the weapon.
Then relating that to actually what could the Empire have done better to ensure that these things wouldn't have happened.
So it's looking at things like employee actions, control of assets out there, audits, reporting on the things that they're doing, learning from their mistakes.
I mean, they went and built a second Death Star and left this one with loads of gaps open and just stuck a shield around it.
It's trying to relate it in that way to say, if they'd only patched up that small hole in that exhaust valve, then the first Death Star would have been out there.
And who knows, the empire could have still been going to this day, he says, living in a fictional world in his head.
So it's trying to frame it in those sorts of ways where people think.
And not necessarily take that scenario and go and speak to your CEO about it, but understand that you need to frame it in a way that they will understand, get on the same page as them, and be able to— if you're going to talk to the CFO, talk to them about why it's important from a costing point of view, what saving is what's that investment then later going to make to them?
From a CEO, obviously, it's mitigating risk and those sorts of things to ensure that the company isn't then held accountable for being hacked or whatever it may well be.
So if the CEO is a car buff, or the CEO is into any sport or any hobby, you could apply the kind of moral of the story of we need to lock everything down in order to stay, you know, to lower our risk, in a way that they exactly right.
And you could say, well, that's like patching and making sure there's no vulnerabilities that people can take advantage of. You can apply it to pretty much any situation.
I've done it with, like I say, the Death Star, Independence Day.
I did one that was speaking about the whole UEM and Unified Endpoint Management suite and how that relates to things like the Fellowship of the Ring and how different people relate to different modules and what they did.
And not only is it useful for them to be able to then translate that and talk to their C-levels, those who hold those purse strings, but also especially at events, whatever it may well be, InfoSecs of the world, a lot of the time you're sort of pummeled to death with tech demos and tech speak.
And sometimes it's nice to just have a little bit of a reprieve from that and be able to take a moment to have a bit of fun with it and have a smile on your face.
The metaphors aren't going to work every single time with these sorts of things, but people tend to be very forgiving with that sort of side of things when it's an enjoyable presentation at least, and the key message is being delivered.
People gathering around the hearth to share stories about their lives and all that sort of thing.
It was what was fundamental to us as human beings, to be able to relate anything out there, especially if you don't understand it, to a story, to a metaphor, or to a simile.
I think our brains are just made to do that.
Is there some key takeaway of why it's important to look at your patches and your patching vulnerability?
One, first and foremost, it's the easiest thing to get sorted.
There's plenty of tools out there that do it, none as good as Barramundi, obviously, but there's plenty of tools out there that you can do it.
And even if you're doing the bare minimum, as I say, auto-updaters or using WSUS or whatever it is, Windows Update Online, all of those are providing patches.
There's really no excuse for you not to patch something at least within your environment. And it's a big tick in the box.
If you take away local admin rights and patch your environment, you're mitigating a lot of the risk within your environment straight off the gate.
Because as I said, those who are looking to infiltrate your system, they don't want to sit down and write the most complex hack in the world.
I mean, some people take joy in that, but if they're trying to make money out of the situation, then they're going to want to do it in the easiest way possible.
And in order to mitigate that is to take away those easy routes in, lock your doors, lock your windows before you leave the house and turn on the cameras, the lasers, the smoke detectors, the movement detectors, etc.
So that's what I'd say.
You guys can get your free copy at baramundi.com/smashing, and that's BaraMundi, B-A-R-A-M-U-N-D-I. It's great. Yeah, just note not two Rs because then it is a fish.
Covers off the capabilities not only within the suite, but also just general best practices for vulnerability scanning and patch remediation, which both of which can be handled out of the BaraMundi UEM suite.
Which actually sets us apart from a lot of other products out there.
A lot of the time when you're looking at the vulnerability status as when it is applied to the patching status, a lot of the time these patch providers say, oh yeah, you've patched up to date with all of the content we provide, therefore you're not vulnerable.
Yeah, you know, that's falling short of the mark somewhat because no patch provider can provide every single possible patch you might possibly need within your environment.
So that's why we took it a step further with having a vulnerability scanner alongside that to compare your environment with a huge portfolio of CVEs and CCEs to say, great, you've patched up to date with all the content we provide you.
However, outside of that, these vulnerabilities still need addressing. So go out and manually get them or take remedial action as you see fit.
Or sometimes there's no patch available for some of these CVEs or vulnerabilities that are found out there.
So, you know, rolling back to a previously known good state, uninstalling, whatever it may well be, at least you are aware of your vulnerability status and able to take action as a result of that.
And we think that's key and fundamental to being able to secure your environment.
You know, it's, like I say, there's no excuse really to not be patching, especially the Microsoft stuff. So you should absolutely be doing that.
Don't be the person caught out and say, oh, well actually we got infiltrated by XYZ malware because we didn't patch this vulnerability within, you know, within Microsoft.
WannaCry was, you know, the big key one many, many years now.
We're looking back where that was exactly the case where the vulnerability was discovered and the patch released for it, I think in February of the year.
And then the vulnerability or the way to take control of that vulnerability or to access that vulnerability was then released in April, and then the WannaCry situation happened in May.
So there was almost a two-month gap between patch happening and then the WannaCry situation happening where— Preventative measures could have saved the day. Exactly, exactly that.
And again, you can get your free copy of this white paper called Automatically Detect and Quickly Eliminate vulnerabilities at baramundi.com/smashing.
And all I have to say now is may the Force be with you, Sean Herbert.
And don't forget to ensure that you never miss another episode by following Smashing Security in your favorite podcast app.
For episode show notes, sponsorship info, guest lists, and the entire back catalog of more than 261 episodes, check out smashingsecurity.com.
Hosts:
Graham Cluley:
Carole Theriault:
Guest:
Mark Stockley:
Show notes:
- Les dents, le brouilleur et au lit! — ANFR.
- Dad takes down town's internet by mistake to get his kids offline — Bleeping Computer.
- My first impressions of web3 — Moxie Marlinspike.
- Graham or Carole? – NFT for sale — OpenSea.
- $1.7 million in NFTs stolen in apparent phishing attack on OpenSea users — The Verge.
- Art Copyright, Explained — Artsy.
- The US Copyright Office says an AI can’t copyright its art — The Verge.
- Ruling on "A Recent Entrance to Paradise" — Copyright Review Board.
- Appeals court blasts PETA for using selfie monkey as ‘an unwitting pawn’ — The Verge.
- 'Monkey selfie' case: Photographer wins two year legal fight against Peta over the image copyright — The Independent.
- What I Wish They Taught Me about Copyright in Art School — Library of Congress.
- Who is Banksy and why did he lose the trademark for four of his most famous works? — Sydney Morning Herald.
- The Tinder Swindler — Netflix.
- You Can’t Make This Up: The Making of a Swindler (Part one) — Podcast going behind the scenes of “The Tinder Swindler.”
- Why insects do not (and cannot) attack healthy plants — YouTube.
- Eye of the Storm — BBC iPlayer.
- Smashing Security merchandise (t-shirts, mugs, stickers and stuff
- Support us on Patreon!
Optimize your IT processes with the baramundi Management Suite and make optimal use of resources by automating time-consuming routine tasks.
Stay in control and maximize your productivity by automating routine tasks. The Unified Endpoint Management Software can be installed and implemented quickly, is intuitive to use, has a modular structure and offers a high level of usability and transparency.
Try out the free 30-Day full version for yourself today at baramundi.com/smashingsecurity
At Kolide, we believe the supposedly Average Person is the key to unlocking a new class of security detection, compliance, and threat remediation. So do the hundreds of organizations that send important security notifications to employees from Kolide’s Slack app.
Collectively, we know that organizations can dramatically lower the actual risks they will likely face with a structured, message-based approach. More importantly, they’ll be able to engage end-users to fix nuanced problems that can’t be automated.
Try Kolide Free for 14 Days; no credit card required.
Follow the show:
Follow the show on Bluesky at @smashingsecurity.com, on the Smashing Security subreddit, or visit our website for more episodes.
Remember: Subscribe on Apple Podcasts, or your favourite podcast app, to catch all of the episodes as they go live. Thanks for listening!
Warning: This podcast may contain nuts, adult themes, and rude language.


