Data Security, Storage, Access, Transfer and Destruction

For additional questions please contact Research Integrity Office at: researchintegrity@fredrimonta.com or 561-297-1383.

• It is advisable to export data from raw SQL database or input the data in analytical files in a manner that strips the immediately identifying variables from the SQL database or the paper files.

• Check that they do not contain names or identifiers.
• Utilize dedicated password protected, restricted-access space on shared network drives and conduct and save analytic work directly into these locations.
• The use of cloud-based servers to store and manipulate data is also a feasible secure option to manage data without permanent local storage.
• Contact your College IT representative to explore the options for Florida Atlantic available servers and storage options.
• The use of remote access software is an alternative solution.

• If a local copy of the data is required, follow recommendations in the sections below.
• Work within the secure network as much as possible, and when possible, upload your work to dedicated space on Florida Atlantic shared network drives.
• After uploading to Florida Atlantic network drives, remove local workspaces and copies of the data when no longer needed.

Password-protection of individual files/documents is usually offered by the manufacturer of the software, (i.e.: Microsoft). Users must control the security of their own documents.

In general, good practice is to have three copies in at least two locations (e.g. original + external/local backup + external/remote backup). Geographically distribute your local and remote copies to reduce risk of calamity at the same location (power outage, flood, fire, etc.).

To be sure that your backup system is working, periodically retrieve your data files and confirm that you can read them. You should make these checks when you initially set up the system and on a regular schedule thereafter. CDs or DVDs are not recommended because they are easily lost, decay rapidly and fail frequently.

Florida Atlantic has a policy in place ⁶ for backups to ensure that the institution has a safe and recent copy of data in case a system crashes or other disaster occurs. The system(s) run a backup script each night when there is little activity. A third-party cloud storage company maintains offsite backup data. All data is encrypted and stored safely.

Personal identifying information should be kept separate from the research data AND data should be stored in an encrypted format.

Sharing data

• File Formats for Long-Term Access: The file format in which you keep your data is a primary factor in the ability to use your data in the future. Plan for both hardware and software obsolescence.
• Don't Forget the Documentation: Document your research and data so others can interpret the information. Begin to document your data at the very beginning of your research project and continue throughout the project.
• Ownership and Privacy: Make sure that you have considered the implications of sharing data in terms of copyright, IP ownership, and subject confidentiality. The way to share your data must be planned and described in the original research protocol. Always work with your IT representative, to establish a realistic, up-to-date sharing plan.
• Refer to Florida Atlantic-Sponsor Research for need and terms of Data Use Agreements Guidance:
  ⁷ Click here to review guidance document.

An optimal option is to create/find a data repository. The decision should be based on the long-term security offered and the ease of discovery and access by colleagues in the field. There are two common types of repository to look for:

• Discipline specific: Accepts data in a particular field or of a particular type (e.g., GenBank accepts nucleotide sequence data).
• Institutional: Accepts data of any type produced within the institution that maintains it (e.g., the University of California's Merritt) Central Data Repository.