![]() ![]() The service collects minimal data that could be classified as Personally Identifiable Information (PII). ![]() Data collectionĪuto-Update has been designed with consideration towards both security and compliance. Any vulnerabilities are evaluated through Dependabot (see ) before being applied to production systems during scheduled maintenance windows. Security updates to envQUERY are tested and applied regularly. Access is secured by a unique user ID, password and multi-factor token which is rotated every 60 seconds. aiNPGFjzBDMspHGz8KFrHdpFLo8HfEmx)Īuto-Update Repository Authentication - Token randomised (e.g SUhKYzBvQnZYbEZhTXM3aTptVUtxdVdmUnZJZWxVOXRM)Īs an additional security layer, any administrative access to envQUERY is limited and is not externally accessible. It is designed to securely supply details of Auto-Update repositories to managed macOS clients using the service.īelow is an example of what envQUERY stores in the central database:Īuto-Update Repository randomised (e.g. envQUERY is a highly-available clustered web application, hosted within the Auto-Update service infrastructure. Authentication credentials are also rotated periodically to ensure service security.Īnother major component of the Auto-Update service is a custom web application called envQUERY. Each pod has a unique access URL which is anonymised. Authentication to each pod is performed over HTTPS/TLS using Basic Authentication (BA) ensuring credentials are encrypted during transit. Each customer who has purchased the service has their own application pod.Įach pod is a read-only pod and runs its own HTTPS web service (based on NGINX) and serves read-only content from our central application repository. The Auto-Update service has been designed to be both resilient and support multi-tenancy. ![]() If the service cannot verify the signature HMAC Digest of a JWT, it is disregarded and the pending installation run on the managed macOS client is aborted. These tokens are used within the service to transfer repository credentials between the envQUERY web application and managed macOS clients. JWTs are an open, industry standard (RFC 7519) method for representing claims securely between two parties. To ensure further secure validation, communications between managed macOS clients and the Auto-Update service use JSON Web Tokens (JWTs), which are signed using Hash-Based Message Authentication Code (HMAC) and Secure Hash Algorithm 2 (SHA-256). This will invalidate the session as it is considered MITM. By design, the Auto-Update service will reject any traffic to or that has been proxied, SSL decrypted or redirected. Additionally, HTTP Public Key Pinning (HPKP) is used to mitigate the risk of man-in-the-middle attacks (MITM). Additionally, Ekco and Telehouse adhere to strict compliance requirements which can be reviewed below:Īll external communication to the service is limited to the URLs listed below on the following public network range of 185.43.40.102/28:Īll communication between the Auto-Update service and managed macOS clients is performed over HTTPS/TLS 1.2 with a publicly signed wildcard certificate. The dataJAR platform operates and is accredited to the ISO/IEC 27001:2013 (Information Security Management) standard. All infrastructure components are hosted within Telehouse - one of the UK’s leading data centre providers. ![]() Our infrastructure is supplied in partnership with Ekco. Infrastructure overview and complianceĪuto-Update is a cloud-based service hosted within the dataJAR platform. This document outlines dataflows and protocols used in the delivery of this service and is aimed at information security personnel. The purpose of this document is to provide an overview of the security measures that are employed within Auto-Update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |