Content library
Cyberday content library
Privacy by design and default

Requirement description

How to fill the requirement

Cyberday content library

Privacy by design and default

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
Privacy and Data Protection policy -report publishing, informing and maintenance
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
2
requirements

Examples of other requirements this task affects

9.1: Data Protection Policies
TISAX
9.1.1: Data Protection policies
TISAX
See all related requirements and other information from tasks own page.
Go to >
Privacy and Data Protection policy -report publishing, informing and maintenance
1. Task description

The ogranization must have a privacy and data protection policy created and it must be regularly updated and approved by organization's management.

Measuring and developing a data protection culture in the organization
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
1
requirements

Examples of other requirements this task affects

68: Tietosuojan tila organisaatiossa
Sec overview
See all related requirements and other information from tasks own page.
Go to >
Measuring and developing a data protection culture in the organization
1. Task description

Taking care of data protection is purposefully aimed at forming part of the organizational culture, and the implementation of this is regularly evaluated.

In addition, the organization has defined clear methods of operation to measure staff attitudes towards data protection (e.g. surveys, tests). The measurement results are interpreted and clear measures are formed based on them.

Henkilötietojen säilytyksen rajoittamisen tarkistaminen
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
1
requirements

Examples of other requirements this task affects

TSU-11: Säilytyksen rajoittaminen
Julkri
See all related requirements and other information from tasks own page.
Go to >
Henkilötietojen säilytyksen rajoittamisen tarkistaminen
1. Task description

Organisaatio säilyttää henkilötietoja muodossa, josta rekisteröity on tunnistettavissa, ainoastaan niin kauan, kun on tarpeen tietojen käsittelyn tarkoitusten toteuttamista varten.

Periaatteen toteutuminen tulisi varmistaa säännöllisesti kokonaisuuden näkökulmasta analysoimalla hallintajärjestelmän dokumentaatiota (etenkin määritellyt tietoaineistojen säilytysajat) ja myös vertaamalla dokumentaatiota tietojen todelliseen poistamiseen.

Henkilötunnuksen käsittelyperusteiden tunnistaminen ja dokumentointi
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
1
requirements

Examples of other requirements this task affects

TSU-07.2: Käsittelyn lainmukaisuus - Henkilötunnus
Julkri
See all related requirements and other information from tasks own page.
Go to >
Henkilötunnuksen käsittelyperusteiden tunnistaminen ja dokumentointi
1. Task description

Organisaatio tunnistaa kaikki henkilötietojen käsittelytoimet, joissa käytetään henkilötunnusta. Organisaatio varmistaa kunkin käsittelytoimen osalta, että henkilötunnuksen käytölle on laissa hyväksytty peruste.

Henkilötunnusta saa käsitellä rekisteröidyn suostumuksella tai, jos käsittelystä säädetään laissa. Lisäksi henkilötunnusta saa käsitellä, jos rekisteröidyn yksiselitteinen yksilöiminen on tärkeää:

  • laissa säädetyn tehtävän suorittamiseksi;
  • rekisteröidyn tai rekisterinpitäjän oikeuksien ja velvollisuuksien toteuttamiseksi; tai
  • historiallista tai tieteellistä tutkimusta taikka tilastointia varten.
Process for destruction of temporary files
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
2
requirements

Examples of other requirements this task affects

A.7.4.6: Temporary files
ISO 27701
See all related requirements and other information from tasks own page.
Go to >
Process for destruction of temporary files
1. Task description

The organization should have a documented process for disposing of temporary data generated as a result of personal data processing within the specified time.

Disposal should be carried out by clearing or destroying temporary files in accordance with the procedure within a set schedule.

Goals related to restrictions of processing
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
1
requirements

Examples of other requirements this task affects

A.7.4.4: PII minimization objectives
ISO 27701
See all related requirements and other information from tasks own page.
Go to >
Goals related to restrictions of processing
1. Task description

The organization must identify different processing situations in which it may be necessary to limit the processing of personal data and the amount of personal data in relation to their purposes. This may include e.g. removal of data allowing identification and other data processing limitation techniques.

The organization should determine and document the restriction goals for data processing and the mechanisms used to implement the goals.

Ensuring and documenting the accuracy of personal data
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
3
requirements

Examples of other requirements this task affects

A.7.4.3: Accuracy and quality
ISO 27701
TSU-12: Täsmällisyys
Julkri
P7.1: Collection and maintainment of accurate and relevant personal information
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Ensuring and documenting the accuracy of personal data
1. Task description

The organization should have a process for regularly assessing the accuracy and correctness of personal data, making necessary updates, and notifying data recipients of corrections.

The more important the accuracy of the information is, the more measures the controller must take to ensure the correctness of the information. Ensuring the correctness of the information is particularly important when decisions relevant to the individual are made on the basis of personal information. In this case, inaccurate and incorrect information can seriously endanger the data subject's rights (e.g. lead to incorrect treatment decisions).

Reviewing the execution of data minimisation
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
3
requirements

Examples of other requirements this task affects

A.7.4.1: Limit collection
ISO 27701
TSU-10: Tietojen minimointi
Julkri
P7.1: Collection and maintainment of accurate and relevant personal information
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Reviewing the execution of data minimisation
1. Task description

The organization should limit the collection of personal data to the minimum level that is essential and necessary for the purpose of processing the personal data collected.

The realization of the principle should be ensured regularly from the point of view of all processing by comparing the documentation of the management system (e.g. the purposes of use of the data) with the personal data held by the organization in practice.

Henkilötietojen käyttötarkoitussidonnaisuuden tarkistaminen
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
2
requirements

Examples of other requirements this task affects

TSU-09: Käyttötarkoitussidonnaisuus
Julkri
P4.1: Limiting use of personal information to purposes according to objectives related to privacy
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Henkilötietojen käyttötarkoitussidonnaisuuden tarkistaminen
1. Task description

Organisaatio kerää henkilötietoja vain tietyssä, nimenomaisessa ja laillisessa tarkoituksessa, eikä käsittele henkilötietoja alkuperäisten tarkoitusten kanssa yhteensopimattomalla tavalla myöhemmin.

Periaatteen toteutuminen tulisi varmistaa säännöllisesti kokonaisuuden näkökulmasta vertaamalla hallintajärjestelmän dokumentaatiota (etenkin tietojen käyttötarkoitukset) henkilötietojen todelliseen hyödyntämiseen organisaation arjessa.

Henkilötietojen tarpeellisuuden ja oikeasuhtaisuuden tarkistaminen
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
2
requirements

Examples of other requirements this task affects

TSU-08: Tarpeellisuus ja oikeasuhtaisuus
Julkri
P3.1: Collection of personal information is consistent with objects related to privacy
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Henkilötietojen tarpeellisuuden ja oikeasuhtaisuuden tarkistaminen
1. Task description

Organisaatio varmistaa, että henkilötietojen käsittely on tarpeellista ja oikeasuhtaista käsittelyn laillisten tarkoitusten saavuttamiseksi. Henkilötietoja olisi käsiteltävä vain, jos käsittelyn tarkoitusta ei voida kohtuullisesti toteuttaa muilla keinoilla.

Periaatteen toteutuminen tulisi varmistaa säännöllisesti kokonaisuuden näkökulmasta analysoimalla hallintajärjestelmän dokumentaatiota (etenkin tietojen käyttötarkoitukset).

Regular, internal review of privacy policies
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
4
requirements

Examples of other requirements this task affects

25. Data protection by design and by default
GDPR
A.7.2.1: Identify and document purpose
ISO 27701
TSU-15: Osoitusvelvollisuus
Julkri
P8.1: Periodic monitoring of privacy compliance
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Regular, internal review of privacy policies
1. Task description

The task of the Data Protection Officer (or other responsible person) is to monitor that the Data Protection Regulation and other data protection requirements are complied with in the organisation's operations.

In making her assessment, the responsible person shall take into account the risk associated with the processing operations and of the nature, extent, context and purposes of the processing of personal data.

Pseudonymisation of personal data
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
2
requirements

Examples of other requirements this task affects

32. Security of processing
GDPR
8.11: Data masking
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Pseudonymisation of personal data
1. Task description

Pseudonymisation means the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information.

Anonymization of personal data
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
2
requirements

Examples of other requirements this task affects

32. Security of processing
GDPR
8.11: Data masking
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Anonymization of personal data
1. Task description

Anonymisation means modifying personal information so that the person can no longer be identified from it. For example, data can be roughened to a general level or data about an individual can be deleted. Identification is irreversibly prevented in anonymisation, in contrast to pseudonymisation, where data can be restored to their original form using additional information.

Regular external auditing of privacy policies
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Privacy
Privacy by design and default
1
requirements

Examples of other requirements this task affects

P8.1: Periodic monitoring of privacy compliance
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Regular external auditing of privacy policies
1. Task description

The organization regularly conducts privacy audit. For example, the audit identifies shortcomings and development needs related to the processing of personal data and the processing of personal data.

Universal cyber compliance language model: Comply with confidence and least effort

In Cyberday, all frameworks’ requirements are mapped into universal tasks, so you achieve multi-framework compliance effortlessly.

Security frameworks tend to share the common core. All frameworks cover basic topics like risk management, backup, malware, personnel awareness or access management in their respective sections.
Cyberday’s universal cyber security language technology creates you a single security plan and ensures you implement the common parts of frameworks just once. You focus on implementing your plan, we automate the compliance part - for current and upcoming frameworks.
Start your free trial
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.
1.1 (MIL2): Manage IT and OT Asset Inventory
C2M2: MIL1
1.1 (MIL3): Manage IT and OT Asset Inventory
C2M2: MIL1
1.1.1: Availability of information security policies
TISAX
1.1.1: Identify the organisation’s strategy and priorities
NSM ICT-SP
1.1.2: Identify the organisation’s structures and processes for security management
NSM ICT-SP
1.1.3: Identify the organisation’s processes for ICT risk management
NSM ICT-SP
1.1.4: Identify the organisation’s tolerances for ICT risk
NSM ICT-SP
1.1.5: Identify the organisation’s deliverables, information systems and supporting ICT functions
NSM ICT-SP
1.1.6: Identify information processing and data flow
NSM ICT-SP
1.2 (MIL2): Manage Information Asset Inventory
C2M2: MIL1
1.2 (MIL3): Manage Information Asset Inventory
C2M2: MIL1
1.2.1: Establish a process to identify devices and software in use at the organisation
NSM ICT-SP
1.2.1: Scope of Information Security management
TISAX
1.2.2: Establish organisational guidelines for approved devices and software
NSM ICT-SP
1.2.2: Information Security Responsibilities
TISAX
1.2.3: Identify devices in use at the organisation
NSM ICT-SP
1.2.3: Information Security requirements in projects
TISAX
1.2.4: Definition of responsibilities with service providers
TISAX
1.2.4: Identify the software in use at the organisation
NSM ICT-SP
1.2: Manage Information Asset Inventory
C2M2: MIL1
1.3 (MIL2): Manage IT and OT Asset Configuration
C2M2: MIL1
1.3 (MIL3): Manage IT and OT Asset Configuration
C2M2: MIL1
1.3.1: Identification of information assets
TISAX
1.3.1: Identify the users of the information systems
NSM ICT-SP
1.3.2: Classification of information assets
TISAX
1.3.2: Identify and define the different user categories
NSM ICT-SP
1.3.3: Identify roles and responsibilities linked especially to ICT security
NSM ICT-SP
1.3.3: Use of approved external IT services
TISAX
1.3.4: Use of approved software
TISAX
1.3: Manage IT and OT Asset Configuration
C2M2: MIL1
1.4 (MIL2): Manage Changes to IT and OT Assets
C2M2: MIL1
1.4 (MIL3): Manage Changes to IT and OT Assets
C2M2: MIL1
1.4.1: Management of Information Security Risks
TISAX
1.4: Manage Changes to IT and OT Assets
C2M2: MIL1
1.5 (MIL1): Management Activities for the ASSET domain
C2M2: MIL1
1.5 (MIL2): Management Activities for the ASSET domain
C2M2: MIL1
1.5 (MIL3): Management Activities for the ASSET domain
C2M2: MIL1
1.5.1: Assessment of policies and requirements
TISAX
1.5.2: External review of ISMS
TISAX
1.5: Management Activities for the ASSET domain
C2M2: MIL1
1.6.1: Reporting of security events
TISAX
1.6.2: Management of reported events
TISAX
1.6.3: Crisis preparedness
TISAX
10 §: Johdon vastuu
KyberTL
10. Processing of personal data relating to criminal convictions and offences
GDPR
10.1 (MIL2): Establish Cybersecurity Program Strategy
C2M2: MIL1
10.1 (MIL3): Establish Cybersecurity Program Strategy
C2M2: MIL1
10.1.1: Policy on the use of cryptographic controls
ISO27 Full
10.1.2: Key management
ISO27 Full
10.1.2: Key management
ISO 27017
10.1: Continuous improvement
ISO27k1 Full
10.1: Cryptographic controls
ISO27 Full
10.1: Cryptographic controls
ISO 27017
10.1: Establish Cybersecurity Program Strategy
C2M2: MIL1
10.2 (MIL2): Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2 (MIL3): Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2: Establish and Maintain Cybersecurity Program
C2M2: MIL1
10.2: Non-conformity and corrective action
ISO27k1 Full
10.3 (MIL1): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3 (MIL2): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3 (MIL3): Management Activities for the PROGRAM domain
C2M2: MIL1
10.3: Management Activities for the PROGRAM domain
C2M2: MIL1
10: Cryptography
ISO27 Full
10: Cryptography
ISO 27017
10: Cybersecurity Program Management (PROGRAM)
C2M2: MIL1
10: Prosessi väärinkäytöksiin reagoimiseksi
Sec overview
11 §: Poikkeamailmoitukset viranomaiselle
KyberTL
11. Processing which does not require identification
GDPR
11.1.1: Physical security perimeter
ISO27 Full
11.1.2: Physical entry controls
ISO27 Full
11.1.3: Securing offices, rooms and facilities
ISO27 Full
11.1.4: Protecting against external and environmental threats
ISO27 Full
11.1.5: Working in secure areas
ISO27 Full
11.1.6: Delivery and loading areas
ISO27 Full
11.1: Secure areas
ISO27 Full
11.2.1: Equipment siting and protection
ISO27 Full
11.2.2: Supporting utilities
ISO27 Full
11.2.3: Cabling security
ISO27 Full
11.2.4: Equipment maintenance
ISO27 Full
11.2.5: Removal of assets
ISO27 Full
11.2.6: Security of equipment and assets off-premises
ISO27 Full
11.2.7: Secure disposal or re-use of equipment
ISO27 Full
11.2.7: Secure disposal or re-use of equipment
ISO 27017
11.2.8: Unattended user equipment
ISO27 Full
11.2.9: Clear desk and clear screen policy
ISO27 Full
11.2: Equipment
ISO27 Full
11.2: Equipment
ISO 27017
11: Digiturvan mittarien määrittäminen
Sec overview
11: Physical and environmental security
ISO27 Full
11: Physical and environmental security
ISO 27017
12 §: Luotettavuutta edellyttävien tehtävien tunnistaminen ja luotettavuudesta varmistuminen
TiHL
12 §: Poikkeamaa koskeva väliraportti
KyberTL
12. Transparent information, communication and modalities for the exercise of the rights of the data subject
GDPR
12.1.1: Documented operating procedures
ISO27 Full
12.1.2: Change management
ISO27 Full
12.1.3: Capacity management
ISO27 Full
12.1.4: Separation of development, testing and operational environments
ISO27 Full
12.1: Operational procedures and responsibilities
ISO27 Full
12.2.1: Controls against malware
ISO27 Full
12.2: Protection from malware
ISO27 Full