WEBVTT

00:01.120 --> 00:07.240
Hey everyone welcome to Windows registry analysis with Reg Ripper in the previous video we covered the

00:07.240 --> 00:13.690
sleuth kit and showed how to analyze the NTFS file system of a Windows image in this video.

00:13.750 --> 00:18.700
We're going to illustrate how to analyze another important source of information for Windows forensic

00:18.700 --> 00:21.210
analysis Windows registry.

00:21.670 --> 00:24.320
To begin we're going introduce the Windows registry.

00:24.400 --> 00:30.700
Its structure location and features and explain why it's relevant for the forensic analyst.

00:30.700 --> 00:37.230
Then we'll introduce uncover Reg Ripper an open source tool specifically developed to analyze the registry.

00:37.450 --> 00:43.210
The Windows registry is a hierarchical database that stores most of its configuration and settings not

00:43.210 --> 00:50.050
only from the Windows system but also applications users and devices that reason it's a valuable source

00:50.050 --> 00:55.150
of information that needs to be considered in a forensic analysis of a Windows image.

00:55.270 --> 01:00.280
The information and artifacts that could be extracted from the registry ranged from the OS settings

01:00.280 --> 01:06.280
to the installed and executed programs from the user's activities to the connected devices and many

01:06.280 --> 01:09.820
others examining certain artifacts from the registry.

01:09.820 --> 01:16.370
For example the auto run keys could also lead to the detection of malware on the investigated system.

01:16.390 --> 01:20.640
The registry is composed of binary data files also called HIV's.

01:20.800 --> 01:25.810
The main registry hives that are common through the different versions of Windows are the same security

01:25.870 --> 01:28.060
software and system HIV's.

01:28.060 --> 01:33.790
They're located in the system 32 config folder under the windows system directory.

01:33.790 --> 01:38.010
There are also registry hives that are specific to each user of the system.

01:38.020 --> 01:43.100
These are the anti user dot dot and the User class dot dot HIV's.

01:43.150 --> 01:48.250
The former is located in the main user's profile directory but the path of the folders in which are

01:48.250 --> 01:54.580
located slightly differ between versions of Windows up to XP and the newer ones the same haif contains

01:54.580 --> 02:00.440
information about the local system users and groups including the password stored in hashed format.

02:00.490 --> 02:07.540
The security hived stores the system security settings such as the accounts audit users rights and applications

02:07.540 --> 02:08.860
control policies.

02:09.040 --> 02:15.460
The software hive as the name says stores the windows configuration as well as of the installed programs

02:15.940 --> 02:22.210
system HIV's contain the settings of the system and other devices that are currently or have previously

02:22.300 --> 02:23.970
been attached to the computer.

02:23.980 --> 02:29.330
The information in the registry is structured on two basic elements keys and values.

02:29.410 --> 02:34.180
Keys are containers similar to folders that could include values or other keys.

02:34.270 --> 02:42.010
Values are objects similar to files identify by a name type and the associated data value the highest

02:42.010 --> 02:50.020
keys in the hierarchy are called Root keys and the most important is the key local machine or HK L.M.

02:50.470 --> 02:56.860
or KLM key under which are mapped as subkey as the contents of the four main registry hives.

02:56.890 --> 03:04.510
We've seen Sam security software and system users and I.T. admins generally interact with the registry

03:04.570 --> 03:08.200
using Reg edit or similar ed. programs.

03:08.200 --> 03:13.720
This approach isn't very effective when dealing with forensic analysis because the registry has quite

03:13.720 --> 03:20.410
a complex structure and simply using an editor will certainly make us miss many artifacts to automatize

03:20.410 --> 03:22.300
the analysis of the registry.

03:22.300 --> 03:27.530
There's a very useful tool pre-installed on Kelly Linux Reg Ripper.

03:27.610 --> 03:30.870
It's a program written in Perl by Harlan Carvey.

03:30.880 --> 03:34.450
It comes in the form of both a g y and a Seelye tool.

03:34.480 --> 03:40.270
It's originally been written for Windows but also runs on Linux through the wine program.

03:40.360 --> 03:46.800
Reg Ripper has a modular structure as it's capable of running many plug ins on the high files each plug

03:46.800 --> 03:49.460
in extracting different types of artifacts.

03:49.480 --> 03:51.400
There are hundreds of plug ins available.

03:51.400 --> 03:56.860
Also written in Perl that are continuously being updated and everyone could write and add their plug

03:56.860 --> 03:57.880
ins.

03:57.940 --> 04:01.130
We're going to use the graphical version before running the tool.

04:01.150 --> 04:07.990
If our forensic system is 64 bit we'll have to install the 32 bit version of wine to do so let's execute

04:07.990 --> 04:09.310
the following command.

04:09.310 --> 04:16.380
Then we run the usual apt get install command.

04:16.430 --> 04:19.990
In this case the output says 132 is already installed.

04:20.030 --> 04:26.090
Reg Ripper works on registry hives so we must find a way to take them out of our split roll images.

04:26.120 --> 04:33.890
It's here that comes to our rescue a tool from the Libs suite AFFO use this tool could combine all the

04:33.890 --> 04:38.750
image files into a single one that we can then mount under our local file system.

04:38.810 --> 04:45.980
First we create a Malle directory for example and then image then we list the files in the current directory.

04:45.980 --> 04:52.580
We notice that we have renamed the files adding the digit 0 because that use only accepts image names

04:52.700 --> 04:54.590
that end with three digits.

04:54.890 --> 05:00.120
Now we can execute the use command given the input of the image files.

05:00.170 --> 05:05.870
This case we named the first image file and the directory display the content of the image directory.

05:05.960 --> 05:08.590
We could see that the image file has been created.

05:08.600 --> 05:12.090
These files combines all the split image files.

05:12.230 --> 05:16.700
Then we come down to the Mount image directory then create a mail directory.

05:16.700 --> 05:19.130
Now we can execute the Malc command.

05:19.130 --> 05:25.130
Note that we have used the ARO option to mount the image read only and specify the offset of the NTFS

05:25.130 --> 05:29.490
partition which is in bytes starting sector 63.

05:29.510 --> 05:33.170
Multiply by sector size 512 bytes.

05:33.170 --> 05:39.920
Now we can access the file system under NMT suspect and move to the Windows system 32 config directory

05:40.430 --> 05:42.920
where the registry hives are located.

05:42.920 --> 05:48.570
We have to copy the Sam security software and system HIV's to our examination directory.

05:48.830 --> 05:51.350
Then we move to the user profiles directory.

05:51.350 --> 05:58.690
In our case a Windows XP system is Documents and Settings then we would have to copy the end to user

05:58.710 --> 06:03.650
dot dot and the User class dot dot HIV's of all the user accounts.

06:03.770 --> 06:08.900
Now that we have all the registry hives we can execute Reg ripper to run the program.

06:08.900 --> 06:15.950
We click on the applications menu then forensics digital forensics Reg Ripper the interface.

06:15.950 --> 06:17.930
The program is very simple.

06:18.230 --> 06:25.020
First we have to select the high files Samm then select the output report file and the profile.

06:25.220 --> 06:29.930
The profile defines a list of plugins that are going to be executed on the hive.

06:29.930 --> 06:36.170
Each type of pipe has its relative profile and we can select it in the dropdown menu.

06:36.170 --> 06:39.260
In this case we select system plug in file.

06:39.260 --> 06:44.360
We click on the repeat button and the status of all the running plugins is displayed in the text window

06:44.360 --> 06:45.270
below.

06:45.590 --> 06:50.640
When the execution is finished the status bar at the bottom of the window shows done.

06:50.690 --> 06:55.570
We repeat this procedure for each registry hives selecting the appropriate profile.

06:55.610 --> 07:00.950
Now that all the hives have been analyzed we can open some of the report files with a text editor to

07:00.950 --> 07:03.320
give a look to the extracted information.

07:03.320 --> 07:08.950
We first open the same report file as we could see shows info about users and groups.

07:09.170 --> 07:14.000
Here's the most useful information seemed to be when the accounts had been created and the last log

07:14.000 --> 07:14.900
in time.

07:14.990 --> 07:16.980
Then we open the system report file.

07:17.210 --> 07:21.220
But here we will use the Liberty office to show it more clearly.

07:21.380 --> 07:27.830
In particular interesting information are reported about the computer's name I.D. hard disks mounted

07:27.830 --> 07:34.890
drives network interfaces list of services and drivers and at the bottom the USP drives connected.

07:35.030 --> 07:41.690
It's usually a very useful information for forensic investigation because a list all connected USP devices

07:42.140 --> 07:46.990
and the time when they've been connected the model and the serial number of the device.

07:47.060 --> 07:50.020
We take a look at the end to user Deedat report file.

07:50.050 --> 07:53.900
We're going to find the information relative to the user's activities.

07:53.900 --> 08:00.160
The first are the more you list that provide the most recently used files also grouped by file type.

08:00.200 --> 08:07.280
Other important registry keys are the typed paths and type q r l keys and the autostart keys.

08:07.280 --> 08:12.600
The latter lists all the programs or services that are automatically started when the user logs in.

08:16.370 --> 08:23.390
The main one of these keys is a software Microsoft Windows current version run key.

08:23.390 --> 08:28.970
These keys are one of the main indicators of a malware infection because malware typically uses these

08:28.970 --> 08:31.680
keys to achieve persistence on the system.

08:32.600 --> 08:38.300
Another important key to consider is the user assist key that displays a list of the programs executed

08:38.660 --> 08:42.370
along with the date time and the running count.

08:42.380 --> 08:45.680
There are a lot of info and artifacts that can be retrieved from the registry.

08:45.830 --> 08:50.530
In this video we only looked at those which are generally considered the most relevant.

08:50.690 --> 08:56.090
As with any type of artifacts their importance greatly depends on what you're looking for.

08:56.090 --> 09:03.030
Great job in this video we introduce the Windows registry its structure locations and features.

09:03.050 --> 09:08.000
Then we looked at reg Ripper and have shown how to practically extract and analyze the most relevant

09:08.030 --> 09:14.900
artifacts in the next video extracting and analyzing browser and e-mail and instant messaging artifacts.

09:14.900 --> 09:20.750
We're going to cover the tools available on Kelly Linux to extract and analyze forensic artifacts of

09:20.750 --> 09:23.220
the most common browser and email.

09:23.240 --> 09:24.460
And I am clients.
