Keeping customer and user data secure should be at the top of every library and vendor, and researcher’s list. As a version of HTTP, the primary vehicle which sends data from a web browser to a website, Hypertext transfer protocol secure (HTTPS) keeps data secure. When users upload sensitive information onto a website (credit card data, passwords, etc.), HTTPS keeps that data secure, using an encryption protocol. In a world where security issues exist, users expect products to adhere to modern security standards and for their research activity to remain secure.
EBSCO has been in the business for a long time, working hard to support HTTPS in our interfaces, old and new. Available as an option for years, HTTPS ensures that the data is encrypted between the user's browser and the servers for search terms sent to EBSCO is supported. This ensures all data is encrypted between the user and EBSCO, including credentials passed through authentication.
Beginning on July 19th, we’re encouraging our customers to update their interfaces to automatically redirect to HTTPS, to provide an optimal, safe research experience and meet privacy standards. This applies to EBSCO’s legacy products and services, with many of our authentication and newer interfaces already enforcing HTTPS.
We’re partnering with different proxy and authentication vendors to ensure customers are set up for success with this new change, including OCLC and RemoteXS, continuing support with our other authentication methods. We’re also working to prepare common API integrations and partners, including Stacks, SirsiDynix and Innovative Interfaces.
Keeping secure with enabled HTTPS is crucial to maintain data confidentiality. Learn more about how EBSCO helps keeps users secure with the FAQ on EBSCO Connect.
