Initiative-6 - HTTP 2 HTTPS - Risk Log

	Date Raised	Risk Description	Likelihood of the risk occurring	Impact if the risk occurring	Owner	Mitigation Action
1	11/12/2019	During Conversion As a website is converted, we will discover issues that will require additional resources to complete the conversion. For example sasd - Loss of identity between workstation and sql server prevents custom security. Hardcoded HTTP addresses require changes.	Almost a certainty since this has been proven to be the case.	Additional IT labor, of various sort. Possible outside vendor support for vended apps.	Mark Wachdorf
2	11/13/2019	As a website is converted, it will have a new address. Any processes that connect to this website will need to be adjusted. People who have bookmarks will need to update those bookmarks.	This will occur on many websites.	Programs that have links will have problems. People who have broken bookmarks will contact helpdesk. The fix for help desk will be to direct person to the revised location.	Mark Wachdorf	When moving a website to production, send a change announcement. Both before the update, and after the conversion to give users the new web address.
3	11/21/2019	If a failure based on HTTPS occurs then system will be down until that is corrected.		Downtime	Mark Wachdorf	A plan is needed on high impact applications to accommodate https downtime.
4	11/21/2019	If the solution is not known to the vendor, then they may trouble supporting us.				We need vendor buy in on the solution we choose, or we accept the risk.
5	1/7/2020	We found some F5 support documents, but which F5 server/version ect do we have? Technical articles might be referencing the wrong products		Delays, and possible functionality problems.