8 hours 39 minutes
hello and welcome to another application of the minor attack framework discussion. Today, we're going to be looking at browser extension. So with that, let's go ahead and jump on over to our objectives. So the objectives four to today's discussion or is followed.
So we're going to describe what browser extension is as faras within the minor attack framework
and how that's used. How have browser extensions been used? What are some mitigation techniques? And, of course, we're going around out with some detection techniques as well. So let's go ahead and jump right in.
So browser extension, as it is listed in the minor attack framework, is involving things like plug ins or programs that could be added to or provide function to and customization of Internet browsers.
That's a great thing, right? We love things that make our lives easier, that make our lives more convenient. Password managers are coupon cutters,
whatever honey token things were doing or something of that nature. But in this case,
that is not always a great thing. Malicious extensions can be installed through malicious applications and downloads that may seem legitimate through things like social engineering or through some phase of an already installed malicious payload. And so these extensions allow threat actors to do things like a website browsing in the background,
stealing information a user inputs into the browser commanding control purposes,
and then for the installation of other tools such as rants or remote access tools. And so there are a lot of different things that browser extensions can achieve. I know that some of my best experiences as far as helping
folks with system issues just from personal stories that I like to share with other folks
is any time you have a user that's complaining of slow system, that's having problems and they don't understand it with acting fine yesterday. And so the first thing you do
and she start to investigate Askew, open up a Web browser. And lo and behold, a good quarter of the top of that has just all these different plug ins and extensions and pieces. And you kind of shake your head and hang it low and, you know, start doing some virus scanning and some other questions and clean up activity.
So browser extensions have been used and have been around for quite some time.
So let's talk real quick about an application of that are looking at a particular threat group. So Kim Suki and Google Chrome so information indicates that the group has been active since September of 2013 so they've been around for a little bit.
A report released in December
of 2018 indicated that the group infected systems using a Google chrome extension. Kato still passwords cookie information and, of course, do other things to those systems. So several fishing campaigns were essentially conducted using the extension on the academic sector,
with no information on the victims provided at this time.
And so it's looking like based on some reading and research,
that a part of the attack was motivated, of course, by the research the academics were doing, and they're given fields such as biomedical engineering. And so when we think about threat groups, often times they come in different flavors and forms that can be state funded criminal organizations. But they're very sophisticated,
and so it would make sense
that they made target research and academia and things of that nature because there could be technologies or discoveries or things that we're working on that they could take advantage of and So
again, as you'll note here, this keeps coming up. Fishing campaigns and things of that. Nature continued to be a savvy way for these folks to get these extensions in and to take advantage of that good old user trust. Now
let's talk about some mitigation techniques with respect to browser extensions and what's going on there.
So set extension white or black lists as appropriate for the business security policy. So again,
we really want to make sure that policies and procedures are in place to allow us to effectively implement controls and to enforce those controls if we're not implementing controls based on security policies are based on risk management activities than we could really be shooting in the dark and hoping that we're hitting the mark.
Do not allow the installation of software by standard user accounts and practice lease privilege
again. Least privileges coming back into that. Make sure that you have to at least maybe elevate your privilege via command. All right, right click or some type of prompt prior to being able to install something so that nothing can just run outright without some type of prompt or warning,
and then implement regular in user awareness training covering such attack methods again.
A lot of these things, especially when we're involving phishing attacks and things of that nature
training and the human element, is going to be the last line of defense when all other technical components fail. And so having that human element, well educated and strong, is going to help us to mitigate these types of risks. But
I beg to ask a question
that maybe some of you caught and maybe some of you are thinking about, and I think this is a good time to bring it up.
So in the previous slide,
the attack was specific
to the academic sector.
And so we're dealing with researchers and students and people of that caliber and nature. So when I was a student and I'm always a student, it feels like
I used university laptops or desktops as they were available in a lab setting. Maybe,
But for the most part I did my research and my paper writing and submissions and email checking and all of those things on my personal device.
then do we start to protect
academic information such as, ah, persons thesis or research that could be
pertinent to bettering our nation or whatever the case may be. Wherever you're at
right, do we keep that research in a cloud based system that is protected and we don't keep it on local systems? But then, who ultimately owns the research? Is it the property of the person doing the research? The person that is is designing that system or the person that is doing that, or since it's funded by the college,
does the college or university have ultimate authority and control over the information?
So as you can see, this particular topic kind of led to some very interesting questions with respect to how we would handle those mitigation techniques. So keep that in mind as you designed security policies and procedures,
depending on the industry in the area that you're working. And that may change the way in which you have to approach these controls. So let's talk about some detection techniques real quick as well. So you could audit Web browser extensions to ensure that the ones installed or for business purpose on Lee, and that they're not masquerading as legitimate ones.
We can use network monitoring tools,
toe look for communications with command and control servers. If we've got a known blacklist of those,
and then we can monitor for new files written to the registry or portable execution files written to the disk. So all great things again that we can do if we have the tools in place that allow us to do so and the systems belong to the organization. Question. Because again, when we start to blur the lines between
personally owned devices
versus the property of an organization or a university, that can make these controls in these detection methodologies a little bit more difficult to implement. So with that in mind, let's go ahead and do a quick check on learning. True or false browser extension attacks are limited to Web browsers like Google Chrome.
All right, well, if you need some additional time Teoh research or think about this question, please pause the video so browser extension attacks are limited to Web browsers like Google chrome. Well,
the good news is, is that they are not limited to just where browsers like Google chrome they can be. Any browser that can install an extension
could be susceptible to these types of attacks and So in this case, this is not a true statement. It is a false statement. Now, with that, let's go ahead and jump over to our summary. So today we looked at and described browser extension browser extensions essentially being applications, plug ins,
to the Web browser and your overall browsing experience. We reviewed how browser extensions have been used in ways in which we can still cookies or do things of that nature. Still, passwords still data or use maybe the browser on the system without the knowledge of the end user.
We reviewed some mitigation techniques again, such as validating
those particular extensions as faras. That would be more detection. Sorry with mitigation techniques. It would be not allowing the installation of maybe unsigned plug ins or maybe not allowing installation at all without administrative intervention and then for detection techniques. Looking for known bad browser
four gins as well as maybe auditing for commanding control. At type activity would be beneficial. Do is well,
so with that in mind, I want to thank you for your time today, and I look forward to seeing you again soon