Data security model

Overview

CoGe's data security model relies on users. The security model relies on users. Users may have access to restricted data that they deposit into CoGe or have shared with them by other users. Primary restricted data includes genomes (DNA sequence data and structural annotations) and experiments (e.g., transcriptomes, SNPs).

Data Specifics

Primary Sequence and Experiment Data

All primary sequence data and experimental data (e.g., transcriptomes/SNPs) are stored in non-web accessible directories. The service responsible for retrieving sequence data requires authentication for each transaction on privileged/restricted access data. In addition, all data is stored without identifying information as to the organism from which they are derived.

Derivative Sequence Data

These data include fasta sequences derived from the primary sequence data (e.g., CDS sequences), results from whole genome comparative analyses, processed experiments, etc. These data are stored in non-web accessible directories. The service responsible for retrieving sequence data requires authentication for each transaction on privileged/restricted access data.

Backups

All primary sequence data are backed-up daily. All experiments are backed-up daily. All metadata stored in CoGe's main relational database are backed up daily. The backup process utilizes irsync (from iRODS). Backups are kept daily for a week, weekly for a month, and monthly for 6 months. The primary CoGe server's hard-drives are RAID6. Backups are kept in iRODS and are multiply redundant (multiple servers replicating data among separate data centers in different US states).

User Accounts

CoGe does not manage user account information. This is a service provided by iPlant which is used for user management and authentication. CoGe keeps a minimal amount of information about each user including real name, user name, and email address. If you would like your user account removed from CoGe, please contact us.