Article 11.1-2: Processing consent

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

1. The Controller shall obtain the Data Subject's consent for Processing their Data in any appropriate form or means, including written or verbal consent or by using electronic methods, subject to the following conditions:

  1. Consent shall be given freely and not obtained through misleading methods, and obtaining consent shall comply with the provisions of Article (7) of the Law.
  2. Processing purposes shall be clear, specific, and shall be explained and clarified to the Data Subject before or at the time of requesting consent.
  3. Consent shall be given by a person who has full legal capacity.
  4. Consent shall be documented in a way that allows verification in the future, such as keeping records that include the Consent of the Data Subjects regarding the Processing operations, along with the time and the method of Consent.
  5. Independent consent shall be obtained for each Processing purpose.

2. The Data Subject's consent shall be explicit in the following cases:

  1. When the Processing involves Sensitive Data.
  2. When the Processing involves Credit Data.
  3. When decisions are made solely based on automated Processing of Personal Data.

Best practices
How to implement:
Article 11.1-2: Processing consent
This policy on
Article 11.1-2: Processing consent
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.

1. The Controller shall obtain the Data Subject's consent for Processing their Data in any appropriate form or means, including written or verbal consent or by using electronic methods, subject to the following conditions:

  1. Consent shall be given freely and not obtained through misleading methods, and obtaining consent shall comply with the provisions of Article (7) of the Law.
  2. Processing purposes shall be clear, specific, and shall be explained and clarified to the Data Subject before or at the time of requesting consent.
  3. Consent shall be given by a person who has full legal capacity.
  4. Consent shall be documented in a way that allows verification in the future, such as keeping records that include the Consent of the Data Subjects regarding the Processing operations, along with the time and the method of Consent.
  5. Independent consent shall be obtained for each Processing purpose.

2. The Data Subject's consent shall be explicit in the following cases:

  1. When the Processing involves Sensitive Data.
  2. When the Processing involves Credit Data.
  3. When decisions are made solely based on automated Processing of Personal Data.

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 11.1-2: Processing consent
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 11.1-2: Processing consent
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
Documentation of personal data processing purposes for data stores
Critical
High
Normal
Low
24
requirements
Privacy
Processing principles and accountability

Documentation of personal data processing purposes for data stores

This task helps you comply with the following requirements

Managing and documenting data subject consent
Critical
High
Normal
Low
1
requirements
Privacy
Processing principles and accountability

Managing and documenting data subject consent

This task helps you comply with the following requirements

Documentation of conditions of consent for relevant processing purposes
Critical
High
Normal
Low
Consent condition review
Critical
High
Normal
Low
3
requirements
Privacy
Processing principles and accountability

Consent condition review

This task helps you comply with the following requirements

Clear communication about the effects of consent
Critical
High
Normal
Low
3
requirements
Privacy
Informing and data subject requests

Clear communication about the effects of consent

This task helps you comply with the following requirements

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.