System Transfers

The file transfers set up to provide verification that the file has been received, and received by the intended recipient. In addition, the data is transmitted using Strong Encryption. 


SFTP is recommended, GPG is additionally provided as an option, and uploaded files are automatically processed and generate a success or failure notification.


Use strong authentication to ensure that the integrity of the message is adhered to. Secure Hash Algorithms (currently SHA2 onwards or HMAC ) used where the systems permit.

Network Messages

Network devices that communicate with each other using network devices Simple Network Management Protocol (SNMP) use SNMP v3.0 and no earlier


Encrypted using strong encryption, especially where events relate to the security monitoring of systems, i.e. IDS, SIEM log information, and includes the storage of such events.


Block based cipher encryption should be used when application or hardware is configured to permit streaming. Where system or application limitations prevent the use of block based ciphers stream based ciphers should be used instead.


HTTP Tunnelling not used for streaming of data.


API control includes:

  • The authentication of users or service accounts.  
  • The authorisation of users or service accounts.
  • The encryption of static keys when sending over the TUI internal network.
  • Encryption of data using strong encryption.
  • Credentials and data passed between layers is to be encrypted using encryption

File Sharing

Movement of files between servers happens using rsync over ssh


FTP is not used for inter server communication

Database Links

JDBC and ODBC are not utilised to connect to our datastores.  All code changes are passed through automated testing and manual review prior to being accepted into the Feefo code repositories.

  • Users are authenticated prior to accessing restricted data.
  • User access is controlled by username/password combinations, API keys and short-lived access tokens.
  • User’s actions are recorded and audited for high-risk actions.
  • Compiled code is encrypted at rest


Files are transmitted in encrypted form using strong encryption.


Access to these files are restricted on a need to know basis with read only set as the default. Other levels of access must be by exception and subject to additional authorisation."


The printing of personal data isavoided. Where printing is required the systems that receive the print file do not print any documentation until the recipient has authenticated that they are the person that requested the print.

Telephone & Fax

IP (Internet Protocol) based telephony is encrypted using strong encryption.

IP (Internet Protocol) based telephony is located on a dedicated network segment and firewalled from data traffic.

Personal data is not left in voice messages.

Where personal data is stored or delivered into a recording system it is encrypted using strong encryption and subject to review in line with the Data Retention Standard.

Transmission of personal data over Fax is not permitted unless the authorised recipient has been verified and confirmed as physically awaiting receipt unless the Fax is in a secure area."

Physical Mail


  • Marked “confidential” and “to be opened by the addressee only” on the internal envelope. The enveloped should be sealed.
  • No personal data is to be visible on the external envelope.



  • Marked “confidential” and “to be opened by the addressee only”.
  • Envelope sealed.
  • No personal data is visible on the envelope.
  • Royal Mail is used.