WEBVTT

00:00:01.703 --> 00:00:03.803 align:middle line:84%
Additional features and
things that we really

00:00:03.803 --> 00:00:04.973 align:middle line:90%
like within this tool.

00:00:04.973 --> 00:00:07.103 align:middle line:84%
The Dynamic App Finder,
which I mentioned to you,

00:00:07.103 --> 00:00:09.173 align:middle line:84%
that is going to be
reported as custom.

00:00:09.173 --> 00:00:12.473 align:middle line:84%
In Physical Analyzer, it
was reported as manual.

00:00:12.473 --> 00:00:15.623 align:middle line:84%
Internet of Things is
awesome in this tool.

00:00:15.623 --> 00:00:17.206 align:middle line:90%
If you are looking for--

00:00:17.206 --> 00:00:18.623 align:middle line:84%
let's say you're
working on crime,

00:00:18.623 --> 00:00:22.563 align:middle line:84%
and you think Alexa heard
the crime being committed,

00:00:22.563 --> 00:00:25.683 align:middle line:84%
Alexa is parsed
really well in AXIOM.

00:00:25.683 --> 00:00:28.413 align:middle line:84%
You are going to need the
user credentials-- the Amazon

00:00:28.413 --> 00:00:30.783 align:middle line:84%
username and password--
to hear everything

00:00:30.783 --> 00:00:32.373 align:middle line:90%
that Alexa has heard.

00:00:32.373 --> 00:00:35.433 align:middle line:84%
A good example-- my son,
when he was younger,

00:00:35.433 --> 00:00:36.933 align:middle line:84%
we went through a
phase where we had

00:00:36.933 --> 00:00:39.573 align:middle line:84%
to listen to "Feliz Navidad"
year-round-- year-round,

00:00:39.573 --> 00:00:41.043 align:middle line:90%
it was painful.

00:00:41.043 --> 00:00:41.913 align:middle line:90%
He would always say.

00:00:41.913 --> 00:00:44.073 align:middle line:90%
"Alexa play Feliz Naughty Dog."

00:00:44.073 --> 00:00:46.593 align:middle line:84%
What's crazy is when you
look at the Alexa information

00:00:46.593 --> 00:00:48.813 align:middle line:84%
in internet of things,
it would actually

00:00:48.813 --> 00:00:53.403 align:middle line:84%
show the request
"Feliz Naughty Dog"

00:00:53.403 --> 00:00:57.453 align:middle line:84%
and then you would see Alexa
responding, "Feliz Navidad."

00:00:57.453 --> 00:01:00.303 align:middle line:84%
So let's say that
someone is speaking maybe

00:01:00.303 --> 00:01:02.673 align:middle line:84%
in a foreign language or
asking Alexa to do something

00:01:02.673 --> 00:01:04.863 align:middle line:84%
and it's not the
normal detected voice,

00:01:04.863 --> 00:01:06.873 align:middle line:90%
you could see that in the text.

00:01:06.873 --> 00:01:09.753 align:middle line:84%
If you have the person's
Amazon username and password,

00:01:09.753 --> 00:01:11.283 align:middle line:90%
you can actually hear it.

00:01:11.283 --> 00:01:13.353 align:middle line:90%
It's amazing what you can get.

00:01:13.353 --> 00:01:16.413 align:middle line:84%
Think about how many times if
you have Alexa, Google Home,

00:01:16.413 --> 00:01:19.773 align:middle line:84%
or any of these
things in your house

00:01:19.773 --> 00:01:22.443 align:middle line:84%
that the ring spins or you
see the lights lighting up

00:01:22.443 --> 00:01:24.093 align:middle line:84%
and you know it's
listening to you.

00:01:24.093 --> 00:01:25.743 align:middle line:84%
All of those things
can be parsed.

00:01:25.743 --> 00:01:29.393 align:middle line:84%
AXIOM is fantastic
with that type of data.

00:01:29.393 --> 00:01:31.143 align:middle line:84%
We're going to
look at timelining.

00:01:31.143 --> 00:01:33.383 align:middle line:84%
What's interesting
about Magnet, they

00:01:33.383 --> 00:01:38.783 align:middle line:84%
took all of the colorization
that we use in 50508,

00:01:38.783 --> 00:01:41.393 align:middle line:84%
and use those colors for
the timeline-- so evidence

00:01:41.393 --> 00:01:44.483 align:middle line:84%
of execution and things
like that-- file knowledge.

00:01:44.483 --> 00:01:47.300 align:middle line:84%
Mapping, obviously,
is similar to what

00:01:47.300 --> 00:01:48.383 align:middle line:90%
we've seen in other tools.

00:01:48.383 --> 00:01:50.363 align:middle line:84%
You would go into world
map view for that.

00:01:50.363 --> 00:01:52.283 align:middle line:90%
You can do connections.

00:01:52.283 --> 00:01:53.783 align:middle line:84%
Now, if I'm being
honest, I'm not

00:01:53.783 --> 00:01:56.603 align:middle line:84%
a big fan of these spider
webs of connections,

00:01:56.603 --> 00:01:58.523 align:middle line:90%
but you can do that.

00:01:58.523 --> 00:02:01.913 align:middle line:84%
Don't change the
system preferences

00:02:01.913 --> 00:02:04.733 align:middle line:84%
to create connections
upon parsing

00:02:04.733 --> 00:02:06.533 align:middle line:84%
or it's going to add
a lot of time to it.

00:02:06.533 --> 00:02:08.183 align:middle line:90%
Do it on the fly as needed.

00:02:08.183 --> 00:02:10.673 align:middle line:84%
Where this could help
you is potentially

00:02:10.673 --> 00:02:14.183 align:middle line:90%
in the CTF on Section 6.

00:02:14.183 --> 00:02:15.653 align:middle line:90%
There's also filtering.

00:02:15.653 --> 00:02:17.183 align:middle line:90%
There's image categorization.

00:02:17.183 --> 00:02:19.613 align:middle line:84%
There's all kinds of things
I'm going to walk you through.
