DISX Secure Collaboration Deployment and Operations Guide

Why can DISX take longer to deploy than a standard cloud collaboration platform?

A standard SaaS platform may be provisioned quickly because the primary task is enabling access to an existing service. A DISX deployment can include customer-specific configuration, security and quality checks, identity preparation, approved collaboration arrangements, the build of hardened endpoints and security clearance verification.

Some elements are deliberately reviewed rather than left to a completely automated deployment pattern. The result is an environment prepared for operational use, rather than a tenant that still requires the customer to design and organise the surrounding security and service-management arrangements.

What happens from contract signature to first login?

The onboarding journey begins with a prerequisite pack for the customer’s nominated point of contact. This captures the information needed to prepare the service, including in-scope users, vetting or clearance details, required applications, external collaborators and access to services such as r.mil.uk email or MOD core network services where included in scope and subject to the relevant approvals.

The DISX team then builds and configures the environment behind the scenes. For a larger DISX Pro deployment, this can account for several weeks of the implementation period. As go-live approaches, the focus moves to user configuration, identity checks, training and communications. Training can be provided through a webinar, written guides or another agreed approach.

On the agreed go-live date, users receive the credentials and instructions needed to access the service.

What does Day 1 look like?

Go-live is the point at which the in-scope users become operational. They can authenticate to the service, use the agreed functionality, collaborate with approved organisations and process information appropriate to the environment. There is no separate post-deployment waiting period before the service becomes usable.

This distinction is important when evaluating time to value. The deployment period includes the work needed to make the environment ready; the team is expected to be able to work when that period ends.

What usually delays deployment?

The most common delays arise when prerequisite information, licences, application media, user details or clearance information are not available when needed. Bespoke DISX Pro environments can also take longer where additional applications or integrations must be designed and introduced.

Onboarding should begin with a clear owner on the customer side and a complete view of users, devices, applications and collaborating organisations.

Can onboarding be phased?

Yes. A customer can choose a single go-live or bring users on by project, programme or business unit. DISX has supported both small phased onboarding and go-lives involving hundreds of users in one day.

The preferred approach usually depends on internal readiness, training, device distribution and the urgency of the customer’s programme.

Can an external organisation be added after go-live?

Yes. Post-go-live collaboration is handled through a defined service request in the customer portal. The DISX service desk works with the customer security assurance function to obtain evidence that the external environment is appropriate to connect to the DISX environment.

These requests can typically be completed within five working days, provided the required evidence and information are available.

When is a managed physical endpoint required?

The endpoint decision depends on the operating model and assurance scope. A managed physical endpoint may be needed when the organisation cannot apply the required controls to its existing corporate device, when the physical device must form part of a Cyber Essentials or Cyber Essentials Plus boundary, or when the customer’s DCC and contractual requirements make a dedicated managed device the clearer option.

For the purpose of accessing and processing information in DISX, physical and virtual endpoint models can both be appropriate. The correct choice is driven by the wider control boundary and user requirement.

What happens to a device when a user leaves?

A DISX device is managed as an asset within the secure service. When a user leaves, it can be rebuilt for another authorised user, securely wiped and returned to the customer’s corporate environment, or sanitised for another approved form of reuse or disposal.

The account and access-removal process is handled separately so that the departing user no longer has access to the service or its information.

How quickly can access be revoked?

Access can be revoked immediately once an authorised request reaches the service desk. This supports urgent leaver, role-change and security-incident scenarios.

The customer remains responsible for notifying Logiq when someone joins, changes role or leaves. Logiq cannot act on an employment or project change that has not been communicated.

Who owns the information-management decisions?

The customer owns its information and determines who should be able to access it. DISX provides the managed controls and administration needed to enforce those decisions, while the customer remains accountable for data ownership, classification, need-to-know decisions and the timely notification of joiners, movers and leavers.

What responsibilities remain with the customer?

The customer retains responsibility for its information, user population and contractual obligations. This includes nominating service and security contacts, notifying Logiq about joiners, movers and leavers, managing information ownership and access decisions, and making sure security requirements from the contracting authority are understood and flowed through its supply chain.

Logiq supports these responsibilities with service processes and reporting, including information that can help identify inactive users. The relationship works best as a shared operating model rather than a complete transfer of accountability.

How does DISX reduce operational risk?

The customer does not need to assemble every component of the operating model independently. Identity, endpoint options, access administration, security monitoring, maintenance, vulnerability management, assurance and support are brought together within one managed service.

This gives the customer a clearer line of responsibility for operating the secure environment and helps provide evidence that the controls are being maintained, rather than relying on a platform configuration that may become outdated after deployment.

How is compliance maintained over time?

The security posture is reviewed on an ongoing basis, rather than treated as a one-off deployment activity. Logiq evaluates relevant security notices, MOD and industry guidance, changes in customer requirements and the ongoing performance of the service.

The DISX roadmap also follows changes in Microsoft technology. New capabilities and platform changes are reviewed to determine how they should be designed into the service, whether controls need to change and how security can be improved without creating unnecessary operational friction.

This combines formal governance, risk and compliance activity with an evergreen improvement programme.

Can DISX integrate with existing customer infrastructure?

DISX is often kept separate from the existing corporate environment by design, particularly where that environment is not approved or suitable for the information being processed. Integration is still possible where there is a valid operational need. Logiq has connected DISX cloud services with existing on-premises environments and specialist operational systems. These integrations are assessed, designed and assured case by case because every legacy and operational environment is different.

Does buying DISX automatically make an organisation compliant or DCC certified?

Organisations are responsible for the ownership of their certification, contractual scope and security obligations. DISX can underpin a substantial part of the technical and operational control environment, but certification also depends on the customer’s wider people, processes, governance and supply-chain arrangements.

Logiq’s cyber advisory capability can help customers understand scope and prepare for Cyber Essentials, Cyber Essentials Plus or DCC, working alongside the appropriate certification body where required. In partnership with customers, we can support the entire journey.