Article 18.2: Processing obligations for the Controller

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

Except for cases stated in paragraph (3) of Article 10 of the Law, when the Controller processes Personal Data for a purpose other than the one for which it was initially collected as provided in paragraphs (1), (2), (4), (5), and (6) of Article 10 of the Law, the Controller shall comply with the following:

  1. Clearly and accurately define the purpose of the Processing and refer to it in the records of Personal Data Processing activities.
  2. Limit the Collection and Processing of the Personal Data to the minimum amount necessary to achieve the purpose.
  3. Identify the type of Personal Data to be processed and the necessary measures to ensure that such data is processed appropriately.

This requirement is part of the framework:  
Personal Data Protection Law (Saudi Arabia)

Other requirements of the framework

49457
Article 18.2: Processing obligations for the Controller
No items found.
Best practices
How to implement:
Article 18.2: Processing obligations for the Controller
This policy on
Article 18.2: Processing obligations for the Controller
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

Except for cases stated in paragraph (3) of Article 10 of the Law, when the Controller processes Personal Data for a purpose other than the one for which it was initially collected as provided in paragraphs (1), (2), (4), (5), and (6) of Article 10 of the Law, the Controller shall comply with the following:

  1. Clearly and accurately define the purpose of the Processing and refer to it in the records of Personal Data Processing activities.
  2. Limit the Collection and Processing of the Personal Data to the minimum amount necessary to achieve the purpose.
  3. Identify the type of Personal Data to be processed and the necessary measures to ensure that such data is processed appropriately.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
Article 18.2: Processing obligations for the Controller
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
Article 18.2: Processing obligations for the Controller
of the framework  
Personal Data Protection Law (Saudi Arabia)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Procedure for introducing new personal data processing purposes
Critical
High
Normal
Low

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.