
Join me and fellow computer security industry veterans Vanja Svajcer and Carole Theriault on the “Smashing Security” podcast, as we have another casual chat about the world of online privacy and computer security.
Show full transcript ▼
This transcript was generated automatically, probably contains mistakes, and has not been manually verified.
Hello and welcome to another episode of Smashing Security, episode 8 for Thursday the 16th of February, 2017. And I'm joined by my chums. Hello, chums.
And a lot of security firms, they sort of save up their research or they say, oh, we've discovered something new and come coincidentally, it's just during the RSA show when there'll be lots of security journalists around to talk about it.
So quite often there's a bit of a drought just before the RSA show and then it all happens this week.
Basically, NSS Labs have tested CrowdStrike's product, and CrowdStrike aren't terribly happy about that.
They haven't been very happy with the testing methodology which NSS Labs uses.
And, you know, to be fair, I think both companies have sometimes been embroiled in some controversy, both the testing agency and the security firm as well. So who knows who's right?
But CrowdStrike went to the courts and tried to silence NSS Labs. And what a fantastic way to give it an awful lot more attention to a test that you didn't want people to read.
The best way, in my opinion, to go around or against this is yes, some tests are this, but we also have a list of other reputable testers that tested our products, and here are the results that are so much better than in this case.
And if you're not in the industry, how are you supposed to tell which ones are good and which ones are bad?
But I think there will continue to be a lot of antagonism between security companies and testing agencies, or at least some of the testing agencies and some of the security companies for some time to come.
Going forward, topics for this week. I've got something I want to get off my chest right now, and it is Donald J. Tru— can you guess?
Now, we know that Donald loves to tweet, right?
Oh, actually, you know, he has a very active Twitter account, but it's interesting, he has said in the past that he doesn't actually tweet very much himself.
And there was some digging around done by Android Central, who did a little investigative work. They took a close look at some photos of the US president.
And there he was holding in his little paw, his Android phone. And they sort of, you know how it is on CSI and things like that, right?
Where you enhance the picture, you blow it up to try and work out what kind of phone is that. So it's like enhance, enhance.
And of course that is not the latest and greatest version of Android. It isn't patched against all of the vulnerabilities.
It may not be considered necessarily a terribly secure phone if— and I have to stress if— someone was determined to get into it.
I think they've learned from some of that in the past, but there is a worry that if there's a poorly protected phone being held by the US president, is it possible at all that some people might want to target that phone?
Maybe, as he is the US president, right, maybe he can say, 'Look, I really like this old handset, but I really want the upgraded version inside. Can you make that happen, please?'
Here we go again at RSA this week.
Google security engineers stood up and said, look, yes, we've had huge vulnerabilities like Stagefright, but they're saying nobody ever actually got exploited by that.
You know, they've seen no evidence.
And many times we criticize at the security companies, criticize Google about all the insecurities in Android and the number of malware that's out there. But they always deny it.
They basically deny any kind of malware.
I mean, huge amounts of malware for Android, although much of it may be based around downloading apps from Chinese app stores or unapproved apps.
Google Play, you get a campaign here and there, some malware, some annoying adware happening, but—
But even if you accept Google's claim this week that even though Stagefright was a huge vulnerability on Android, people weren't getting exploited on it, you've got to say to yourself, well, maybe that's true, but what about targeted attacks?
And that's where Trump comes in, right? Because he has to have in his little pool there one of the most widely prized devices on the internet for hackers.
He's going to be a top target for intelligence agencies around the world.
So if that device is vulnerable to bugs like Stagefright, it doesn't matter that millions weren't infected by Stagefright, he could be at risk.
And that is why, I imagine, this week we've had two senators, admittedly Democrats, who've written to the Department of Defense saying, we want details. Has he got this phone?
Has it been properly secured? What's being done to make sure that the phone the president is using has not been compromised in any fashion and is not being spied upon?
If nothing else, we want to know that those tweets that are being sent out really did come from the main man in charge and not some hacker, because sometimes it can be a little bit hard to tell who might have done the tweeting.
You can't necessarily tell from the tweet itself, right?
Guys from Kaspersky were working on one of the incident response processes on one of the banks, and they discover this truly interesting piece of malware or an attack they used.
The attackers used malicious code, which actually hasn't existed as a file on the computer. So we are talking here about so-called fileless malware.
And some of the news sites picked it up as a very important story.
So typically, a malware which comes to your machine as an attachment or somewhere from the web comes in the form of one of the files.
So many people believe, I think still, that anti-malware companies are only scanning files and nothing else.
So they only inspect files when the files are created and when the files are open.
So there's this idea that if you create a malicious code or you have malicious code which doesn't have a file on the hard drive or on the computer, you'd be able to evade all detections that's out there.
But this is really, you know, Graham, you remember Code Red?
So the idea, I remember we were shit scared at the time because as an anti-malware company at the time, we really inspected only files.
The only way to stop it at the time was just to recommend everybody to apply the patch as soon as the Microsoft came out with the security patch.
So since then, you know, it was a long time ago, there were other types of malware that appeared as fileless malware.
There's some kind of organized, possibly country-sponsored groups that use those kind of malware.
But there are also typical information-stealing malware that can come to your machine without a file.
When they say without a file, there's still a representation of that malware on the hard drive and in the memory.
So usually the malware uses registry, which is a database on your Windows machine that contains a lot of settings for all the applications.
And it also allows some programs to run as soon as you boot the machine.
I think the guys from Kaspersky were stressing the fact that they find this in banking IT departments or banking sites.
And they were saying that banks perhaps are not equipped to deal with this kind of attack yet.
However, you know, most of the endpoint protection software these days can and does inspect memory and registry.
And of course, doesn't just work on inspecting the content, but also the behavior of the system.
So, you know, it's pretty much your everyday work for anti-malware companies these days to deal with fileless malware.
It's doing much more than just examining the contents of files.
As you mentioned, antivirus, for instance, is looking at the behavior, what's going on on your computer, and trying to intercept that and stop things like that.
As with any other kind of malware attack, obviously you need to keep your antivirus up to date and make sure that it's properly defending against these kind of things.
And banks obviously are in the front line because they have so much to lose.
Typically, though, banks are pretty well secured against things, but they need to keep on top of these threats.
They use from network to the endpoints, all sorts of layers that allows them to detect when something happens within the organizations.
And it was this—
And it's collated from all the billion users they have and external data, et cetera, et cetera.
So this caused huge media, you know, media went around going, now that this graph search has been launched, you know, this is how you protect yourself.
There was a lot of concern about in terms of privacy, because it really did allow some deep dives into Facebook users.
So you could, for instance, I imagine I could look for I don't know, single people in my village who are under 30 years old or something like that.
There was one search, for example, it was called mothers of Jews who like bacon, just to show what could actually be displayed, which is pretty outrageous, right?
So the idea here is just to show you just how much information a particular user is showing on their Facebook profile, and how much information can a third party actually just get to find out about that person.
So effectively, you've got a homepage, you put in the profile, you know, the URL of the person you're wanting to look up.
And using Facebook's API, it'll go and give you all the information they can find.
I think it's quite, you know, so I did this with a few people and it's quite scary what you can find out even from people that you would assume are quite secure.
And I've just done it just now to my own Facebook profile page. I'm not an avid Facebooker by any means and I tend to be quite careful about my security and privacy.
One of the things that I've never really liked about Facebook is that people can tag you in photographs, right?
Now, the way Facebook works and the way I've set up my privacy settings, if someone tags me in a photograph, it sends me a message saying, "Graham, do you want to put this on your timeline or do you want it to appear automatically?" And I'm "no, I don't want it to appear on my timeline." But what I can't do is I can't prevent my friend from uploading that photograph, putting it on their timeline, and still tagging me.
The only way I can remove that is if I actually go and ask the person, "do you mind untagging me from that photograph? Would that be okay?" Which of course you're never going to do.
And that really pisses me off.
Even if you're locked down, there is still information out there because people tag and you have no control over that. And that's exactly a big problem, I think, with Facebook.
I don't like that either.
If it's yourself, obviously you've got quite a strong relationship. I'm sure in your case, Graham, it's best buds, BFFs.
So I think a few tips are just— I think people should maybe have a go at this and just have a look, even if they think they're pretty secure, just using your example you've given, Graham, I think, you know, you're pretty secure and I think everyone else might want to take a look.
I certainly was a bit surprised when I had a—
And there may be people that are listed there that you have no interest in seeing, don't see anymore, the relationship is over, yet you're still connected to them through Facebook.
That means they still have a lot more access than they would if they were outside your groups.
So I'm recommending that people just take a look at their— who they're friends with and, you know, maybe do a cull if appropriate.
But if you are going to post something, have your default to be security locked down. You know, I'm only going to share this with my friends.
It definitely isn't going to be public rather than having to remember, oh, I don't want this one to be public, I want this one to be private.
The default should be as much privacy as you can. But of course, everything you post on Facebook, remember, this is getting shared with Facebook.
But always be very careful about what you share.
You know, last year there was a 14-point increase in new users aged 65+ on Facebook. And that's a huge amount, right?
So I'm not sure all of them can navigate the security settings that are currently available on Facebook, and it might be good to have a helping hand.
But before we do that, we've got some feedback from listeners who've written in, telling us what they think of past episodes and some of their comments.
Martijn Grooten, friend of the show, editor of Virus Bulletin. He actually gave us our first piece of media coverage, you know. Isn't that fantastic?
So he's actually written about us and some of his other favorite security podcasts, including the SANS Daily, Stormcast, which is a great one, Risky Business, and a bunch of others as well.
Go and check them out. We'll put a link in the show notes to some of those.
And he said about us, "The three presenters of the brand new Smashing Security are all past Virus Bulletin authors and speakers because we've been at the conferences and chatted there.
So I was excited to learn about their new adventure in podcast land.
Podcast is presented with a good sense of humor, which has already made it one of my favorite security shows." Well, thank you very much, Martijn, for saying that.
Graham, your friend, he says your friends are very understanding and your accents are so bad, but entertaining podcast that helps us lesser mortals in IT.
That said, the discussion on ad blocks and on the pros and cons of antivirus in episode 6 were highly informative and thought-provoking.
Go watch one of the early video episodes to see their lovely simple faces.
And those images in your mind, you'll enjoy the later audio-only episode all the more." Oh, that's so great. Thanks very much.
He's suggesting people actually go and check those out, see what we look like.
And this went on for a number of, probably years until I got to see a picture of him.
Because of course, Google didn't exist then, so it's not like you just typed it in, and I was shocked.
I hope you've enjoyed not seeing our faces during the podcast, but you enjoyed what we were talking about.
We are on iTunes and Google Play Music and Stitcher and TuneIn and Overcast and all manner of other podcast apps as well. So please go and check us out and leave a positive review.
Or you could leave a negative review, I suppose, if you wanted to, but we'd rather you didn't.
If you like the show, tell your friends, follow us on Twitter. We're @Smashin'— without a G— Security. Smashing Security. And until next time, cheerio. Bye-bye.
Blurb:
Handbags at dawn for CrowdStrike and NSS Labs! Donald Trump’s insecure Android phone! File-less malware – is that so new? And StalkScan makes it easier to reveal what Facebook users have been carelessly sharing…
Computer security veterans Graham Cluley, Carole Theriault and Vanja Svajcer discuss.
Show notes
- AEP Public Test Announcement
- NSS Labs Report Confirms Testing of CrowdStrike Falcon was Incomplete and Wrong
- Some thoughts on the CrowdStrike vs NSS Labs debacle
- Which Android phone does Donald Trump use?
- Senators raise concerns over Donald Trump’s smartphone security
- Google claims ‘massive’ Stagefright Android bug had ‘sod all effect’
- A Scary New Kind of Malware Is Invading Banks All Over the World
- Fileless attacks against enterprise networks
- StalkScan
- This creepy Facebook tool is revealing a LOT about you
Hope you enjoy the show, tell us what you think and leave us a review on iTunes! You can follow the Smashing Security team on Bluesky.
Hi,
i think "Fileless attacks against enterprise networks " news is same before , lie and Ads news from Kaspersky .