This page consists of common security related questions pertaining to the DSpaceDirect hosted service. If you have additional questions not answered below, please contact email@example.com
DSpaceDirect provides the following security-focused monitoring:
Amazon Web Services (AWS) is the data center for DSpaceDirect. AWS provides very detailed documentation on their security compliance:
The data center we use for DSpaceDirect is AWS (Amazon Web Services). It is SOC certified. See: https://aws.amazon.com/compliance/soc-faqs/
DuraSpace / DSpaceDirect does not have any independent ISO certifications. However, AWS (Amazon Web Services), which provides our data center, is ISO 27001 certified. See: https://aws.amazon.com/compliance/iso-27001-faqs/
Please be aware that configuring/managing authorization plugins often requires extra support and/or coordination with local staff at your institution.
No. DSpaceDirect is intentional about not putting any barriers in place for access, preservation or reuse of data. You are welcome to encrypt data yourselves before putting it into storage, however DSpaceDirect will then only share the encrypted data with users. Simply put, whatever you upload into DSpaceDirect is what is then shared (there is no built in facility to encrypt or decrypt data dynamically).
Yes, all calls to DSpaceDirect are encrypted using Transport Layer Security protocols (HTTPS). We require HTTPS for all sites, and do not allow site data to be sent via plain HTTP. All sites also enable HSTS (HTTP Strict Transfer Security) to tell all web browsers to only use HTTPS.
Note, however, there is one exception to this rule. As OAI-PMH requires HTTP, we do allow HTTP access via the OAI-PMH interface only. That said, OAI-PMH only allows access to publicly available metadata, and does not provide any means for file access, authentication, etc.