Information security policy

Updated on 1 July 2025

Definitions

The following definitions are used in this policy:

Information Security Management System means the Iress information security management system, as more particularly described in paragraph 1 of this policy.

Input Data has the meaning set out in the Terms and Conditions for the Supply of Software and Services. 

Penetration Testing has the meaning set out in paragraph 2 of this policy.

Penetration Testing Attestation has the meaning set out in paragraph 2 of this policy.

Security Control Weakness means the identification by Iress of a vulnerability within its Information Security Management System that has (or is likely to have) a materially adverse impact on the Iress Services. 

Security Incident: means the unauthorised access, disclosure loss of, or alteration to, the Input Data caused by a Security Control Weakness.

Information Security

1. Iress shall operate an Information Security Management System that is aligned with the international security standard ISO/IEC 27001:2022, or equivalent international standard. The Information Security Management System shall encompass the following control areas:

Organisational Controls

(a) Policies for Information Security

(b) Information Security Roles & Responsibilities

(c) Segregation of duties

(d) Management responsibilities

(e) Contact with authorities

(f) Contact with special interest groups

(g) Threat intelligence

(h) Information security in project management

(i) Inventory of information and other associated assets

(j) Acceptable use of information and other associated assets

(k) Return of assets

(l) Classification of Information

(m) Labelling of Information

(n) Information Transfer

(o) Access Control

(p) Identity management

(q) Authentication information

(r) Access Rights

(s) Information security in supplier relationships

(t) Addressing information security within supplier agreements

(u) Managing information security in the information and communication technology (ICT) supply chain

(v) Monitoring, review and change management of supplier services

(w) Information security for use of cloud services

(x) Information security incident management planning and preparation

(y) Assessment and decision on information security events

(z) Response to information security incidents

(aa) Learning from information security incidents

(bb) Collection of Evidence

(cc) Information security during disruption

(dd) ICT readiness for business continuity

(ee) Legal, statutory, regulatory & contractual requirements

(ff) Intellectual property rights

(gg) Protection of records

(hh) Privacy & protection of personal identifiable information

(ii) Independent review of information security

(jj) Compliance with policies, rules & standards for information security

(kk) Documented operating procedures

People Controls

(a) Screening

(b) Terms & Conditions of Employment

(c) Information security, awareness, education & training

(d) Disciplinary process

(e) Responsibilities after termination or change of employment

(f) Confidentiality or non-disclosure agreements

(g) Remote working

(h) Information security event reporting

Physical Controls

(a) Physical security parameters

(b) Physical entry Delivery and loading areas

(c) Securing offices, rooms and facilities

(d) Physical security monitoring

(e) Protecting against external and environmental threats

(f) Working in secure areas

(g) Clear desk and clear screen

(h) Equipment siting and protection

(i) Security of equipment and assets off-premises

(j) Storage media Removal of assets

(k) Supporting utilities

(l) Cabling security

(m) Equipment maintenance

(n) Secure disposal or reuse of equipment

Technological Controls

(a) User endpoint devices

(b) Privileged access rights

(c) Information access restriction 

(d) Access to source code

(e) Secure authentication

(f) Capacity management

(g) Protection against malware

(h) Management of technical vulnerabilities

(i) Configuration management

(j) Information deletion

(k) Data masking

(l) Data leakage prevention

(m) Information backup 

(n) Redundancy of information processing facilities

(o) Logging 

(p) Monitoring activities

(q) Clock synchronisation

(r) Use of privileged utility programs

(s) Installation of software on operational systems

(t) Network security

(u) Security of network services

(v) Segregation of networks

(w) Web filtering

(x) Use of cryptography

(y) Secure development lifecycle

(z) Application security requirements

(aa) Secure system architecture and engineering principles

(bb) Secure coding

(cc) Security testing in development and acceptance

(dd) Outsourced development

(ee) Separation of development, test and production environments

(ff) Change management

(gg) Test information

(hh) Protection of information systems during audit testing

2 Security Testing

Iress shall, on an annual basis, undertake penetration testing of the Software which forms part of the Iress Services provided to the Customer (“Penetration Testing”). Iress shall produce a letter of attestation citing any material vulnerabilities identified during the Penetration Testing process (“Penetration Testing Attestation”). Upon written request, Iress shall make the latest Penetrating Testing Attestation available to the Customer.

3 Notification

a) Iress shall, as soon as possible (and where reasonably practicable within 72 hours after becoming aware) notify the Customer of: 

(i) a Security Incident; and

(ii) a Security Control Weakness 

and shall provide all relevant information within its possession. 

b) Iress shall remedy any Security Control Weakness as soon as reasonably practicable, and will provide the Customer with timely updates until the Security Control Weakness is remedied.

Version control