QC v24.02 Release Notes v1.0

Arqit QuantumCloud™

v24.02 Release Notes

© Arqit Limited

This document contains confidential and proprietary information, the copyright of which belongs to Arqit Limited and is intended only for the addressee to whom this copy has been supplied. The recipient will neither copy, distribute or otherwise use the information contained in this document for any purpose other than that for which it has been made available, nor permit anyone else to do the same without prior written authorisation from Arqit Limited. The recipient will be held liable for any wrongful disclosure or use of any information contained in this document by them, their officers or employees, or anyone else to whom they make the information available.

What’s new

Bilocation key controls

System administrators can control the length of time bilocation and p2p keys are valid for within their tenant.

The feature is controlled by a policy type: ‘Key Management Policy’. After the period set in the policy, devices will need to re-negotiate a new key directly with the other device (for p2p keys), or via QuantumCloud™ (for bilocation keys).

The time can be set across the estate by navigating to the ‘Policies’ page and selecting the edit button for the ‘Default Key Management Policy’. Users can then type a value and choose the relevant units (minimum of 30 seconds, maximum of 50 years).

More granular policies can be applied to OUs or devices by copying the ‘Default Key Management Policy’ instance, editing the values in each copy, then applying them as required.

It should be noted that the settings applied in each policy instance will be made available to devices using apps and services controlled by the policy, implementation (how the values are used within the app) remains the responsibility of the app developer (see Device policies below).

Audit export API

System administrators and security managers can pull audit logs from QuantumCloud™ via the Audit export API.

To access the API, users will need a client id and secret, which can be obtained by raising a service desk request (support@arqit.uk).

Further documentation, including information about the location of the API, how to use it and a list of audit messages that customers can expect to find, is available in the accompanying document.

Device policies

Settings that govern behaviour by (or local to) an endpoint/device can be set centrally in QuantumCloud™ and promulgated, to be consumed by devices in the wider estate.

This feature can be used to set or change e.g. logging levels, peering mode, port used, etc.. (For further examples of the settings which can be consumed, please see all policies with Scope: ‘Device’ in the ‘Policies’ page of the administration console.)

For more information on integrating this feature with apps and services, see the ‘Device policies guide’ section of the QuantumCloud™ Developer guide documentation.

Changes

SDK updates

The SDKs have been updated with the following changes for this release:

Device-based policies are now consumable by customers and development partners.

Access to sensitive files stored by SDKs is restricted to the current logged in OS user.

Support for C++ asynchronous authentication and peering methods has been deprecated in this release and they will be removed in a future release. Customers are advised to use synchronous methods instead and raise a feature request via the service desk (support@arqit.uk) if asynchronous methods are required for an app or service.

Partners and customers are advised to incorporate this latest (v24.02) SDK release into their apps and services.

Minor changes

Users updating their own email address will now receive a link via an email, which must be verified before the change is completed.

Known issues

QC-2901 (QCPI/PaaS) Python SDK does not currently support Python v3.11. Support will be added in a future release. SDK developers are advised to use v3.10 of Python in the interim.

SDK feature matrix

Some features are not yet available across the suite of SDKs, these are captured in the table below.