Plagiarism-Report 1

PLAGIARISM SCAN REPORT
Date 2023-05-17

0%
100%
Words 708
Plagiarised Unique
Characters 4892
Content Checked For Plagiarism
CHAPTER 1 INTRODUCTION

1.1 Identification of Client / Contemporary issue

Client: Big Companies whose most of the work is relied on the data exchange between different departments. Hospitals
who share sensitive data of the patients with the research laboratories. Any organization that shares confidential data with
other of their trusted agents and if leaked can result in huge loses to the organization.

Need: Today every organization works on a lot of data which is shared between different departments of the organization
or so called the trusted agents and also some of the third-party agents. Thus, the value of an organization is measured
using the data it generates and how it uses that data to improve themselves or their services. If this confidential data is
leaked then it will result in the deprecation of the value of the organization and its integrity. Therefore, we need to ensure
the security of this data.

1.2 Identification of Problem

A number of issues can develop in a data leakage detection system that reduce its effectiveness. False positives and false
negatives—where acceptable actions are mistakenly reported as cases of data leakage or real occurrences are overlooked
—are frequent problems. Inadequate data classification can make it difficult for the system to recognize and safeguard
sensitive information. Data breaches may go undiscovered due to low visibility across several channels, such as email or
file-sharing websites. It may be difficult to distinguish between typical and suspect activity if user behavior profiling is
inaccurate. Data leakage may become more likely if privileged users who have access to sensitive information are not
sufficiently monitored.

The system's capacity to correlate events and identify potential leaks is constrained by a lack of integration with other
security technologies. Inadequate employee data security training and awareness might leave workers vulnerable to social
engineering attacks or unintended data releases. To find new or undiscovered dangers that might elude conventional
detection methods, proactive threat hunting is crucial. Data leakage issues may be handled slowly or incorrectly due to
inadequate incident response skills and a lack of well-defined response protocols. Last but not least, skipping routine
system upgrades and maintenance makes the system more susceptible to fresh attack vectors and less effective at spotting
and stopping data leaks.

1.3 Identification of Tasks
Identify: The identification phase involves determining the requirements for the Data Leakage Detection System. This
includes understanding the needs of the people, the technology stack to be used, and the overall scope of the project.
Some of the tasks related to this phase are listed below:

Page 1 of 2
• Understanding the different data leakage sources and causes.
• Defining the functional and non-functional requirements for Data Leakage Detection System.

• Defining the user stories and use cases to identify the features required.

• Selecting the appropriate technology stack.

Build: The building phase involves developing the software based on the requirements identified in the previous phase.
This involves the following tasks:

• Building a watermarking system that is more efficient than the pre-existing systems and embedding codes in it which
can be later used to identify the data.

• Conducting and evaluating the software for a given use case.

Test: The testing phase involves verifying that the software meets the requirements and functions as intended. This includes
the following tasks:

• Conducting unit testing, integration testing, and system testing to ensure that the detection system functions
correctly.
•
Conducting user acceptance testing to ensure that the software meets the needs of the people outside.

• Conducting security testing to identify and fix any vulnerabilities.

• Conducting performance testing to ensure that the software can
handle different use cases. Fixing any bugs and
issues identified during testing.

In summary, the identification phase involves determining the requirements for the people outside, the building phase
involves developing the program based on these requirements, and the testing phase involves verifying that the program
would meet the requirements and functions as intended.

1.4 Timeline

Review of Data Leakage Detection System Calendar

Phase 1- Project Scope, Planning and Task definition
[Feb 8 – March 14] Phase 2- Literature Review [March 14 – April 10]

Phase 3- Preliminary design [April 10 – April 30]

Phase 4- Detailed System Design/Technical Details
[April 30 – May 17] Phase 5- Work Ethics [Feb 8 – May 17]
Matched Source
No plagiarism found
Page 2 of 2

Plagiarism-Report 1

Uploaded by

Copyright:

Available Formats

Plagiarism-Report 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Plagiarism-Report 1

Uploaded by

Copyright:

Available Formats

PLAGIARISM SCAN REPORT

Content Checked For Plagiarism

1.1 Identification of Client / Contemporary issue

1.2 Identification of Problem

1.3 Identification of Tasks

• Selecting the appropriate technology stack.

• Conducting and evaluating the software for a given use case.

• Conducting security testing to identify and fix any vulnerabilities.

Review of Data Leakage Detection System Calendar

Phase 3- Preliminary design [April 10 – April 30]

You might also like