Research institutes produce some of the world’s most valuable data: research of human beings, animal/plant life, society’s and cultures, and so much more. This data being collected is integral to future advancements in our society, yet we must ask ourselves how it’s being protected today. For the sake of confidentiality and privacy, how can we keep critical research data protected?
Research institutes are responsible for conducting, storing, analyzing, using and ultimately sharing research data. Before research begins, there should be data protection protocols in place to prevent data loss, manipulation or theft. Read on to discover how research institutes can actively prevent data infringement and protect their data with Nextcloud as their platform.
How can research institutes’ data be protected with Nextcloud?
1. Access controls
One of the best ways to protect research data is to limit access to it. Only a handful of people will need to open the research folders and sysadmins can control this process down to a tee.
In Nextcloud Files, advanced permissions that limit and/or restrict access are state-of-the-art and trusted by our customers and community.
Just a few examples of advanced permissions:
Setting permissions on a shared file to: read, create, edit, and/or upload.
Watermarking confidential documents to make it harder to steal data.
Enabling a password protection or expiration date on a public file or folder.
Blocking downloads so the user can view and even edit the shared file(s), but not download them.
Watch the webinar recording!
Learn more about how your organization can collaborate on research data with Nextcloud
On a daily basis, external contacts send files and documents by email or through other channels which need to be scanned for threats like viruses. The Nextcloud Antivirus app (AV) performs automatic virus scans. Whenever a file is uploaded, it first gets handed over to the AV app.
Nextcloud provides optimal security for research data and communication through encryption and hardening.
We offer three types of encryption:
Encrypted data transfer with industry-standard TLS (Transport Layer Security)
Server side encryption
Enables researchers to store files locally and securely with encryption keys and ciphers
End-to-End encryption
E2EE file sharing: Enables researchers to share confidential files to other users and can be synced between devices.
E2EE file drop: Allows researchers to receive files from external users through sharing a secure shared link. The external user only has the option to upload a file in the end-to-end encrypted folder.
4. Intrusion detection software
With machine learning based suspicious login detection, research institutes can increase security and productivity even beyond our brute-force protection and 2-factor authentification.
Suspicious Login Detection uses a locally trained neural network to detect attempts to login by malicious actors.
Nextcloud Hub 9 te permite estar conectado. Descubre nuevas funciones de federación, automatización del flujo de trabajo, una gran revisión del diseño y mucho más en tu plataforma de colaboración de código abierto favorita.
Maintenance updates 28.0.12, 29.0.9 and 30.0.2 for Nextcloud Hub 7, 8 and 9 respectively are here! Read an update summary and access full changelog on the website.
In this article, we explain how federation works and what federation tools you can already use in Nextcloud, and discover how it can help businesses and governments achieve digital sovereignty.
Guardamos algunas cookies para contar los visitantes y facilitar el uso del sitio. Esto no sale de nuestro servidor y no es para rastrearte personalmente. Consulta nuestra política de privacidad para obtener más información. Personalización
Las cookies estadísticas recopilan información de forma anónima y nos ayudan a comprender cómo utilizan nuestro sitio web nuestros visitantes. Utilizamos Matomo alojado en la nube.
Matomo
_pk_ses*: Cuenta la primera visita del usuario
_pk_id*: Ayuda a no contar dos veces las visitas.
mtm_cookie_consent: Recuerda que el usuario ha dado su consentimiento para almacenar y utilizar cookies.
_pk_ses*: 30 minutos
_pk_id*: 28 días
mtm_cookie_consent: 30 días