No. Issue Further details Refer to 20. Jurisdiction Which country or jurisdiction is the Vendor vendor based in. 21. Which jurisdiction will the data reside? Vendor 22. Site security Does the vendor have a current Vendor independently compiled security audit of their site? 23. How often are security audits conducted Vendor and by whom? 24. Levels of Service Does the vendor provide a Service Level Vendor Agreement that sets targets for the services it offers? 25. Is there a documented and enforceable Vendor means of complaints resolution? 26. How does the vendor charge for its Vendor services? E.g. annual charge, numbers of students etc. 27. If the service level needs to be scaled up System sponsor or down how is this to be accommodated in the cost of the service? 28. Has the College secured future price System sponsor protection for this service? 29. Continuity of service Does the vendor have adequate Vendor documented arrangements for dealing with computer disasters and ensuring a continuity of service to College? 30. What would be the impact to College if System sponsor the service was unavailable? 31. Compatibility List any operating systems or versions Vendor that the vendor product cannot work on. 32. List any web browsers or versions that the vendor’s product cannot work on. A.6 Data issues This section deals with College data and the implications of its use. System sponsors will need to consider if the cloud solution justifies the risk of processing data offsite and the possible costs security audits. For sensitive data a College hosted system may offer cost savings in the long term. No. Issue Further details to 33. Data ownership and Will the system need data from core Data owner(s) safety College systems such as Student Administration, Personnel or Research Support Systems? The permission of the relevant College data owner will be needed to use data of this type. 34. Will the vendor allow other organizations Vendor access to the data stored on the cloud system?
No. Issue Further details Refer to 20. Jurisdiction Which country or jurisdiction is the vendor based in. Vendor 21. Which jurisdiction will the data reside? Vendor 22. Site security Does the vendor have a current independently compiled security audit of their site? Vendor 23. How often are security audits conducted and by whom? Vendor 24. Levels of Service Does the vendor provide a Service Level Agreement that sets targets for the services it offers? Vendor 25. Is there a documented and enforceable means of complaints resolution? Vendor 26. How does the vendor charge for its services? E.g. annual charge, numbers of students etc. Vendor 27. If the service level needs to be scaled up or down how is this to be accommodated in the cost of the service? System sponsor 28. Has the College secured future price protection for this service? System sponsor 29. Continuity of service Does the vendor have adequate documented arrangements for dealing with computer disasters and ensuring a continuity of service to College? Vendor 30. What would be the impact to College if the service was unavailable? System sponsor 31. Compatibility List any operating systems or versions that the vendor product cannot work on. Vendor 32. List any web browsers or versions that the vendor’s product cannot work on. A.6 Data issues This section deals with College data and the implications of its use. System sponsors will need to consider if the cloud solution justifies the risk of processing data offsite and the possible costs security audits. For sensitive data a College hosted system may offer cost savings in the long term. No. Issue Further details to 33. Data ownership and safety Will the system need data from core College systems such as Student Administration, Personnel or Research Support Systems? The permission of the relevant College data owner will be needed to use data of this type. Data owner(s) 34. Will the vendor allow other organizations access to the data stored on the cloud system? Vendor
Cloud%20Policy%202014%20Appendix%20A.docx