Data encryption/sl: Difference between revisions
From LimeSurvey Manual
Maren.fritz (talk | contribs) (Created page with "*vrsta podatkov, ki jih zbirate *če vaša anketa temelji na *nacionalni ali zvezni zakonodaji") |
Maren.fritz (talk | contribs) (Created page with "Največkrat je pomembno šifrirati podatke, ki omogočajo osebno identifikacijo (npr. kot priporoča Splošna uredba o varstvu podatkov). Zato se lahko polja, kot so ime, prii...") |
||
Line 28: | Line 28: | ||
*nacionalni ali zvezni zakonodaji | *nacionalni ali zvezni zakonodaji | ||
Največkrat je pomembno šifrirati podatke, ki omogočajo osebno identifikacijo (npr. kot priporoča Splošna uredba o varstvu podatkov). Zato se lahko polja, kot so ime, priimek, e-poštni naslov, telefonska številka, naslov itd., uporabijo za prepoznavanje odgovorov, ki jih je poslala ena oseba. | |||
In other cases, the data that should be encrypted does not necessarily stop at the examples provided above. In certain scenarios (e.g., in medical research), you might need to encrypt most of your data if you can track back the responses to the person who submitted them. | In other cases, the data that should be encrypted does not necessarily stop at the examples provided above. In certain scenarios (e.g., in medical research), you might need to encrypt most of your data if you can track back the responses to the person who submitted them. |
Revision as of 10:19, 14 December 2023
Uvod
Šifriranje podatkov je nova funkcija, ki je na voljo v LimeSurvey 4. Ustvarjena je bila za pomoč skrbnikom anket pri boljšem soočanju z novimi predpisi o varstvu podatkov, sprejetimi v različnih delih sveta (npr. GDPR).
Ta funkcija omogoča šifriranje osebnih podatkov, ki se nahajajo v osrednji podatkovni bazi udeležencev in/ali tabeli udeležencev ankete. Poleg tega lahko tudi šifrirate podatke, ki jih zberete od anketirancev, če je omogočen atribut vprašanja za šifriranje.
Upoštevajte, da bodo vaši podatki vedno vidni v vmesniku LimeSurvey. Šifrirani so samo vnosi v bazo podatkov - nihče, ki dostopa do strežnika, kjer gostite LimeSurvey, ne more vizualizirati ustreznih podatkov. Zato bodite pozorni, komu dajete globalna in anketna dovoljenja.
Kdaj šifrirati svoje podatke?
Na to vprašanje ni enega pravilnega odgovora. Močno je odvisno od:
- vrsta podatkov, ki jih zbirate
- če vaša anketa temelji na
- nacionalni ali zvezni zakonodaji
Največkrat je pomembno šifrirati podatke, ki omogočajo osebno identifikacijo (npr. kot priporoča Splošna uredba o varstvu podatkov). Zato se lahko polja, kot so ime, priimek, e-poštni naslov, telefonska številka, naslov itd., uporabijo za prepoznavanje odgovorov, ki jih je poslala ena oseba.
In other cases, the data that should be encrypted does not necessarily stop at the examples provided above. In certain scenarios (e.g., in medical research), you might need to encrypt most of your data if you can track back the responses to the person who submitted them.
As a result, please adapt your survey and the data collection to the local legislation!
Settings
There are three places in LimeSurvey where data encryption settings can be set:
Question attributes
Question attribute "Encrypted" is used to enable data encryption for corresponding responses. This attribute is turned off by default. Once survey is activated, it is not possible to change this attribute.
Participant attributes
Three core attributes (firstname, lastname, and email) are always shown in the survey participants table, the encryption being turned on by default.
Each new participant attribute will have encryption turned off by default.
Encryption can be turned on or off at any moment.
Central participant database attribute management
Three core attributes (firstname, lastname and email) are always shown in the central participant database, the encryption being turned on by default.
Each new participant attribute will have encryption turned off by default.
Encryption can be turned on or off at any moment.
Advanced
Sodium library is used to provide data encryption and decryption functionality for LimeSurvey.
Sodium is a modern, easy-to-use software library for encryption, decryption, signatures, password hashing and more. It is a portable, cross-compilable, installable, packageable fork of NaCl, with a compatible API, and an extended API to improve usability even further. Its goal is to provide all of the core operations needed to build higher-level cryptographic tools.
Sodium is cross-platforms and cross-languages. It runs on a variety of compilers and operating systems, including Windows (with MinGW or Visual Studio, x86 and x86_64), iOS and Android. Javascript and WebAssembly versions are also available and are fully supported. Bindings for all common programming languages are available and well-supported.
Version 7.2.0 and newer of the PHP programming language includes the Sodium extension (referred to as ext/sodium) as a core cryptography library. Version 2 of the PHP extension in PECL is compatible with ext/sodium in PHP 7.2.
LimeSurvey uses the Sodium Compat library to bridge with different PHP versions.
This library tentatively supports PHP 5.2.4 - 7.x (latest), but officially it only supports non-EOL'd versions of PHP.
Data encryption/decryption methods used in LimeSurvey are based on public-key signatures. Public and secret keys can be found in /application/config/security.php file. Keys are automatically generated on first usage of encryption feature.
Partial string search won't be possible for database columns with encrypted data, only exact match search.
Errors
Possible errors when using data encryption:
- library doesn't exists: PHP Sodium library have to be installed to be able to use data encryption feature. Here is a guide on how to install library: Sodium installation. If you don't want to use data encryption, you have to disable encryption in attribute settings.
- wrong decryption key: decryption key has changed since data was last saved, so data can't be decrypted. The only way to decrypt data is to retrieve the original key from backup and replace the current decryption key with the original key.
Note: if the wrong decryption key error happens only when LimeSurvey sends an email (e.g. when you concluded a survey), go in Configuration > Global Settings > E-mail settings, and re-insert your STMP password and press Save.[1]
Otherwise, you can still try to compare and eventually recover your decryption keys from a backup (since you do backups... isn't it? Uh?).