WEBVTT

00:00:00.240 --> 00:00:02.770
We talked about detection, and, of course,

00:00:02.770 --> 00:00:05.730
the next logical step is going to be response.

00:00:05.740 --> 00:00:09.410
So, thinking about response, once you've identified this,

00:00:09.410 --> 00:00:12.460
you're in the oh crap moment, like, now what do we do?

00:00:12.840 --> 00:00:15.870
‑Yeah, so once you've found a business email compromised,

00:00:15.870 --> 00:00:20.230
there are absolutely a number of steps that you want to go through first.

00:00:20.750 --> 00:00:24.210
And again, we're talking Office 365 here,

00:00:25.020 --> 00:00:28.820
these steps still apply to any other email system that you might have access to.

00:00:28.830 --> 00:00:29.450
So,

00:00:29.460 --> 00:00:31.410
the first thing you're going to want to do is you're going to

00:00:31.410 --> 00:00:35.500
want to set it up so that you force a password change across

00:00:35.510 --> 00:00:37.460
all of the compromised users.

00:00:37.540 --> 00:00:40.290
If you don't know who all the compromised users are,

00:00:40.300 --> 00:00:42.640
then just do a forced password change across everybody.

00:00:42.650 --> 00:00:46.320
I know people don't, or organizations don't like to do that,

00:00:46.330 --> 00:00:48.880
but sometimes it's something that has to be done.

00:00:48.890 --> 00:00:52.080
So, once you set that forced password change,

00:00:52.090 --> 00:00:54.350
then the next thing you want to do is you want to kill

00:00:54.360 --> 00:00:56.950
all active sessions in Office 365.

00:00:56.940 --> 00:00:59.880
What that means is you go into the users,

00:00:59.890 --> 00:01:03.170
there is a button in there where you can say revoke active session.

00:01:03.180 --> 00:01:05.410
You want to click on that or write a PowerShell script to

00:01:05.410 --> 00:01:06.860
go through and do it for everybody,

00:01:06.870 --> 00:01:10.910
and what that does is that kills any active session that's there,

00:01:10.910 --> 00:01:13.830
so if an attacker is still able to get into the network

00:01:13.840 --> 00:01:16.850
because they have that session open, that's going to stop that,

00:01:16.850 --> 00:01:18.170
that's going to remove that.

00:01:18.440 --> 00:01:23.090
This is important to do because even if a user changes their password,

00:01:23.100 --> 00:01:26.370
those active sessions could be valid for up to 6 hours,

00:01:26.370 --> 00:01:30.710
depending on how the user has accessed it or how the attacker has accessed it.

00:01:30.720 --> 00:01:31.640
‑Yeah, no kidding.

00:01:31.640 --> 00:01:35.020
And likely with this dwell time they do have active sessions open,

00:01:35.020 --> 00:01:37.920
so that's something that's nearly a requirement for this.

00:01:37.920 --> 00:01:39.050
‑Yeah, absolutely.

00:01:39.050 --> 00:01:42.060
They will, and so you absolutely have to do that.

00:01:42.440 --> 00:01:44.770
And then the next thing you want to do is you want to find those inbox

00:01:44.770 --> 00:01:46.920
rules that we were just talking about and remove them.

00:01:46.930 --> 00:01:51.430
You want to prevent the attacker from getting any more emails coming in.

00:01:51.440 --> 00:01:55.560
And the best way to do that is to remove those inbox rules.

00:01:55.570 --> 00:01:55.870
You know,

00:01:55.870 --> 00:01:58.770
another way that you could do this is just completely disable the

00:01:58.770 --> 00:02:02.800
user's account and then put in blocks to prevent any emails from going

00:02:02.800 --> 00:02:05.300
out from that user or coming into that user,

00:02:05.300 --> 00:02:06.990
depending on how you want to set it up,

00:02:06.990 --> 00:02:10.419
but you absolutely want to go in and remove those inbox rules.

00:02:10.419 --> 00:02:12.170
‑So, as far as like response objectives,

00:02:12.170 --> 00:02:14.290
our first things are like we've shown up,

00:02:14.290 --> 00:02:18.010
we know what's happening, we need to reset accounts,

00:02:18.010 --> 00:02:21.290
we need to disable sessions, or revoke sessions,

00:02:21.290 --> 00:02:21.970
active sessions,

00:02:21.970 --> 00:02:26.420
we need to lock down those inbox rules or remove them completely,

00:02:26.420 --> 00:02:27.830
and maybe we start from scratch,

00:02:27.830 --> 00:02:31.540
I haven't been too many places where inbox rules are absolutely required,

00:02:31.540 --> 00:02:34.810
the user can go set them back up, it's okay,

00:02:34.820 --> 00:02:38.550
and/or you need to figure out what was accessed.

00:02:38.560 --> 00:02:42.160
Now, to do all of that, you kind of have to know what was the scope,

00:02:42.270 --> 00:02:45.400
how many people were actually compromised,

00:02:45.400 --> 00:02:47.220
where were they coming from, all of that stuff.

00:02:47.220 --> 00:02:48.750
How do you find all those things?

00:02:48.740 --> 00:02:49.280
‑Right.

00:02:49.280 --> 00:02:50.860
And that goes back to the investigation,

00:02:50.860 --> 00:02:53.120
doing the investigation that that we talked about.

00:02:53.120 --> 00:02:54.160
You know, what we just mentioned,

00:02:54.160 --> 00:02:56.030
the forcing the password change and killing the

00:02:56.030 --> 00:02:58.880
active sessions and and all that, that is,

00:02:58.970 --> 00:03:00.000
we're reaching containment,

00:03:00.000 --> 00:03:03.060
that's to contain the incident and eradicate the attacker.

00:03:03.070 --> 00:03:03.610
Basically,

00:03:03.610 --> 00:03:05.840
stopping the bleeding or preventing the attacker from

00:03:05.840 --> 00:03:07.850
maintaining access in the environment.

00:03:07.840 --> 00:03:09.790
But you're right, you need to define those rules,

00:03:09.790 --> 00:03:13.090
you need to figure out all those people who have been compromised.

00:03:13.090 --> 00:03:14.680
And, we went in,

00:03:14.680 --> 00:03:17.970
you showed your PowerShell script to pull the logs out and do that,

00:03:17.970 --> 00:03:22.190
I showed how to get into the audit logs and do that,

00:03:22.190 --> 00:03:27.240
but, you know, not everybody is going to have the time to do that manually,

00:03:27.240 --> 00:03:28.900
you need to have some automated process.

00:03:28.910 --> 00:03:29.840
And so, fortunately,

00:03:29.840 --> 00:03:32.700
there are a couple of tools out there that will kind of

00:03:32.700 --> 00:03:34.230
pull all these things down for you.

00:03:34.230 --> 00:03:34.780
And so,

00:03:34.780 --> 00:03:38.820
we can show how to use one of those tools to make the investigation at least a

00:03:38.820 --> 00:03:41.150
little bit easier so you can go in and find that information.

00:03:41.150 --> 00:03:43.270
‑Yeah, please do, I love open source tools,

00:03:43.270 --> 00:03:45.630
and I think the more we show, the better.

00:03:45.630 --> 00:03:49.670
So, getting rid of that scrolling through logs like we just said,

00:03:49.670 --> 00:03:52.780
that's not really tenable for this kind of investigation.

00:03:52.780 --> 00:03:56.440
And the other thing about automation is humans are less likely to

00:03:56.440 --> 00:03:58.560
miss stuff if it's being automated by the computer.

00:03:58.560 --> 00:04:01.080
Like if I'm like, oh, I'm looking for 188,

00:04:01.080 --> 00:04:03.580
is what I think the IP address was from Vietnam,

00:04:03.580 --> 00:04:06.180
if I'm looking for that, I may miss it as I scroll,

00:04:06.180 --> 00:04:08.990
whereas that may not happen with the automated tool.

00:04:09.000 --> 00:04:09.710
‑Absolutely.

00:04:09.710 --> 00:04:13.570
So let me do this, let me share my application here.

00:04:13.580 --> 00:04:14.960
‑Yeah, show me what you got.

00:04:16.339 --> 00:04:19.500
‑All right, so, you're going to love this, it's a PowerShell script.

00:04:19.510 --> 00:04:20.500
‑I love PowerShell.

00:04:21.029 --> 00:04:24.020
‑There is a project out there called KITT‑0365‑Tool,

00:04:24.020 --> 00:04:28.850
it's on GitHub, and it's got this really great PowerShell script.

00:04:28.850 --> 00:04:29.980
So, all you need to do,

00:04:29.990 --> 00:04:33.100
once you install all the prerequisites and all that

00:04:33.110 --> 00:04:37.700
which are on the GitHub website, is you run it,

00:04:37.700 --> 00:04:39.450
yes I do want to run this,

00:04:40.040 --> 00:04:43.190
it's going to create a transcript of everything that it does,

00:04:43.190 --> 00:04:45.170
so I'm just going to throw that on my desktop for the moment,

00:04:45.540 --> 00:04:46.910
and then it's going to ask you to sign in.

00:04:46.910 --> 00:04:50.980
You do need to sign in with somebody with admin privileges to Office 365.

00:04:50.980 --> 00:04:56.160
So, I'm going to sign in to that, into our demo corp that we set up.

00:04:56.160 --> 00:04:58.750
‑This already looks way cooler than my PowerShell script.

00:04:58.760 --> 00:04:59.720
‑So it's going to do that,

00:04:59.720 --> 00:05:01.490
and then it's going to start processing the information.

00:05:01.490 --> 00:05:02.960
It's going to start downloading things,

00:05:02.960 --> 00:05:06.520
it's going to start grabbing everything that it needs,

00:05:06.520 --> 00:05:07.970
and you can see how it's doing that.

00:05:07.980 --> 00:05:12.070
Obviously, you know, we have a very small domain here,

00:05:12.080 --> 00:05:13.730
I think what, seven users,

00:05:13.730 --> 00:05:18.800
I think when we looked at all events there was like maybe 500 events.

00:05:18.800 --> 00:05:22.860
You can imagine that with a larger organization

00:05:22.870 --> 00:05:25.310
that this could take a lot longer.

00:05:25.320 --> 00:05:27.570
‑Yeah, it seems like it'd take quite some time.

00:05:27.570 --> 00:05:29.950
And another thing for information timeout,

00:05:29.950 --> 00:05:31.980
this is probably one of the first things you want to do,

00:05:31.990 --> 00:05:32.320
right?

00:05:32.320 --> 00:05:33.670
You don't want to lose any data?

00:05:33.940 --> 00:05:35.880
‑Absolutely.

00:05:35.890 --> 00:05:37.410
Depending on your license,

00:05:37.650 --> 00:05:42.700
the audit logs may only be kept for 7 days or potentially up to 90 days,

00:05:42.710 --> 00:05:44.920
again, it depends on your license.

00:05:44.930 --> 00:05:46.870
So as soon as something like this happens,

00:05:46.880 --> 00:05:49.860
you need to get in there and grab that information out.

00:05:50.140 --> 00:05:52.430
‑It sounds to me like someone needs to redo the order of

00:05:52.430 --> 00:05:55.120
volatility to include all these cloud services as well.

00:05:55.130 --> 00:05:57.850
‑I agree, that absolutely needs to happen.

00:05:57.940 --> 00:06:01.070
‑That's a nice, new NIST document that someone needs to get on,

00:06:01.080 --> 00:06:02.770
other than me, right away.

00:06:03.140 --> 00:06:06.650
‑So, the application has popped up this nice little GUI,

00:06:06.650 --> 00:06:09.420
it's all GUI‑driven, even though it's PowerShell,

00:06:09.420 --> 00:06:12.020
you don't have to worry about modifying anything like that.

00:06:12.030 --> 00:06:16.290
I will say you will have to go into the PowerShell script

00:06:16.290 --> 00:06:18.100
before you run it to modify a couple places,

00:06:18.100 --> 00:06:20.630
but again, read the documentation, it'll tell you that.

00:06:20.630 --> 00:06:22.910
But the first thing I'm going to do is I'm going to go in

00:06:22.910 --> 00:06:24.950
and I'm going to tell it the date range.

00:06:24.940 --> 00:06:28.140
I'm just going to go this week,

00:06:28.150 --> 00:06:32.810
and then I'm going to click Search and it's going to ask,

00:06:32.820 --> 00:06:34.800
well, what user do you want to look at?

00:06:34.810 --> 00:06:36.690
We're like, we're going to cheat a little bit,

00:06:36.690 --> 00:06:38.680
we know that Kim is the one who's been compromised,

00:06:38.680 --> 00:06:43.010
so let's just choose Kim, and then I'll click OK.

00:06:43.010 --> 00:06:45.910
And then, it's going to be doing a bunch of things,

00:06:45.910 --> 00:06:48.150
right now it's pulling back all of her information.

00:06:49.640 --> 00:06:52.920
So here on the left pane, we see the user information for Kim,

00:06:52.920 --> 00:06:59.320
we see when she was last logged on, when her password was last changed,

00:06:59.330 --> 00:07:00.580
and so on.

00:07:00.580 --> 00:07:03.430
On the right‑hand side there's some additional information about her,

00:07:03.430 --> 00:07:06.150
but we are interested in a couple of things.

00:07:06.150 --> 00:07:09.730
We want to see her inbox rules and we want to see the logins.

00:07:09.730 --> 00:07:11.550
So I'm just going to jump over the Logins first.

00:07:12.140 --> 00:07:15.280
And here, unfortunately, it doesn't do the GoIP lookups,

00:07:15.520 --> 00:07:17.840
but you know, it's PowerShell, it's open source,

00:07:17.840 --> 00:07:19.370
we could add that in if we wanted to.

00:07:19.370 --> 00:07:21.550
I expect you to have that done by tomorrow, Aaron.

00:07:21.560 --> 00:07:23.500
‑Yeah, I'm doing it right now.

00:07:23.510 --> 00:07:26.560
‑But we can at least see all the different IP addresses

00:07:26.560 --> 00:07:29.150
that Kim's user ID logged on from.

00:07:29.140 --> 00:07:31.410
Additionally, you remember, we were talking about the user agent,

00:07:31.410 --> 00:07:34.130
you can actually see that user agent here,

00:07:34.140 --> 00:07:36.700
all of the different user agents that she's logged in as.

00:07:36.710 --> 00:07:39.910
She logged in from using Edge and on Firefox.

00:07:39.920 --> 00:07:42.950
And we can, again, have that conversation with her to ask,

00:07:42.950 --> 00:07:45.560
hey Kim, what browser do you use when you access your email?

00:07:45.560 --> 00:07:48.760
Or do you only use like the Outlook Client because the Outlook

00:07:48.760 --> 00:07:51.460
Client will have its own user agent as well.

00:07:51.740 --> 00:07:55.970
So this absolutely is a lot easier than us downloading the logs,

00:07:56.040 --> 00:07:58.790
grepping through them, pulling out what we need,

00:07:58.790 --> 00:08:02.750
or even looking through the web interface because we might have to scroll

00:08:02.750 --> 00:08:04.820
through page upon page upon page to see all of this.

00:08:04.820 --> 00:08:06.360
This kind of gives it to us right here.

00:08:06.740 --> 00:08:07.590
‑Certainly.

00:08:07.590 --> 00:08:10.120
And if you look at this initially, you also get stuff like,

00:08:10.130 --> 00:08:13.650
hey, if you've had this environment for quite some time,

00:08:13.650 --> 00:08:16.570
you're going to have hundreds of logins from a user and then just a few

00:08:16.570 --> 00:08:19.360
logins that are probably from the malicious actor,

00:08:19.370 --> 00:08:21.430
right, it's not going to be equal numbers.

00:08:21.430 --> 00:08:22.960
That's a bit of an indicator as well.

00:08:22.970 --> 00:08:24.050
‑Right, absolutely.

00:08:24.040 --> 00:08:25.570
Now, this is her logins.

00:08:25.570 --> 00:08:27.610
Let's let's go over and look at her inbox rules.

00:08:27.620 --> 00:08:30.410
And it automatically pulled down all of her inbox rules,

00:08:30.420 --> 00:08:33.210
and you can see that it's actually a much nicer interface

00:08:33.210 --> 00:08:35.650
than what the audit logs were showing us.

00:08:35.740 --> 00:08:36.620
The audit logs,

00:08:36.620 --> 00:08:40.200
we kind of had to go through the JSON that it was showing us in

00:08:40.200 --> 00:08:42.159
order to kind of parse that out ourselves.

00:08:42.539 --> 00:08:45.410
The PowerShell script here does it automatically for us.

00:08:45.410 --> 00:08:48.190
So I'm going to move to Rule 2 first because this is the one that's

00:08:48.190 --> 00:08:50.530
a little bit more interesting where it shows,

00:08:50.540 --> 00:08:53.620
if the message, the body of the message contains the words wire,

00:08:53.620 --> 00:08:56.560
wiring, fund, and so on, for the email to that,

00:08:56.560 --> 00:09:01.350
oh in this case, it's Kimberly.logan@outlook.com instead of ProtonMail.

00:09:01.340 --> 00:09:04.780
If you remember when we were looking at the audit logs,

00:09:04.780 --> 00:09:07.280
we saw that there was a create inbox rule,

00:09:07.280 --> 00:09:09.200
and then there was an update inbox rule.

00:09:09.200 --> 00:09:11.240
‑Oh right, the set inbox, yeah.

00:09:11.240 --> 00:09:15.360
‑Right, we never looked at the set inbox rule, which would update it.

00:09:15.360 --> 00:09:17.680
And so, this is,

00:09:17.690 --> 00:09:22.260
the attacker obviously went in and updated it from ProtonMail to Outlook.com.

00:09:22.340 --> 00:09:22.870
‑That's awesome.

00:09:22.870 --> 00:09:27.260
That's really cool attention grab to, again, go check the set inbox stuff too.

00:09:27.270 --> 00:09:28.250
‑Yeah, exactly.

00:09:28.440 --> 00:09:31.110
So this is showing us a lot of information.

00:09:31.120 --> 00:09:35.140
One other thing that we can look at,

00:09:35.520 --> 00:09:38.740
remember I said that if one user is compromised,

00:09:38.740 --> 00:09:41.300
chances are another user is compromised as well.

00:09:41.310 --> 00:09:47.160
Well, again, we know that these 188 addresses are the attacker's addresses,

00:09:47.160 --> 00:09:51.900
so let me ‑‑‑And at this point, that's super valid because we've already,

00:09:51.900 --> 00:09:52.870
we're in response now.

00:09:52.870 --> 00:09:54.540
We've done detection, we know that this is bad,

00:09:54.540 --> 00:09:57.350
we've gone and validated that in response mode.

00:09:57.360 --> 00:09:59.960
It seems like cheating now just because there's not a lot of data,

00:09:59.960 --> 00:10:01.650
but this is, you'd already be at this point.

00:10:01.660 --> 00:10:03.220
‑Yeah, exactly, exactly.

00:10:03.220 --> 00:10:04.490
We're just kind of,

00:10:04.500 --> 00:10:06.900
you would normally probably do this at the beginning of your

00:10:06.900 --> 00:10:09.200
investigation to just kind of pull all the information,

00:10:09.210 --> 00:10:13.000
or in the middle of your investigation, just to kind of validate some things,

00:10:13.010 --> 00:10:15.670
make sure you're not missing anything, and so on.

00:10:15.670 --> 00:10:21.690
But, I'm going to copy this IP address, go to Logins by IP,

00:10:21.690 --> 00:10:25.970
nope, there's something hidden over here.

00:10:26.340 --> 00:10:27.150
There we go.

00:10:27.540 --> 00:10:30.410
So I'm going to type in that IP over here and then I'm

00:10:30.410 --> 00:10:33.080
going to click Search Using Fresh IP.

00:10:34.050 --> 00:10:37.360
And in this case, it shows us that yes, from this IP address,

00:10:37.360 --> 00:10:41.060
this .76 IP address, Kim was the only one who logged on.

00:10:41.640 --> 00:10:42.130
‑Got it.

00:10:42.130 --> 00:10:44.030
But if there were other users.

00:10:44.030 --> 00:10:45.040
‑Right.

00:10:45.050 --> 00:10:48.470
Well, there is a second IP address, the second IP address in this range.

00:10:48.470 --> 00:10:49.660
So let's look at this one.

00:10:50.740 --> 00:10:52.060
Let's see if this pulls us anything.

00:10:52.840 --> 00:10:55.880
In this case, it kind of confirms for us that,

00:10:55.880 --> 00:10:59.570
yes, Kim was the only one that, at least using these IP addresses,

00:10:59.580 --> 00:11:01.260
that the attacker logged in under.

00:11:01.260 --> 00:11:06.670
Which is good, it would mean that we are restricted to just this.

00:11:07.140 --> 00:11:09.170
‑Though if we had seen that from multiple users,

00:11:09.170 --> 00:11:10.650
this now helps us detect, okay,

00:11:10.650 --> 00:11:13.960
what's the extent of this compromise of the users?

00:11:13.960 --> 00:11:19.830
Now, I suppose, realistically, depending on the access of an individual user,

00:11:19.830 --> 00:11:22.960
they don't really need more than one, depending on where they land,

00:11:22.960 --> 00:11:25.090
but, you at least can figure out,

00:11:25.100 --> 00:11:27.940
if you try to figure out like whose accounts need to be reset right now,

00:11:27.940 --> 00:11:29.540
it's this list of accounts.

00:11:29.550 --> 00:11:31.910
‑Yeah, absolutely correct.

00:11:31.920 --> 00:11:35.190
One other thing that you can look at is it has this Message Trace tab.

00:11:35.200 --> 00:11:40.380
So what we can do is we can start looking to see if that logging is in place,

00:11:40.540 --> 00:11:45.290
what email addresses were receiving, sending and receiving emails.

00:11:45.300 --> 00:11:49.420
So I need to enter in one user email address.

00:11:49.420 --> 00:11:50.480
So I'm going to copy Kim's,

00:11:50.480 --> 00:11:53.110
and we're just going to go in here and say I want to

00:11:53.110 --> 00:11:56.450
see all the emails that Kim sent out.

00:11:57.440 --> 00:11:58.030
‑Oh, great.

00:11:58.040 --> 00:12:01.670
‑And here we can see it kind of shows us all of the emails,

00:12:01.680 --> 00:12:05.800
the list of senders, the recipients, how many were delivered and failed.

00:12:05.810 --> 00:12:09.650
You can see here that there was one email to our

00:12:09.650 --> 00:12:11.450
ProtonMail account that went out,

00:12:11.460 --> 00:12:15.040
and there were two emails to our malicious Outlook account.

00:12:15.050 --> 00:12:16.390
So, because of that,

00:12:16.390 --> 00:12:21.150
now we know that at least three emails went out to the attacker.

00:12:21.540 --> 00:12:22.120
‑Absolutely.

00:12:22.120 --> 00:12:26.070
And that starts to scope some of the information that was probably lost as well.

00:12:26.440 --> 00:12:27.310
‑Yeah, absolutely.

00:12:27.310 --> 00:12:30.070
And we can go in and we can download these message trace logs.

00:12:30.070 --> 00:12:32.380
In fact, if we wanted to click View Message Trace Logs,

00:12:32.390 --> 00:12:34.900
now we can actually go in and see what these emails were.

00:12:34.900 --> 00:12:41.560
So if I wanted to see what email was sent out to this fake Kimberly Logan one,

00:12:41.560 --> 00:12:46.800
now we can see at least the subject, whether or not it was delivered,

00:12:46.800 --> 00:12:48.500
when it happened, and then we can go in,

00:12:48.510 --> 00:12:52.640
hopefully into the user's sent items folder and see what that email was,

00:12:52.640 --> 00:12:54.610
or at least start looking through the inbox to see what it is.

00:12:54.610 --> 00:12:56.160
Unfortunately, we can't pull it up here,

00:12:56.140 --> 00:12:59.730
but we can at least pivot off that information into their inbox.

00:12:59.740 --> 00:13:01.790
‑Yeah, and as I'm looking at this too,

00:13:01.790 --> 00:13:04.800
I see the status of failed ends up being highly associated

00:13:04.800 --> 00:13:07.870
with those two malicious emails also,

00:13:07.880 --> 00:13:10.910
certainly not an indicator that every failed message is bad,

00:13:10.910 --> 00:13:14.840
but if you're already in this scenario where you have other stuff going on,

00:13:14.840 --> 00:13:18.280
attackers make mistakes, and/or I believe in some of these cases it was,

00:13:18.290 --> 00:13:20.510
you couldn't, like you said, it said invoice,

00:13:20.510 --> 00:13:22.940
it wouldn't allow sending of invoices.

00:13:22.940 --> 00:13:26.550
Like that was something that got caught by whether it was

00:13:26.550 --> 00:13:29.090
ATP or one of the Defender products.

00:13:29.100 --> 00:13:29.820
‑Right.

00:13:29.830 --> 00:13:32.200
Now, the thing to keep in mind, and this is,

00:13:32.200 --> 00:13:32.550
I think,

00:13:32.550 --> 00:13:38.500
a great place for us to kind of pivot over to talking about the licenses because

00:13:38.510 --> 00:13:42.810
these message trace logs are not always going to be there.

00:13:42.810 --> 00:13:46.960
So, let's talk about the licenses just a little bit.

00:13:47.040 --> 00:13:51.600
So, we are using what's called the E5 license within Office 365.

00:13:51.610 --> 00:13:56.010
That is kind of not, that's not their very top tier, but it's pretty close.

00:13:56.010 --> 00:13:57.090
It's like their second from the top.

00:13:57.090 --> 00:14:00.710
I think they're top tier is like F5 is what it's called.

00:14:00.720 --> 00:14:02.060
For the E5 license,

00:14:02.060 --> 00:14:05.260
the most important thing for us is that they turn on a

00:14:05.260 --> 00:14:07.470
lot of the audit logs by default.

00:14:07.440 --> 00:14:11.910
So things like the mail items accessed are going to be logged by default,

00:14:11.910 --> 00:14:14.110
or at least shown to the user by default.

00:14:14.120 --> 00:14:20.160
Now, unfortunately, most organizations don't have E5 because it costs more.

00:14:20.740 --> 00:14:24.260
Most organizations have E3 or below.

00:14:24.270 --> 00:14:27.270
And Microsoft has a couple of levels below E3,

00:14:27.550 --> 00:14:30.420
but most organizations have at least an E3 level.

00:14:30.430 --> 00:14:33.310
And what that means is, if you go into those audit logs,

00:14:33.310 --> 00:14:37.660
or you run the kit PowerShell tool that we just did,

00:14:37.840 --> 00:14:40.380
you're not going to be able to necessarily see all the information.

00:14:40.380 --> 00:14:43.110
And in my experience, you'll still see the inbox rules being created,

00:14:43.110 --> 00:14:47.260
you'll see the signins and logons, but that's it.

00:14:47.270 --> 00:14:48.150
Now,

00:14:48.160 --> 00:14:52.230
in order to see all the other things like what the attacker actually accessed,

00:14:52.230 --> 00:14:56.060
which mail items they accessed, you need to either have E5 or,

00:14:56.740 --> 00:14:59.060
and again, this gets a little bit confusing,

00:14:59.060 --> 00:15:03.000
if you have E3 you have to specifically go in and use

00:15:03.000 --> 00:15:05.870
PowerShell to turn on that auditing for that,

00:15:05.880 --> 00:15:07.530
for specific users.

00:15:07.540 --> 00:15:10.880
It's there, Microsoft will record it,

00:15:10.880 --> 00:15:13.290
but you don't get to see it unless you turn it on.

00:15:13.300 --> 00:15:18.560
And unfortunately, you only get to see it when you turn it on going forward.

00:15:18.560 --> 00:15:23.240
So Aaron, if you got compromised right now and we had E3,

00:15:23.250 --> 00:15:25.670
and we didn't discover it until next week and we turned

00:15:25.670 --> 00:15:29.580
your auditing on under E3 next week, we wouldn't see any of this data beforehand.

00:15:29.580 --> 00:15:29.670
‑Right.

00:15:29.670 --> 00:15:31.560
And we wouldn't catch those inbox rules,

00:15:31.560 --> 00:15:33.050
we wouldn't catch any of that from there.

00:15:33.140 --> 00:15:33.560
‑Exactly,

00:15:33.560 --> 00:15:37.560
so this is definitely something that you, as administrators,

00:15:37.570 --> 00:15:40.420
want to go in and see what is turned on.

00:15:40.420 --> 00:15:43.780
I would highly recommend actually going in and users who are

00:15:43.780 --> 00:15:46.680
going to be handling sensitive data like this,

00:15:46.690 --> 00:15:49.820
that are going to be handling invoices or who are more

00:15:49.820 --> 00:15:51.850
susceptible to these types of attacks,

00:15:51.860 --> 00:15:54.360
to going in and turning on that mailbox auditing or

00:15:54.360 --> 00:15:57.430
upgrading their license to E5 just in case.

00:15:57.440 --> 00:16:00.190
‑I see what you're saying now, it's at an individual level.

00:16:00.200 --> 00:16:00.640
‑Right?

00:16:00.650 --> 00:16:02.660
For E3 it is at an individual level.

00:16:02.740 --> 00:16:05.360
‑So you have to go turn it on for a very specific user,

00:16:05.360 --> 00:16:07.570
and, of course, that takes up more log space,

00:16:07.570 --> 00:16:10.120
which means it probably costs a little bit more on the storage end of it,

00:16:10.120 --> 00:16:10.400
too.

00:16:10.410 --> 00:16:12.340
And to be clear,

00:16:12.340 --> 00:16:15.450
this isn't a sales pitch for buying a higher level of premium

00:16:15.450 --> 00:16:19.170
service for Azure or any other cloud service,

00:16:19.170 --> 00:16:21.250
but what I do think is an important note,

00:16:21.340 --> 00:16:24.850
and you just brought it up now, was the sensitive data component.

00:16:25.140 --> 00:16:26.770
Maybe this is where you start looking at,

00:16:26.780 --> 00:16:32.620
if we are an organization that has the responsibility to manage sensitive data,

00:16:32.630 --> 00:16:37.180
and again that's a word to a reasonable amount of security,

00:16:37.180 --> 00:16:43.270
like the legal phrase within the regulatory bodies that

00:16:43.270 --> 00:16:45.180
want to come look at this after the fact,

00:16:45.190 --> 00:16:48.040
is are you protecting it within a reasonable amount?

00:16:48.050 --> 00:16:49.800
And the reasonable amount could be like,

00:16:49.810 --> 00:16:51.610
well, of course, should you manage sensitive data,

00:16:51.610 --> 00:16:55.430
you probably should turn on the audit logging for

00:16:55.430 --> 00:16:57.230
users who manage the sensitive data.

00:16:57.230 --> 00:17:00.060
And that's, I just wanted to make that delineation for,

00:17:00.140 --> 00:17:02.770
here's a good point to maybe look at that and maybe where

00:17:02.770 --> 00:17:05.310
you should invest a little bit more money.

00:17:05.310 --> 00:17:05.599
‑Right.

00:17:05.599 --> 00:17:08.400
And you just, I think you hit it on the head right there.

00:17:08.410 --> 00:17:10.150
It all comes down to money.

00:17:10.160 --> 00:17:12.920
Obviously the attackers, they're motivated by money here,

00:17:12.920 --> 00:17:16.200
but our protections as well are also motivated by money.

00:17:16.200 --> 00:17:16.880
And, you know,

00:17:16.880 --> 00:17:21.640
if I'm a security person who's trying to convince management or

00:17:21.640 --> 00:17:24.060
whoever controls the budget that we need to do this,

00:17:24.060 --> 00:17:26.430
the way that I would phrase it is,

00:17:26.430 --> 00:17:29.830
well we can spend a couple extra bucks a month to have these

00:17:29.830 --> 00:17:31.530
logs sitting there in case we need them,

00:17:31.540 --> 00:17:34.990
or, in the future if we get compromised by this,

00:17:35.000 --> 00:17:37.700
we cannot have these logs and get hit with regulatory

00:17:37.700 --> 00:17:41.040
penalties because we can't say whether or not sensitive

00:17:41.040 --> 00:17:43.960
information was exfiltrated or accessed.

00:17:43.940 --> 00:17:46.950
And that right there, those fines aren't cheap.

00:17:46.950 --> 00:17:49.870
We're not talking a $10 parking ticket here.

00:17:49.870 --> 00:17:53.280
We're talking potentially thousands or hundreds of thousands of dollars

00:17:53.280 --> 00:17:55.880
or more fines that could potentially happen here.

00:17:55.890 --> 00:17:56.870
Would you rather pay that,

00:17:56.870 --> 00:18:00.360
or would you rather pay a couple extra bucks a month just to have these logs?

00:18:00.360 --> 00:18:01.490
‑Yeah, absolutely.

00:18:01.490 --> 00:18:03.370
I think that kind of takes us in,

00:18:03.370 --> 00:18:07.840
we're moving into a wrap up of where that puts some of this stuff that

00:18:07.840 --> 00:18:10.450
we're talking about doing for detections and response,

00:18:10.450 --> 00:18:13.340
and what level you need to go to to be able to protect yourself.

00:18:13.340 --> 00:18:17.060
We can get into some of that risk management stuff here in this last bit.

00:18:17.540 --> 00:18:17.820
‑Okay.

00:18:17.830 --> 00:18:18.350
Sounds good.
