Ca2 797
Ca2 797
Student Declaration
for the partial fulfilment of the requirements for the award of the degree,
“Masters in Computer application”.
Dated: 07/April/2023
Disclaimer: I have not performed any live investigation. This was a part of our university assignment,
CONTENTS
where I assumed the roles of forensics investigator, determining what methods were applicable.
Page
1. Case Study
1.1 Scenario overview --------------------------------- 3
1.2 Deliverables ---------------------------------------- 4
1.3 Methodology --------------------------------------- 4 - 5
1.4 Guidelines and Principle ------------------------ 5 - 6
4. Analysis ------------------------------------------- 14
5. Results -------------------------------------------- 15 - 19
5.1 Findings ------------------------------------------ 19 - 20
1.3 Methodology
I started the project running a desktop with Ryzen 5 4000 Series and 8GB of
RAM. The computer ran a 64-bit Windows 10 Enterprise edition operating
system with Service Pack 1. The computer was given the final name of
PhagwaraMcase.
After set-up was complete, we were given a 250GB internal hard drive
containing Fire. Fire was the result a previous project where information was
generated on a hard drive from Windows, Mac, and Linux. Our team utilizes
this hard drive when working on other forensic research projects in order to
set a base line. Using this hard drive, we can create an image to test all the
programs using the same example.
Most computers will have programs that will lengthen the time it takes to
image the drive, so we decided to use the Fire II drive to comply with time
constraints.
The chosen framework, Digital Forensic Research Conference (DFRWS)
Investigative Model (2001) – Palmer, proposing a well-known digital
forensic investigation process consists of seven components such as:
2.1.1 Photographs
2.2 Preservation
In this stage, should works on isolation, securing and preserving the physical
and digital evidence. This helps to maintain the integrity of the digital
evidence and protect the digital evidence from the modifications. Examiners
should be responsible and must demonstrate that the evidence should be
preserved through all steps in the process like in collection phase, examine
phase, analyse phase, etc. Preservation of the digital and physical evidence
should be done by trained and skilled staff members that possess the required
techniques and the knowledge of using appropriate tools.
Methods to preserve the digital evidence with this section, following
methods are needed to consider preserving the digital evidence by forensic
examiner.
Drive Imaging
Imaging the drives can help to keep the evidence side and use the images for
the analysis. To perform this imagining, professional make a duplicate of the
drive with completing the sector by sector. There are many tools that to use
for imaging like Acronis, Barracuda etc.
Making copies of the evidence
Copies of the evidence could also help to retain the evidence; copies
should be encrypted with hash values like MD5 in the label of the copies
so can distinguish from Original. Along with that, critical information
like name of the personnel, the date and time and place would be added
with. This helps to verify the authenticity and helps to protect the
integrity. These hash values could be useful in the court case.
Chain of custody
When forensic examiners extract the media from the business and do
transfer their media if it required, should document all the transfer on a
form called Chain of Custody (CoC) and track down all the dates, under
whose supervision etc. If the suspected evidence found, it should be
immediately isolated and keep under the Chain of Custody so the
examiner can create an image later. This is crucial because once if the
evidence not being preserved properly, this might be invalid in court case.
This will motivate GDPR to impose more fines on the business which
may be unable to afford.
FTK imager tools - FTK Imager is a tool for creating disk images and is
absolutely free to use. It was developed by The Access Data Group. It is a
tool that helps to preview data and for imaging.
EWF tool - EWF Tools: working with Expert Witness Files in Linux 2
minute read Expert Witness Format (EWF) files, often saved with an E01
extension, are very common in digital investigations. Many forensic tools
support E01 files, but many non-forensic tools don’t. This is a problem if
you are using other tools, like many Linux utilities to try to do an
investigation.
ewfverify — verifies media data stored in EWF files
ewfverify is a utility to verify media data stored in EWF files.
ewfverify is part of the libewf package. libewf is a library to access the
Expert Witness Compression Format (EWF).
ewf_files the first or the entire set of EWF segment files.
Then I just click on start option and the process will be started. You can
see all the information also.
After finished imaging
Now I have to verify also the file for that I’m using ewfverify tool so we can see
all the verified hash files
DESCRIPTION
ewfverify is a utility to verify media data stored in EWF files.
ewfverify is part of the libewf package. libewf is a library to access the Expert
Witness Compression Format (EWF).
ewf_files the first or the entire set of EWF segment files.
3. Verify the integrity of the data by verifying the log file of an image.
TASK 3
Identify the target storage device: You need to determine which storage device
you want to image. This can be done using a tool such as lsblk or fdisk, which
will show you the available storage devices and their properties. Determine the
output file: You need to specify the location where you want to save the image
file. You can specify either a local file or a network share. Run the dc3dd
command: The dc3dd command is used to create the image of the target storage
device. The basic syntax of the command is:
Task 4
Data carving
This disk image file will be carved for .jpeg, .png, .zip, .pdf and .avi file
formats. We will not be instructing Foremost to carve the .docx but, since one
exists in the .zip we have placed inside the disk image, it will do so
automatically.
To break this down “-t” is setting the file types we want to carve out of the disk
image, here those are .jpeg and .png.
“-i” is specifying the input file, the “disk.img” that is placed on the desktop.
“-o” is telling Foremost where we want the carved files to be stored, for that we
have the “recov” folder on the desktop that we made earlier.
“-v” is to tell Foremost to log all the messages that appear on screen as the file
is being carved into a text file in the output folder (recov) as an audit report.
Task 5
FTK imager analysis
1. Create an image file specifying the necessary information from the
source of evidence.
In the menu navigation bar, you need to click on the File tab which will give
you a drop-down, like given in the image below, just click on the first one
that says, Add Evidence Item.
After that, there will be a pop-up window that will ask you to Select the
Source of the Evidence. If you have connected a physical hard drive to the
laptop/computer you are using to make the forensic image, then you will
select the Physical Drive here.
Click on Next. Now, Select the Physical Drive that you would like to use.
Please make sure that you are selecting the right drive, or you will waste
your time exporting a forensic image of your own OS drive.
In the menu navigation bar, you need to click on the File tab which will give
you a drop-down, like given in the image below, just click on the first one that
says, Add Evidence Item.
there will be a pop-up window that will ask you to Select the Source of the
Evidence. If you have connected a physical hard drive to the laptop/computer
you are using to make the forensic image, then you will select the Physical
Drive here. Click on Next. Now, Select the Physical Drive that you would like
to use. Please make sure that you are selecting the right drive, or you will waste
your time exporting a forensic image of your own OS drive.
Now, we will export the forensic images.
Right-click on the Physical Drive that you would like to export in the FTK
Imager window. Select Export Disk Image here.
Click the Add button for the Image Destination.
Select the Type of Forensic Image you would like to export. Select .E01 and
Click Next.
After that, you will have to enter information regarding the case now. You can
either leave them blank or keep it general, this part is totally upon you.
Fill
ed all the details Below as Screenshots
And, there you have it – a bit-by-bit image of the device! You’ve just captured
everything on the device, including deleted files and slack space data. Next
time, we’ll discuss Adding an Evidence Item to look at contents or drives or
images (including the image we created here).
2. Collect the possible meta information such as PNG/JPEG if any.
There is some file also where some information is regarding company which is
trying to disclose but some image, I found is the following:
3. Generate the hex value of the data found as evidence.
Findings
As a cyber forensic examiner, We conducted a thorough analysis of the
digital evidence collected from the suspect's device. Among the findings
were several images depicting potential evidence of illegal activities,
including images of suspicious financial transactions and confidential
documents. Additionally, there were PDF files containing sensitive
information related to a business deal, as well as blueprints of a high-security
building. Furthermore, I discovered lines of code that appeared to be
malicious in nature, suggesting the suspect may have been involved in
cybercrime. The evidence revealed a complex web of illicit activities,
requiring further investigation and expertise to unravel the full scope of the
suspect's actions.
6. Conclusion
In conclusion, the case of intellectual property theft by a company employee has
been successfully solved. The discovery of a pendrive as the main evidence
proved to be crucial in unraveling the mystery.
Upon thorough investigation, the pendrive was found to contain a treasure trove
of information, including blueprints, bank transactions, and credit card
information. These findings confirmed that the employee had been stealing and
misusing the company's intellectual property for personal gain.
Furthermore, the pendrive also contained malicious code, indicating that the
employee had engaged in unauthorized activities to compromise the company's
security and integrity. This malicious intent added another layer of severity to
the case, making it a serious offense.
Through diligent forensic analysis, the team was able to track the employee's
activities and establish a timeline of events, ultimately leading to the
identification and apprehension of the culprit. The evidence found on the
pendrive was pivotal in securing a conviction, as it provided irrefutable proof of
the employee's illicit actions.
As a result of the successful investigation, the stolen intellectual property was
recovered, and the employee was held accountable for their actions in a court of
law. The company has since implemented robust security measures to prevent
similar incidents from occurring in the future, safeguarding their valuable
intellectual property.
The resolution of this case highlights the importance of protecting intellectual
property and maintaining stringent security protocols within organizations. It
serves as a reminder that intellectual property theft is a serious crime with
severe consequences, and that thorough investigation and forensic analysis are
critical in uncovering the truth and bringing the perpetrators to justice.
In conclusion, the discovery of the pendrive and the critical information it
contained, along with the identification of malicious activities, were key factors
in solving the case of intellectual property theft by the company employee,
ensuring that justice was served and the company's intellectual property
was safeguarded.