Content library
Data classification
Lakisääteisten vaatimusten huomiointi tietoluokitteluun liittyvissä merkinnöissä

Other tasks from the same security theme

Task name
Priority
Status
Theme
Policy
Other requirements
Definition of data classifications and class-specific security procedures
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
29
requirements

Examples of other requirements this task affects

8.2: Information classification
ISO27 Full
8.2.1: Classification of information
ISO27 Full
8.2.2: Labelling of information
ISO27 Full
8.2.3: Handling of assets
ISO27 Full
11.2.5: Removal of assets
ISO27 Full
See all related requirements and other information from tasks own page.
Go to >
Definition of data classifications and class-specific security procedures
1. Task description

Data classification can be used to give data processors a quick view of how critical data is and how data should be processed and protected.

The data categories used and the corresponding security levels are defined. The category of information is defined by analyzing the confidentiality, integrity and availability of the information in question, as well as any other requirements. Each level is given a clear and descriptive name.

Data classifications can be, for example, the following:

  • disclosure of information does not cause harm (PUBLIC)
  • disclosure of information causes slight inconvenience or minor operational annoyance (CONFIDENTIAL)
  • disclosure of information has significant short-term effects on operations or tactical objectives (LIMITED)
  • disclosure of information has serious implications for long-term strategic objectives or jeopardizes the very existence of the organization (PROHIBITED)

CONFIDENTIAL paper information may require e.g. the following protections:

  • Locked cabinet
  • Trusted transfer partner
  • Sealed envelopes
  • Safe disposal process

CONFIDENTIAL electronic information may require e.g. the following protections:

  • Use the selected encryption level
  • Password protection
  • Safe disposal process
  • More limited access rights
Documentation of data classes for data sets
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
21
requirements

Examples of other requirements this task affects

8.2.1: Classification of information
ISO27 Full
18.1.3: Protection of records
ISO27 Full
T07: Tietojen luokittelu
Katakri
ID.AM-5: Resource prioritization
NIST
HAL-04.2: Suojattavat kohteet - luokittelu
Julkri
See all related requirements and other information from tasks own page.
Go to >
Documentation of data classes for data sets
1. Task description

The dataset owners (or the owners of the related information asset, such as a data store or data system) are responsible for the classifications of the datasets and the correspondence of the classification to the definitions of the classes.

The owner updates the data classification over the life cycle of the asset according to variations in its value, sensitivity, and criticality.

Defining and implementing masking for confidential data
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
1
requirements

Examples of other requirements this task affects

8.11: Data masking
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Defining and implementing masking for confidential data
1. Task description

Organization must determine the situations in which the protection of personal data or other confidential data is particularly important, and if necessary implement the hiding of such data using suitably strong methods, for example using masking, pseudonymization or anonymization.

In addition to anonymization and pseudonymization, possible techniques that can be used include:

  • encryption
  • resetting or deleting characters
  • changing values
  • replacing values with hashes
Lakisääteisten vaatimusten huomiointi tietoluokitteluun liittyvissä merkinnöissä
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
1
requirements

Examples of other requirements this task affects

HAL-04.4: Suojattavat kohteet - merkitseminen
Julkri
See all related requirements and other information from tasks own page.
Go to >
Lakisääteisten vaatimusten huomiointi tietoluokitteluun liittyvissä merkinnöissä
1. Task description

Tiedon merkitsemistapojen pitää kattaa sekä fyysisessä että sähköisessä muodossa olevat tiedot ja niihin liittyvä suojattava omaisuus kuten tietovälineet.

Merkintöjen olisi oltava organisaation määrittelemien luokitteluperiaatteiden mukaisia ja helposti tunnistettavia. Organisaation olisi ohjeistettava, mihin ja miten merkinnät kiinnitetään. Ohjeistuksessa tulee ottaa huomioon myös tulosteet. Lisäksi tarpeettoman työn säästämiseksi kannattaa ohjeistaa, milloin merkintöjä ei tarvita.

Tietyissä tapauksissa, kuten esimerkiksi julkisuuslain mukaisista salassa pitoa koskevista merkinnöistä tulee myös käydä ilmi, miltä osin asiakirja on salassa pidettävä sekä mihin salassapito perustuu.



Data classification for offices and physical data assets
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
2
requirements

Examples of other requirements this task affects

No items found.
See all related requirements and other information from tasks own page.
Go to >
Data classification for offices and physical data assets
1. Task description

In addition to the records, the organization has also classified the sites and physical assets based on the criticality of the information they process.

Definitions and instructions on information classifications
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
9
requirements

Examples of other requirements this task affects

8.2.1: Classification of information
ISO27 Full
8.2.2: Labelling of information
ISO27 Full
12.1.1: Documented operating procedures
ISO27 Full
HAL-04.4: Suojattavat kohteet - merkitseminen
Julkri
5.13: Labelling of information
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Definitions and instructions on information classifications
1. Task description

The ways in which information is classified and classifications marked are defined, markings are easily identifiable and they cover both physical and electronic information and assets. The marking must indicate to what extent the document is to be kept secret and on what basis the secrecy is based. Personnel are instructed on how to make markings.

Documentation of data and metadata for designated datatypes
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
1
requirements

Examples of other requirements this task affects

No items found.
See all related requirements and other information from tasks own page.
Go to >
Documentation of data and metadata for designated datatypes
1. Task description

Organization maintains a list of the designated data types of interest that could include for example:

  • Personally identifiable information
  • Protected health information
  • Financial account numbers
  • Organization intellectual property
  • Operational technology data

And tracks and documents metadata, of each instance of these designated data types like:

  • Provenance
  • Data owner
  • Geolocation

The organizations can also continuously discover and analyze ad hoc data to identify new instances of these designated data types.

Identification of confidential information
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
1
requirements

Examples of other requirements this task affects

C1.1: Identification and maintainment of confidental information
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Identification of confidential information
1. Task description

The organization must have a procedure for identifying new datasets containing confidential information during their reception or creation phase.

A retention period must be set for datasets containing confidential information, after which the data is deleted or archived.

Review of data classification procedures
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
2
requirements

Examples of other requirements this task affects

8.2.3: Handling of assets
ISO27 Full
See all related requirements and other information from tasks own page.
Go to >
Review of data classification procedures
1. Task description

The functionality and consistency of the data classification is regularly reviewed in the organization as a whole.

The principles of data classification should be consistent throughout the organization so that everyone has a common understanding of security requirements and equally critical protection is applied to equally critical information.

Marking of equipment that needs safe disposal
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Management of data sets
Data classification
8
requirements

Examples of other requirements this task affects

8.2.2: Labelling of information
ISO27 Full
8.3.2: Disposal of media
ISO27 Full
TEK-21: Sähköisessä muodossa olevien tietojen tuhoaminen
Julkri
5.13: Labelling of information
ISO27k1 Full
CC6.5: Discontinuation of logical physical protections when no longer required
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Marking of equipment that needs safe disposal
1. Task description

There are agreed procedures for identifying and marking media that require safe disposal.

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.