WEBVTT

00:00:06.973 --> 00:00:09.118
Man, you're like
an assembly line today!

00:00:09.190 --> 00:00:12.024
It seems like we've been
sending out wire transfers all day.

00:00:12.095 --> 00:00:13.899
How many closings has the boss
had you handling today?

00:00:13.946 --> 00:00:16.977
- It feels like twice as much as usual.
- Must be something in the water.

00:00:17.050 --> 00:00:19.290
I'd be twice as fast if I didn't
have all this email.

00:00:19.352 --> 00:00:21.306
Yea. My inbox is flooded, too.

00:00:21.377 --> 00:00:23.602
Boom!
Beat the buzzer!

00:00:23.706 --> 00:00:25.134
It's not three o'clock yet is it?

00:00:25.191 --> 00:00:26.566
No, it's five to...

00:00:26.577 --> 00:00:28.327
Oh, I forget we had that
meeting with marking!

00:00:28.338 --> 00:00:30.530
Oh, oh, shoot, I wanna get
that last wire transfer in

00:00:30.541 --> 00:00:31.780
before cut off!

00:00:32.243 --> 00:00:33.468
Say no more.

00:00:33.836 --> 00:00:35.513
- What's your login info?
- No, no, no, it's okay,

00:00:35.540 --> 00:00:37.218
I gotta hustle, I got,
I'll just do it later.

00:00:37.273 --> 00:00:39.513
Really, it's no big deal.
I got you.

00:00:39.539 --> 00:00:43.124
Um... okay, all right, here's my
access information, thanks.

00:00:56.583 --> 00:00:59.569
Oh, no. Oh, no no no.
Oh, gosh.

00:00:59.642 --> 00:01:01.147
- What? What's up?
- Oh

00:01:01.188 --> 00:01:04.085
I just got a message that we were
hit by a DDoS attack.

00:01:05.157 --> 00:01:07.143
What? That means our internet's
gonna be down for

00:01:07.174 --> 00:01:09.533
- who knows how long?
- I, I don't have time for this,

00:01:09.549 --> 00:01:11.366
I'm still trying to reverse
those transfers.

00:01:11.391 --> 00:01:12.225
Which ones?

00:01:12.297 --> 00:01:14.717
Somehow we had
two bad transfers

00:01:14.728 --> 00:01:16.664
to the Ukraine at seven
AM this morning?

00:01:17.189 --> 00:01:17.976
How bad?

00:01:18.032 --> 00:01:21.601
Uh, over a million dollars,
$505,000 each!

00:01:21.658 --> 00:01:22.664
What?!?

00:01:23.383 --> 00:01:24.726
Oh, my gosh.

00:01:24.782 --> 00:01:26.133
Were you able to reverse them?

00:01:26.174 --> 00:01:28.160
Just one, but as I tried
to notify the bank that the

00:01:28.171 --> 00:01:30.288
other one wasn't authorized...

00:01:30.299 --> 00:01:32.914
then the internet went down
because of the DDoS attack.

00:01:33.908 --> 00:01:35.617
Man,

00:01:35.628 --> 00:01:37.164
I wonder how that happened?

00:01:38.251 --> 00:01:40.804
I wonder how that happened.

00:01:41.048 --> 00:01:42.336
Indeed.

00:01:43.204 --> 00:01:44.633
This stuff happens,

00:01:44.644 --> 00:01:47.508
not as much as I'd like
but it happens.

00:01:47.830 --> 00:01:50.720
People get in a hurry,
they skip processes,

00:01:50.731 --> 00:01:53.885
they share usernames
and passwords

00:01:53.896 --> 00:01:55.445
and before they know it

00:01:55.455 --> 00:01:57.304
things get missed.

00:01:57.586 --> 00:02:00.789
That gives guys like me
a golden opportunity.

00:02:00.939 --> 00:02:03.445
You might be curious to know
what happened in this case.

00:02:03.526 --> 00:02:07.122
Well, the transfer was not stopped,

00:02:07.138 --> 00:02:08.466
the money was gone,

00:02:08.497 --> 00:02:09.330
poof.

00:02:10.294 --> 00:02:14.346
And when the company submitted
a claim through its insurance company,

00:02:14.373 --> 00:02:18.058
the investigation revealed
the bad habits of this group.

00:02:18.208 --> 00:02:21.480
This is the part that I really love.

00:02:21.530 --> 00:02:27.261
Employees opened a phishing
email message that had links,

00:02:27.289 --> 00:02:28.654
and yes,

00:02:28.665 --> 00:02:32.389
they clicked on those
links and yes,

00:02:32.407 --> 00:02:35.749
those links contained
malware and viruses

00:02:35.776 --> 00:02:38.356
that were loaded into the machine.

00:02:38.449 --> 00:02:39.637
Wow,

00:02:40.606 --> 00:02:44.193
I feel like these guys were
doing my work for me.

00:02:44.390 --> 00:02:48.146
Bad for the company.
But BEAUTIFUL for me!

00:02:48.968 --> 00:02:51.193
Man, I sure messed up.

00:02:51.453 --> 00:02:54.818
I never thought something like
this would happen... to me.

00:02:55.156 --> 00:02:57.880
I got so busy and distracted,

00:02:58.515 --> 00:03:01.458
I didn't think it was a big deal,
skipping a few procedures,

00:03:01.468 --> 00:03:03.224
and that's what happened
here for sure.

00:03:03.796 --> 00:03:06.146
Now, there are new
checklists in place

00:03:06.164 --> 00:03:10.333
to help make sure something
like this doesn't happen again,

00:03:10.424 --> 00:03:12.208
at least not as easily.

00:03:13.640 --> 00:03:17.083
When you don't follow
your organizations processes,

00:03:17.556 --> 00:03:21.047
things can go really bad,

00:03:21.931 --> 00:03:23.422
really fast.