CTS R16 – Security

The technical infrastructure of the repository provides for protection of the facility and its data, products, services, and users

The technical infrastructure provides by construction a certain level of protection against the risks of data loss or service interruption due to hardware failures. This protection is guaranteed through redundant systems and data and server backups. In addition, SEDOO constantly monitors its hardware, network flows and services uptime through Nagios.
Depending on project requirements, SEDOO can draw up a risk management table with risks likelihood, severity and mitigation strategies, based on the analysis described in its Data Management Plan.
As explained in the technical infrastructure, the SEDOO service level on a “best efforts” basis also applies to security level. In the case of outage, most of SEDOO staff is trained in basic system administration of the different services. One half-time equivalent is dedicated to hardware and network administration and security. The configuration of the IT infrastructure on two geographical distant sites allows the implementation of a continuity or recovery plan for the most critical services, thus guaranteeing an availability of data access services higher than 99%.


According to the criticality of the datasets, several levels of backup/archiving can be implemented:

  • Daily replication to dedicated disk storage systems for data requiring quick restoration;
  • Daily replication to disk storage systems on two sites for the most critical data for which SEDOO provides primary storage;
  • The security of Information System (IS) is ensured at different levels:
  • At the repository level: the IS CNRS referent validates the installation of SEDOO systems against security alerts issued by the national CERT (listing the flaws identified in the software or risks of attacks). SEDOO servers that are open to the outside world for data distribution have read-only access to the storage spaces hosting the data. If the server is hacked, the data cannot be deleted or modified.
  • At the IT department level: network firewalls (iptables, firewalld) or application firewalls (modsecurity, fail2ban) are used to filter network ports open to the outside world as well as to monitor network flows, with the ability to detect and block attacks.
  • At the national level: RENATER monitors the network flows and is able to quickly stop attacks and isolate the potential corrupted systems.
    Finally, access to the servers on the internal network is restricted by the firewall. Only IT administrators are allowed to access server configuration: data users can only access data-related services. Similarly, as described in R2 and R4, SSH access to data requiring a restrictive embargo is limited to Linux user groups or Access Control Lists (ACLs). Access to private data through other protocols (HTTPS, FTP, GridFTP) requires authentication via Lightweight Directory Access Protocol (LDAP). Authentication and verification of identifiers are systematically ensured by the LDAP or the IdP: no password is recorded in the data distribution application. Data access permissions are managed at the access application level using directory-level ACLs.

Links:

  • Technical infrastructure documentation

Rechercher