Skip navigation

Standard: Infrastructure security classification

Purpose

To establish the infrastructure security classification standards and guidelines for University information infrastructure, information systems and assets.

Definitions

Definitions of additional terms used in this document are provided in the overarching policy, Information Technology security.

Encryption: The University considers an appropriate level of encryption to be the standards specified in the Australian Government Information Security Manual.

Information asset: any set of information or part of the information infrastructure critical to the functioning of the University, with a designated system owner.

Standard

  1. The University is committed to providing a secure yet open information infrastructure that protects the integrity of its information assets (data and other information), and confidentiality of information without compromising its availability. Systems hosting the University's information or data sets are required to be appropriately classified and secured.
  2. It is recommended that University data is backed up and primarily stored on University provided storage infrastructure. Data owners that choose to store University data elsewhere are responsible for maintaining appropriate backups.
  3. The University recognises three broad categories of data held within its systems:
  1. public data
  2. sensitive data (formerly referred to as internal data)
  3. highly sensitive data (formerly referred to as confidential data)
  1. Responsibility for the classification of data rests with the system owner.
  2. Data users must comply with all relevant non-disclosure agreements, copyright restrictions, confidentiality agreements and ANU disclosure rules.
  3. All systems, regardless of their classification, must include the following measures:
  1. access control
  2. asset management
  3. communication and operations management.

Public data

  1. Public data is defined as that which would have an insignificant impact on the University if breached.
  2. Public data is available to all members of the University community and all individuals and entities outside ANU. Disclosure of public data is generally unrestricted, providing the disclosure does not violate non-disclosure agreements.
  3. Encryption is permitted but not required for the transmission of public data.
  4. Examples of public data include:
  1. publicly posted press releases
  2. published research data
  3. publicly available marketing materials
  4. publicly posted job announcements.

Sensitive data

  1. Sensitive data is defined as that which would have a low or medium impact on the University if breached.
  2. Sensitive data is restricted on a need to know basis, and may only be accessed, transmitted, modified, or stored for a legitimate academic, research or business purpose.
  3. Encryption is recommended but not required for the transmission of sensitive data.
  4. Sensitive data is:
  1. protected to prevent loss, theft, malicious activity, unauthorised access and/or unauthorised disclosure
  2. protected by confidentiality agreements before access is permitted
  3. the default classification for data if a classification level has not been explicitly defined.
  1. Hard copies of sensitive data must be stored in a closed container (filing cabinet, closed office, secure area etc.). Sensitive data in electronic format must be stored on a system that requires user authentication.
  2. Examples of sensitive data may include:
  1. employment data
  2. business partner information (in the absence of more restrictive arrangements)
  3. internal directories and organisational charts
  4. planning documents.

Highly sensitive data

  1. Highly sensitive data is defined as that which would have a high impact on the University if breached.
  2. Highly sensitive data is restricted on a need to know basis, and may only be accessed, transmitted, modified, or stored for legitimate academic, research or business purposes.
  3. Disclosure of highly sensitive data to parties outside the University must be authorised by executive management, or covered by a binding confidentiality agreement.
  4. Highly sensitive data is protected by statutes, regulations, policies and contractual obligations.
  5. When storing and transmitting highly sensitive data, the following measures must be undertaken:
  1. hard copies must be stored in a locked drawer, cabinet, room or area where access is controlled or has sufficient access control measures
  2. electronic copies must be stored on a system that requires ANU-based user authentication
  3. in the event that it must be recorded to an external data storage device, such as a flash drive, all data must be encrypted
  4. electronic copies must be encrypted when transferring to an external entity
  5. must not be posted to a public website
  6. must not be sent to an external email account
  7. must not be stored on non ANU-managed storage.
  1. The Information Technology Services (ITS) Cyber and Digital Security Team must be notified if data classified as highly sensitive is lost, disclosed to an unauthorised party, is suspected of being lost or disclosed, or if any unauthorised use of ANU information systems has taken place, or is suspected of taking place.
  2. Examples of highly sensitive data include:
  1. medical records and clinical trial data
  2. safety data
  3. personnel and/or payroll records
  4. student records
  5. data identified under the Australian government security classification system as confidential (refer to www.protectivesecurity.gov.au)
  6. data belonging to a third party that may contain personal or identifiable information
  7. contracts
  8. patent information.

System owner responsibilities

  1. Physical and logical access to systems may be granted by the system owner if access is appropriately controlled, and formal procedures are implemented to permit access to the system.
  2. The allocation and use of system privileges must be restricted and controlled.
  3. A formal review of user privileges must be conducted on a regular basis to ensure that they remain appropriate. Accounts that are no longer required or appropriate must be closed or disabled.
  4. When users leave the University, or change roles, access rights on systems must be reviewed and adjusted appropriately.
  5. System resources must be monitored, tuned, and projections made for future capacity requirements to ensure the required system performance.
  6. For each new and ongoing activity, capacity requirements must be identified. System tuning and monitoring must be applied to ensure and improve the availability and efficiency of systems. Detective controls must be put in place to indicate problems in due time, and projections of future capacity requirements take account of new business and system requirements, and current and projected trends in information processing capabilities.
  7. Operating procedures must be documented, maintained and made available to all users. Sensitive documentation must be protected, and access restricted on a need-to-know basis.

User responsibilities

  1. The allocation, management, and use of passwords and other forms of authentication must be controlled and in accordance with the Passwords procedure.
  2. All remote access connections made to the information infrastructure must be made through approved University secure connections.
  3. Portable computing devices owned by the University, or that contain non-public University information, must be physically secured when unattended by either; locked drawer, cabinet or room, or with a cable-lock system.

Information

Printable version (PDF)
Title Infrastructure security classification
Document Type Standard
Document Number ANUP_000753
Version 8
Purpose To establish the infrastructure security classification standards and guidelines for University information infrastructure, information systems and assets.
Audience Staff, Students, Alumni, Affiliates
Category Administrative
Topic/ SubTopic Information Technology - Security
 
Effective Date 1 Nov 2017
Review Date 1 Nov 2018
 
Responsible Officer Director, Information Technology Services
Approved By: Vice-Chancellor
Contact Area Information Technology Services
Authority Information Infrastructure and Services Statute 2012
Information Infrastructure and Services Rule 2015
AS ISO/IEC 27002:2015
Australian National University Act 1991
Australian Government Protective Security Policy Framework
Public Governance, Performance and Accountability Act 2013
Public Governance, Performance and Accountability Rule 2014
Australian Government Department of Finance and Deregulation Finance Circular No. 2009/08
Crimes Act 1914 (Cth)
Privacy Act 1998
Telecommunications Act 1997
Telecommunications Regulations 2001
1504249909