Overview
Background
The October 2017 update of Google Chrome (release 62) will change treatment of websites served over HTTP. Where there is a text input field on a webpage, the page must be served over HTTPS. A failure to do so could result in a ‘Not secure’ warning in the browser bar.
Google indicated in late April that this change was in relation to personal data but have recently extended it to any text input on a website, including website search. Equally, the Chrome browser in ‘Incognito’ mode will flag all HTTP sites as ‘not secure’.
Chrome is the world's most popular browser and currently Chrome accounts for 47% of browser usage of the University website with more than 80% on the latest version
Generally the popular uptake of a new release is 2-6 weeks post release. and post that will tend to become the def facto version.
Scope
Until now the website has accepted HTTP input fields and the integrity has been maintained within the current system. The scope of this project is to ensure that the product remains compliant with the changes that Google is making to the Chrome browser .
The project also intends to protect the reputation of the university in that users will not question whether the site is secure, something that could happen should users spot the not secure comment in their browser bar
Objectives
The objective of this project is to ensure that users who utilise Chrome as their browser will not experience a 'not secure' flag in their browser bar. UWS is not currently HTTPS but this project will implement SSL across www.ed.ac.uk to ensure full compliance.
A viable communications strategy to be produced.
Deliverables
NR |
Objectives / Deliverables |
Success Criteria |
Priority |
|
|
|
|
O1 |
To ensure that those who utilise Chrome as their browser do not experience a not secure flag |
No not secure flags |
Must |
D1 |
Present options for solution to business |
Identify benefits, risks and costs |
Must |
|
|
|
|
O2 |
Communications strategy |
|
|
D2 |
Delivery of a communications plan to business |
Business informed |
Must |
|
|
|
|
O3 |
No changes to workflow or loss of service |
Business notices no change |
Must |
D3 |
Delivery of agreed recommendation |
Testing proves that desired solution is working and fault free |
Must |
|
|
|
|
Project Milestones
Target Date![]() |
Previous Date | Title | Stage | Complete |
---|---|---|---|---|
18-Sep-2017 | No date available | Planning Review | Plan | Yes |
29-Sep-2017 | No date available | Build Review | Build | Yes |
03-Oct-2017 | No date available | Acceptance Review | Accept | Yes |
12-Oct-2017 | No date available | Delivery | Deliver | Yes |
02-Nov-2017 | 16-Oct-2017 | Deployment Review | Deliver | Yes |
16-Nov-2017 | 27-Oct-2017 | Closure review | Close | Yes |