hosting the functions on separate servers would not be technically feasible or would cause unreasonable business disruption (e.g. High or Very High Risk Information is not being processed through these servers and/or.Ideally, web, application and database functions should be hosted on separate servers however, it is acceptable to host all of these functions on the same server in the following circumstances:.Questions about this standard may be referred to Architecture Requirements The Chief Information Officer has issued this standard under the authority of Policy SC14, Acceptable Use and Security of UBC Electronic Information and Systems.Servers that are not Internet-facing, such as intranet servers, should also follow this standard, wherever feasible. This standard focusses on Web Servers because these are primary targets for exploitation and therefore pose the highest risk to the University. This document defines minimum standards to be followed by University IT Support Staff for the security architecture, protected network protocols, hardening/patching and monitoring/logging of UBC’s Internet-facing systems and services to ensure they are adequately protected.Without adequate security, these systems and services provide an avenue for malicious activity such as theft of UBC Electronic Information or the denial of service to UBC resources. visible or accessible from the Internet) are prime targets for exploitation. UBC Systems and services that are Internet-facing (i.e.Print-friendly version Internet-facing Systems and Services Introduction
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |