x

Landlord Security Access Policy

How our landlords limit access to your data

Landlords working with Purple Frog will establish specific requirements for protecting information and information systems against unauthorised access.

Landlords working with Purple Frog will effectively communicate the need for information and information system access control.

1. Purpose

Information security is the protection of information against accidental or malicious disclosure, modification or destruction. Information is an important, valuable asset of landlords which must be managed with care. All information has a value. However, not all this information has an equal value or requires the same level of protection.

Access controls are put in place to protect information by controlling who has the rights to use different information resources and by guarding against unauthorised use.

Procedures control how access to information is granted and how such access is changed.

This policy also mandates a standard for the creation of strong passwords, their protection and frequency of change.

2. Scope

This policy applies to landlords working with Purple Frog, contractual third parties and agents of the landlord with any form of access to the landlord’s information and information systems.

3. Definition

Access control rules and procedures are required to regulate who can access the landlord’s information resources or systems and the associated access privileges. This policy applies at all times and should be adhered to whenever accessing information in any format, and on any device.

4. Risks

On occasion business information may be disclosed or accessed prematurely, accidentally or unlawfully. Individuals or companies, without the correct authorisation and clearance may intentionally or accidentally gain unauthorised access to business information which may adversely affect day to day business. This policy is intended to mitigate that risk.

Noncompliance with this policy could have a significant effect on the efficient operation of the organisation and may result in a breach of data, financial loss and an inability to provide necessary services to our customers.

5. Passwords

5.1. Choosing Passwords

Passwords are the first line of defence for our IT systems and together with the user ID help to establish that people are who they claim to be.

A poorly chosen or misused password is a security risk and may impact upon the confidentiality, integrity or availability of our computers and systems.

5.1.1. Weak and strong passwords

A weak password is one which is easily discovered, or detected, by people who are not supposed to know it. Examples of weak passwords include words picked out of a dictionary, names of children and pets, car registration numbers and simple patterns of letters from a computer keyboard.

A strong password is a password that is designed in such a way that it is unlikely to be detected by people who are not supposed to know it, and difficult to work out even with the help of a computer.

To this end, the landlord’s policy is that everyone who falls into the scope of this policy must use strong passwords with a minimum standard of:

  • At least seven characters
  • Contain a mix of alpha and numeric, with at least one digit
  • More complex than a single word (such passwords are easier for hackers to crack)

5.1.2. Protecting Passwords

Landlords working with Purple Frog have the following guidelines for protecting passwords, must be adhered to at all times:

  • Never reveal your passwords to anyone
  • Never write your passwords down or store them where they are open to theft
  • Never store your passwords in a computer system without encryption/further protection
  • Do not use any part of your username within the password
  • Do not use the same password for systems inside and outside of work

5.1.3. Changing Passwords

If a landlord uses a database or data software to store personal data, all user-level passwords must be changed at a maximum of every 90 days, or whenever a system prompts you to change it. Default passwords must also be changed immediately.

Users must not reuse the same password within password changes.

5.2. System Administration Standards

The password administration process for individual systems is well-documented and available to designated individuals.

All IT systems will be configured to enforce the following:

  • Authentication of individual users, not groups of users - i.e. no generic accounts
  • Protection with regards to the retrieval of passwords and security details
  • System access monitoring and logging at a user level
  • Role management so that functions can be performed without sharing passwords
  • Password admin processes must be properly controlled, secure and auditable

6. Employee Access (where applicable)

6.1 User Access Management

Formal user access control procedures must be documented, implemented and kept up to date for each application and information system to ensure authorised user access and to prevent unauthorised access. They must cover all stages of the lifecycle of user access, from the initial registration of new users to the final de-registration of users who no longer require access. These must be agreed by the landlord, acting as data controller. Each user must be allocated access rights and permissions to computer systems and data that:

  • Are commensurate with the tasks they are expected to perform
  • Have a unique login that is not shared with or disclosed to any other user
  • Have an associated unique password that is requested at each new login

User access rights must be reviewed at regular intervals to ensure that the appropriate rights are still allocated. System administration accounts must only be provided to users that are required to perform system administration tasks.

6.2 User Registration

Where applicable, a request for access to the data controller’s computer systems must first be submitted to the landlord.

When an employee leaves the organisation, their access to computer systems and data must be suspended at the close of business on the employee’s last working day. It is the responsibility of the employer to request the suspension of the access rights via the data controller.

6.3 User Responsibilities

It is a user’s responsibility to prevent their user ID and password being used to gain unauthorised access to the organisations systems by:

  • Following the Password Policy Statements outlined above in Section 6
  • Ensuring that any PC they are using that is left unattended is locked or logged out
  • Leaving nothing on display that may contain access information such as login names and passwords

6.4 Network Access Control

The use of USBs and Remote Log In methods on non-organisation owned PCs connected to the organisation’s network can seriously compromise the security of the network. While users can access the system remotely, the normal operation of the network must not be interfered with. Specific approval must be obtained from the data controller before connecting any equipment to the  network.

6.5 User Authentication for External Connections

Where remote access to the landlord’s network is required, an application must be made before access is granted. Remote access to the network must be secured by two factor authentication consisting of a username and one other component.

6.6 Supplier’s Remote Access to the Organisations Network

Partner agencies or 3rd party suppliers must not be given details of how to access the organisation’s network without permission from the data controller. Any changes to suppliers’ connections must be immediately sent to the landlord so that access can be updated or ceased. All permissions and access methods must be controlled by the landlord, acting as data controller.

Partners or 3rd party suppliers must contact the landlord before connecting to the network and a log of activity must be maintained. Remote access software must be disabled when not in use.

6.7 Operating System Access Control

Access to operating systems is controlled by a secure login process. The access control defined in the User Access Management section (section 7) and the Password section (section 6) above must be applied. The login procedure must also be protected by:

  • Not displaying any previous login information e.g. username
  • The password characters being hidden by symbols
  • Displaying a general warning notice that only authorised users are allowed

All access to operating systems is via a unique login id that will be audited and can be traced back to each individual user. The login ID must not give any indication of the level of access that it provides to the system (e.g. administration rights).

System administrators must have individual administrator accounts that will be logged and audited. The administrator account must not be used by individuals for normal day to day activities.

6.8 Application and Information Access

Access within software applications must be restricted using the security features built into the individual product. The access must:

  • Be compliant with the User Access Management section (section 7) and the Password section (section 6) above
  • Be separated into clearly defined roles
  • Give the appropriate level of access required for the role of the user
  • Be unable to be overridden (with the admin settings removed or hidden from the user)
  • Be free from alteration by rights inherited from the operating system that could allow unauthorised higher levels of access
  • Be logged and auditable

7. Policy Compliance

If any user is found to have breached this policy, they may be subject to the landlord’s disciplinary procedure, where applicable. If a criminal offence is considered to have been committed further action may be taken to assist in the prosecution of the offender(s).

If you do not understand the implications of this policy or how it may apply to you, seek advice from the data controller.

8. Review and Revision

This policy will be reviewed as it is deemed appropriate, but no less frequently than every 12 months.

How do you feel about Purple Frog?