MURDOCH     INDEX     SEARCH     PEOPLE  
Policies Index >>  Facilities & Services >>  Information Technology >> 

MurdochNet Policy

Section 1: PREAMBLE
Section 1.1: Purpose
Section 1.2: Scope
Section 1.3: Field of Application
Section 1.4: Policy Vocabulary
Section 1.5: Key Terms
Section 2: INTRODUCTION
Section 2.1: Goals
Section 2.2: Boundary of MurdochNet
Section 2.3: Environment of MurdochNet
Section 3: CODE OF CONDUCT
Section 3.1: Servers
Section 3.2: Content
Section 3.3: Links
Section 3.4: Misconduct
Section 4: SERVER MANAGEMENT
Section 4.1: Registration of Web Servers
Section 4.2: Murdoch Sub-domains
Section 4.3: Alternate Domain Names
Section 4.4: Naming Conventions for Web Servers
Section 4.5: Availability of Web Servers
Section 4.6: Security of Web Servers
Section 4.7: Backup (Hardware, Software, Data) of Web Servers
Section 4.8: Web Server Software
Section 4.9: Responsibility for Web Servers
Section 5: CONTENT MANAGEMENT
Section 5.1: Content Categories
Section 5.2: Content Management Procedures & Practices
Section 5.3: Standards & Guidelines for Content Preparation
Section 5.4: Murdoch Conventions for Content Preparation
Section 5.5: Murdoch Guidelines for Content Preparation
Section 5.6: Applications & Tools
Section 5.7: Responsibility for Content
Section 6: LINK MANAGEMENT
Section 6.1: Permissible Links
Section 6.2: Link Validation & Checking
Section 6.3: Link Revision & Relocation
Section 6.4: Responsibility for Registered Links
Section 7: Glossary of MurdochNet Terminology
: SCHEDULES
Schedule 1: Forms
Schedule 2: Contracts
Schedule 3: Guidelines
Schedule 4: Regulations
Schedule 5: Disclaimers
Schedule 6: Roles & Responsibilities

Section 5 CONTENT MANAGEMENT

Section 5.4 Murdoch Conventions for Content Preparation

Section 5.4.3 Security Convention

Security in the context of Content preparation refers to ensuring that Content is secure from interference whilst being transmitted between Server and Web browser.

The Murdoch Security Convention to be practiced in the preparation of Content includes:

  • Determining the intended audience prior to hosting Content on a Server
  • Confirming that the Server to be used to host or provide access to Content can offer the level of security required.

In complying with the Code of Conduct Section 3.1.3 Appropriate Access to Content for End-Users, a Content Custodian, or in their absence a Web Liaison Officer, or a Content Provider, shall determine the intended audience for Content. If the Content is of a personal, sensitive, or confidential nature, or involves a financial transaction, they shall

  • liaise with a Web Administrator to ensure that the Content is either hosted on, or accessed by a Secure Server (SSL)
  • advise end-users that data encryption is used, and
  • advise end-users of any known Web browser version requirements to ensure that they can successfully interact with a Secure Server to retrieve the information or service offered.

As search engines may index restricted Content and potentially display details in an index entry that are not intended to be viewed beyond the intended audience, it is recommended that Content Providers seek advice re the use of a Secure Server for hosting Content of a sensitive or confidential nature. If there is any uncertainty as to whether Content that has restricted access will still be indexed via external search engines, then the Content should be accessed via an intranet solution.