{"id":168,"date":"2026-03-06T09:59:25","date_gmt":"2026-03-06T09:59:25","guid":{"rendered":"http:\/\/openscience.bc.cas.cz\/?page_id=168"},"modified":"2026-04-27T13:49:30","modified_gmt":"2026-04-27T11:49:30","slug":"bezpecne-nakladani-s-daty","status":"publish","type":"page","link":"https:\/\/openscience.bc.cas.cz\/en\/fair-data\/bezpecne-nakladani-s-daty\/","title":{"rendered":"Secure Data Handling"},"content":{"rendered":"
\"\"<\/span>
\n
\n
\n
\n

Biology Centre CAS<\/span><\/mark><\/a><\/strong><\/strong><\/strong><\/strong><\/strong><\/p>\n\n\n\n

Secure Data Handling<\/h2>\n\n\n\n

Lost data is like lost time: you can never fully take it back!<\/p>\n\n\n\n

\n
More...<\/a><\/div>\n\n\n\n
Contact support<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/main>\n<\/div><\/main>\n\n\n\n
\n
\n
\n
\n

<\/h2>\n\n\n\n

Secure research data handling means a set of procedures and technical measures that protect data throughout the entire project life cycle \u2013 from its collection and processing to archiving or sharing. This includes appropriate selection of storage locations, regular backups, control of access rights, protection of personal and sensitive data, encryption of transmissions and devices, and the use of secure working practices within the team. The aim is to ensure the integrity, credibility and security of the entire research process, minimizing the risks of loss, damage, unauthorized access or leakage of data.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/main>\n\n\n\n

\n
\n
\n
\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n\n
\n

For scientists and research organizations, data management is essential not only from a legislative perspective (e.g. GDPR, ethical standards, contractual obligations), but also for maintaining the reputation and credibility of research. Errors in storing or sharing data can lead to the irreversible loss of unique results, violation of the rights of research participants or questioning of published conclusions. When planning research, it is therefore necessary to think about structuring data, labeling it, controlling access within the team, suitable formats for archiving and also how to handle the data after the project ends. In practice, it is therefore important to think about choosing a suitable storage location based on the sensitivity of the data.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/main>\n\n\n\n

\n
\n

Types of data storage and their uses<\/strong><\/h2>\n\n\n\n

<\/a><\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

Flash drives<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> mall, portable, inexpensive<\/p>\n\n\n\n

Advantages:<\/strong> portable; instant access without a network<\/p>\n\n\n\n

Disadvantages\/risks:<\/strong> easily lost or damaged; prone to data loss; security (often unencrypted)<\/p>\n\n\n\n

Recommendations:<\/strong> only used for short-term transfers or \"working copy\" backups. Never as the sole repository for main data; encrypt; have at least one copy.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

Portable drives (external HDD\/SSD)<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> higher capacities than flash drives, suitable for backups<\/p>\n\n\n\n

Advantages:<\/strong> portable, price\/volume of data<\/p>\n\n\n\n

Disadvantages:<\/strong> risk of physical damage; security<\/p>\n\n\n\n

Recommendations:<\/strong> use for off-site backups, keep one copy in another location; regularly test data integrity.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

Network Attached Storage (NAS)<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> dedicated device providing network storage (typically with RAID, user accounts)<\/p>\n\n\n\n

Advantages:<\/strong> flexible, possibility of redundant array (RAID), suitable for sharing in a team<\/p>\n\n\n\n

Disadvantages:<\/strong> administrator has to deal with updates, security; RAID is not a backup (user errors are propagated)<\/p>\n\n\n\n

Recommendations:<\/strong> combine NAS (first level) with off-site or cloud-backup. For internal large volumes of data, this is often ideal.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

Data repositories \/ data repositories (Zenodo, Dryard, ASEP, etc.)<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> designed for research data, supports persistent identifiers and metadata<\/p>\n\n\n\n

Advantages:<\/strong> allows for DOI assignment, meets FAIR and grant requirements; often provides long-term retention<\/p>\n\n\n\n

Disadvantages:<\/strong> may have storage size limits or format requirements; not always suitable for highly sensitive data without access restrictions<\/p>\n\n\n\n

Recommendations:<\/strong> Publish final data intended for sharing; for sensitive data, use repositories with access control or store only anonymized datasets + open metadata.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

Local disk
(in a computer)<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> basic storage for work<\/p>\n\n\n\n

Advantages:<\/strong> fast access, suitable for data analysis<\/p>\n\n\n\n

Disadvantages:<\/strong> risk of hardware failure, theft, loss; often lacks automatic backup<\/p>\n\n\n\n

Recommendations:<\/strong> do not keep a single copy there; regular backup to another physical medium or network storage; encryption for sensitive data.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

Network storage (institutional network drives, fileshares)<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> central server in the institution accessible via LAN\/VPN<\/p>\n\n\n\n

Advantages:<\/strong> central management, IT-managed backups, access rights options<\/p>\n\n\n\n

Disadvantages:<\/strong> dependence on institutional infrastructure and management; capacity limits; off-campus availability may require VPN<\/p>\n\n\n\n

Recommendations:<\/strong> suitable for internal data and drafts; verify SLA (availability), backup policy, and retention.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

Cloud storage
(Google Drive, OneDrive, etc.)<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> scalable, accessible via the Internet<\/p>\n\n\n\n

Advantages:<\/strong> good availability, automatic backups, integration with tools, easy sharing<\/p>\n\n\n\n

Disadvantages:<\/strong> legal issues (where the data is physically located), costs for large volumes, dependence on the supplier<\/p>\n\n\n\n

Recommendations:<\/strong> for public or internal data, the cloud is suitable; for sensitive data, check the terms of service, encryption (at-rest and in-transit) and data location (GDPR). For long-term archiving, other services are better.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n

National\/scientific services (e.g. CESNET)<\/h2>\n<\/div>\n\n\n\n

Characteristics:<\/strong> services intended for the scientific community (CESNET: VO Storage, ownCloud, FileSender<\/a>They offer capacity tailored to scientific needs.<\/p>\n\n\n\n

Advantages:<\/strong> available to BCs without additional fees; trustworthy in terms of long-term preservation and compliance<\/p>\n\n\n\n

Disadvantages:<\/strong> access limited to users of connected institutions<\/p>\n\n\n\n

Recommendations:<\/strong> for large volumes of scientific data and sharing within research teams, CESNET (or similar national services) in the Czech Republic is a very suitable choice; check the terms of service and limits.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

3-2-1 Backup: The Golden Rule for Protecting Your Data<\/strong><\/h2>\n\n\n\n

At the BC, data represent the most important outcome of years of research, laboratory experiments, and field data collection. Losing this data is not merely a technical issue; it jeopardizes entire projects, grant commitments, and publication efforts. The 3-2-1 strategy is an internationally recognized standard for ensuring maximum redundancy and resilience for your datasets.<\/p>\n\n\n\n

Data from biological experiments are often irreproducible or take a very long time to collect (seasonal collections, unique genetic sequences). The 3-2-1 rule forms the cornerstone of the\u00a0Data Management Plan<\/span><\/a><\/strong>, which is now standard practice for most grant providers.<\/p>\n\n\n\n

\n
\n
\n

3 copies<\/h2>\n\n\n\n

Minimum redundancy<\/strong><\/p>\n\n\n\n

Always keep at least three copies of your research data. The first is the original, primary, raw data you\u2019re working with. You keep this on your computer or lab instrument. The other two are independent backups. Statistically, this eliminates the risk of simultaneous write errors or media failures. If all three copies fail, you might go home. The world has probably come to an end\u2026<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

2 media<\/h2>\n\n\n\n

Storage diversification<\/strong><\/p>\n\n\n\n

The two backups mentioned in the first point must not be stored on the same type of storage medium. Let alone on a single device! Combine different storage methods and devices. For example, store one copy on an external SSD\/HDD and the other on network storage. This will help you avoid data loss due to a hardware failure or a specific system error associated with a particular type of storage medium.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

1 outside<\/h2>\n\n\n\n

Geographic separation<\/strong><\/p>\n\n\n\n

At least one copy must be stored at a different location than the rest of the copies. In the context of business continuity, this means using a remote cloud (e.g., CESNET) or at least a separate server node in a different building. Geographic separation is the only effective protection against natural disasters and other unforeseen events (fire, water main breaks) or cyberattacks.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n

How to Select Storage<\/strong><\/h2>\n\n\n\n
\"\"<\/figure>\n<\/div>\n\n\n\n

If you need help setting up research data backup, don't hesitate to contact your institute's IT support<\/span><\/a>. The guys have got it covered. If you need advice on the Data Management Plan, grant terms related to data storage and sharing, or uploading data to a repository, write to your institutional data steward<\/span><\/a>.<\/p>\n\n\n\n

<\/p>","protected":false},"excerpt":{"rendered":"

Jde o soubor postup\u016f a technick\u00fdch opat\u0159en\u00ed, kter\u00e1 chr\u00e1n\u00ed data v pr\u016fb\u011bhu cel\u00e9ho \u017eivotn\u00edho cyklu projektu \u2013 od jejich sb\u011bru a zpracov\u00e1n\u00ed a\u017e po archivaci \u010di sd\u00edlen\u00ed. Pat\u0159\u00ed sem vhodn\u00fd v\u00fdb\u011br ulo\u017ei\u0161\u0165, pravideln\u00e9 z\u00e1lohov\u00e1n\u00ed, kontrola p\u0159\u00edstupov\u00fdch pr\u00e1v, ochrana osobn\u00edch a citliv\u00fdch \u00fadaj\u016f, \u0161ifrov\u00e1n\u00ed p\u0159enos\u016f i za\u0159\u00edzen\u00ed a tak\u00e9 pou\u017e\u00edv\u00e1n\u00ed bezpe\u010dn\u00fdch pracovn\u00edch postup\u016f v t\u00fdmu. C\u00edlem je zajistit […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":139,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-168","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/pages\/168","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/comments?post=168"}],"version-history":[{"count":68,"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/pages\/168\/revisions"}],"predecessor-version":[{"id":1162,"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/pages\/168\/revisions\/1162"}],"up":[{"embeddable":true,"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/pages\/139"}],"wp:attachment":[{"href":"https:\/\/openscience.bc.cas.cz\/en\/wp-json\/wp\/v2\/media?parent=168"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}