Article 3.1: Procedure upon receipt of request from the Data Subject

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

1. The Controller shall, upon receiving a request from the Data Subject regarding their rights as stipulated in the Law, do the following:

  1. Act on the request of the Data Subject for exercising their rights under the Law within a period not exceeding (30) days and without delay. This period may be extended in case the implementation requires disproportionate effort, or if the Controller receives multiple requests from the data subject, provided that the extension does not exceed an additional (30) days and the Data Subject is notified in advance of the extension with the reasons for the delay.
  2. Take the necessary technical, administrative, and organizational measures to ensure a prompt response to requests related to exercising rights.
  3. Take appropriate measures to verify the identity of the requester before executing the request in accordance with relevant legal requirements.
  4. Take the necessary measures to document and keep record of all submitted, including oral requests.

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

Other requirements of the framework

49439
Article 3.1: Procedure upon receipt of request from the Data Subject
Best practices
How to implement:
Article 3.1: Procedure upon receipt of request from the Data Subject
This policy on
Article 3.1: Procedure upon receipt of request from the Data Subject
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, upon receiving a request from the Data Subject regarding their rights as stipulated in the Law, do the following:

  1. Act on the request of the Data Subject for exercising their rights under the Law within a period not exceeding (30) days and without delay. This period may be extended in case the implementation requires disproportionate effort, or if the Controller receives multiple requests from the data subject, provided that the extension does not exceed an additional (30) days and the Data Subject is notified in advance of the extension with the reasons for the delay.
  2. Take the necessary technical, administrative, and organizational measures to ensure a prompt response to requests related to exercising rights.
  3. Take appropriate measures to verify the identity of the requester before executing the request in accordance with relevant legal requirements.
  4. Take the necessary measures to document and keep record of all submitted, including oral requests.

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 3.1: Procedure upon receipt of request from the Data Subject
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 3.1: Procedure upon receipt of request from the Data Subject
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 data sets for data stores
Critical
High
Normal
Low
Publication and maintenance of privacy notice reports
Critical
High
Normal
Low
1
requirements
Privacy
Informing and data subject requests

Publication and maintenance of privacy notice reports

This task helps you comply with the following requirements

Documentation of personal data processing purposes
Critical
High
Normal
Low
2
requirements
Privacy
Informing and data subject requests

Documentation of personal data processing purposes

This task helps you comply with the following requirements

Supporting data subject requests with administrative and technical measures
Critical
High
Normal
Low
1
requirements
Privacy
Informing and data subject requests

Supporting data subject requests with administrative and technical measures

This task helps you comply with the following requirements

Process for receiving and handling data subject requests
Critical
High
Normal
Low
Identification of the rights available to the data subject
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.