How To Protect Data and Comply With Data Protection Laws
How To Protect Data and Comply With Data Protection Laws
PDPL KVKK
PDPB SAMA PIPL
GDPR
KVKK BDSG
LGDP
GDPR Sign in
PDPA PDPB
PDPL searchinform.com
SAMA
How to protect personal data and comply with regulations 2
Despite the large amount of various regulations, most of them have some same aims:
prevent unauthorized and illicit access to Personal Data, its disclosure, change or
inappropriate disposal.
In order to meet the regulators’ requirements, organizations, among other things, must:
• Obtain all the personal data, reveal, where it's kept.
• Define, which users should have rights to work with personal data and prevent cases
of illicit access to such data.
• Define the list of resources, which can be used for personal data keeping. Prevent
keeping personal data elsewhere (including users’ workstations) and detect, if there
are any cases of inappropriate data keeping.
• Take preventive measures to ensure safety of the processed data, including users’
access rights management (access rights distribution).
• Take all the required measures to ensure safety of personal data keeping, processing
and transmitting processes (use only approved data processing technologies, data
transmition channels; implement cryptoprotection).
• Analyze information systems’ vulnerabilities.
• Detect and analyze any incidents (quite often, it’s also required to notify the regulator
about the incident and report on the results of the investigation).
• Keep employees up to date in information security related issues
and enhance their IS competencies.
• Many acts contain the requirement, known as Right to be forgotten, which enshrines the
right to have personal data deleted from Internet searches and other directories.
DCAP class solution obtains all the personal data, kept in the organization’s
storages; detects any operations on it and appropriately distributes access
rights to confidential data.
DLP class solution automatically detects a data leak attempt, prevents the
incident and gathers evidence for precise investigation.
SIEM class solution reveals external attacks and other threats, posed to the
personal data processing systems; reveals the correlation between security
events, which caused the incident.
First of all it’s required to obtain and classify all the files, which contain personal data:
passport information, phone numbers, bank card details etc. The FileAuditor solution helps
to deal with this task.
After the configuration of rule in FileAuditor is completed, the solution scans all the
directories, where the data is kept and obtains all the required files. The solution adds the
label to all the documents, containing personal data, what’s more, it ensures control of
users’ operations on files. For instance, thanks to the FileAuditor, the IS officer knows all the
users, who work with such files (e.g. open, edit, delete them). What’s more, with the help of
FileAuditor the employee in charge knows, who has access to these files. Excessive access
rights can be limited as well: the system allows to prohibit reading, editing, resending
documents, containing the specified label (in our case, personal data label) in any
application. Blockings can be applied for all users or only for the specified ones, as well as
they may be applied for some specific workstations solely.
How to protect personal data and comply with regulations 5
How to configure?
Blockings
Blocking implementation
How to protect personal data and comply with regulations 7
At the next stage it’s required to make sure, that all the personal data obtained
won’t leave the corporate perimeter. This can be ensured with the help of the DLP
system.
SearchInform DLP performs analysis of all the data array and in case a violation
of personal data processing is detected, immediately notifies an IS officer about
the incident.
In order to prevent data leaks, the DLP by SearchInform, just like the FileAuditor, enables to
block operations of personal data sending – it doesn’t matter, whether, personal data is
contained in a file or in a text message. The restrictions are applied to email, web-resources,
messengers, flashdrives, remote connections, printers, FTP-connections and any other
channels, controlled by the DLP system. Blockings are content-based and when they are
implemented, the system considers various other attributes as well: for instance, file, PC and
user name; recipient’s email address; file size and format etc.
What’s more, the DLP solution provides the detailed incident map. When conducting an
investigation, it’s possible to find out, what a user did before he/she attempted to leak
personal data; with whom did the user communicate; reveal the motive behind the user’s
action: whether it was an accidental data leak, case of industrial espionage or something else.
How to protect personal data and comply with regulations 9
Additionally, you can configure transmission of incidents, revealed by DLP according to the
security policies to SIEM.
How to protect personal data and comply with regulations 11
How to configure?
Basically, it’s required to provide regulators with the following details on the incident:
• Evaluate the volume of data leaked – how many strings leaked, whether critical
data was exposed.
• Identify the probable data leak channel: email, copying data to external devices,
social networks, cloud services.
In order to mitigate the risk of data leak incident, it’s required
to implement information security (IS)-tools:
• Identify the incident’s culprits: find out, whether an internal insider or external
malicious actor committed the fraudulent activity. It’s also possible, that the data
leak incident happened at your counterparty or governmental body side, so check
everything precisely.
• Identify the circumstances and find out, whether it was an accidental or deliberate
data leak.
• Gather evidence - interview witnesses, download data from DLP, DCAP or SIEM
(desktop screenshots, correspondence archive, audit of file system operations, etc.).
How to protect personal data and comply with regulations 15
Notifying clients
An equally important part for mitigation or the data leak consequences is to explain
what happened exactly to all the affected parties. By sending a notification on the
data leak, you give them a chance to protect themselves afterwards. For instance,
affected parties can change password. Besides, this measure helps you to have more
chances to save your reputation: you can explain, what happened before data is
published in mass media.
Send a simple and easy for understanding email, containing explanations and your
apologizes. Make sure, that the text isn’t complicated, avoid usage of professional
IS-terms. It’s required to explain, what happened exactly, what measures do you take
to investigate the data leak incident, what risks does the incident pose to the affected
parties and how they can mitigate risks (change passwords, implement two-factor
authentication etc.). You can also offer a compensation: bonus, discount or gift.
After apologizing to customers notify mass media representatives about the data leak.
It’s advised to stick to the following position: "We made a mistake, however, we’re
working on mitigation of the incident’s consequences and we’ll do our best not to let
such an incident happen again."
How to protect personal data and comply with regulations 16
First of all, to prevent incidents it’s required to ensure advanced information security
protection. With the help of DCAP solution you can trace the lifecycle of personal
data, in DLP you can trace such data copying, in SIEM – unwanted access to the
directories, where personal data is kept. It’s helpful to use additional tools in IS
solutions, such as user notifications and blockings, as they help to mitigate risks
significantly.
• Introduce liability for disclosure of confidential information and data leakage. Sign
an NDA (non-disclosure agreement) with employees. Employees must understand
the responsibility for disclosing critical information.
Prevention will reduce the risk of the incident happening again. This is not a one-time
action; such measures should be permanent.