Governance · Policy

Supplier Security Policy

Governing entity
Servana Managed Services Ltd
Framework
StackTrack Governance
Effective date
13 August 2026
Version
2026-08-13
Document owner
Managing Director
Next review
13 August 2027

This document describes standard governance controls. Customer-specific contractual commitments are defined in the applicable service agreement.

Objective

Servana Managed Services Ltd relies on cloud platforms, software providers, infrastructure services and other suppliers in the delivery of StackTrack services.

This policy defines the controls used to assess, approve and monitor suppliers whose products or services could materially affect:

  • the confidentiality, integrity or availability of information;
  • customer data;
  • StackTrack Managed Services;
  • business continuity;
  • information security;
  • data protection; or
  • Servana's contractual and regulatory obligations.

Supplier controls are proportionate to the risk presented by the supplier and the services being provided.

Scope

This policy applies to third-party organisations that:

  • process, store or transmit Servana or customer information;
  • provide cloud infrastructure or hosting;
  • provide software-as-a-service or managed technology services;
  • have administrative or privileged access to Servana or customer systems;
  • provide security, monitoring or operational services;
  • provide critical software or infrastructure dependencies;
  • provide business services that could materially affect Servana's operations; or
  • otherwise have the ability to materially affect information security or service resilience.

This policy does not apply to personnel engaged directly under Servana employment arrangements, which are governed through separate personnel and access-control processes.

Principles

Servana applies the following principles to supplier management:

  • supplier controls must be proportionate to risk;
  • security and resilience should be considered before a material supplier is introduced;
  • suppliers should receive only the access and information necessary to perform their role;
  • contractual controls should reflect the nature of the supplier relationship;
  • suppliers processing personal data must be subject to appropriate data-protection arrangements;
  • material supplier risks must be understood and managed;
  • significant suppliers must be periodically reassessed;
  • material changes in supplier services or risk must be reviewed; and
  • supplier relationships must support appropriate transition and termination arrangements.

Responsibilities

The Directors of Servana are responsible for ensuring that:

  • material suppliers are appropriately assessed before use;
  • supplier risk classifications are established and maintained;
  • supplier approvals are obtained where required;
  • appropriate contractual and security requirements are established;
  • supplier performance and material security risks are periodically reviewed; and
  • significant supplier issues are escalated through the appropriate governance processes.

Operational supplier information, assessments and approvals are maintained through Servana's supplier-management records.

Supplier risk classification

Suppliers are assigned a risk classification based on the nature and significance of the relationship.

Factors considered may include:

  • sensitivity of information processed;
  • access to customer or Servana systems;
  • level of privileged access;
  • volume and type of personal data processed;
  • service criticality;
  • availability and resilience dependencies;
  • substitutability of the supplier;
  • geographic location and data residency;
  • subcontracting dependencies;
  • potential operational impact of supplier failure; and
  • regulatory or contractual requirements.

Suppliers are classified as:

High risk

A supplier may be considered high risk where compromise or failure could cause a significant impact to customer services, protected information or Servana's operations.

Examples may include:

  • primary cloud infrastructure providers;
  • identity or authentication services;
  • providers with significant privileged access;
  • critical security services;
  • critical data-processing platforms; or
  • services forming an essential dependency of Managed Services.

High-risk suppliers require approval from the appropriate Directors before use.

Medium risk

A supplier may be considered medium risk where it processes protected information or supports important business or technical processes, but the potential impact of failure or compromise is more limited.

Medium-risk suppliers require appropriate management approval before use.

Low risk

A supplier may be considered low risk where access to protected information and operational dependency are limited.

Low-risk suppliers remain subject to appropriate assessment and approval, but the depth of assessment may be reduced in proportion to the risk.

Supplier assessment

Material suppliers must be assessed before use.

The scope of assessment depends on supplier risk and may include consideration of:

  • information security controls;
  • security certifications and independent assurance;
  • privacy and data-protection practices;
  • access-control arrangements;
  • cryptographic controls;
  • vulnerability and patch management;
  • incident response capability;
  • business continuity and disaster recovery;
  • service availability and resilience;
  • backup and recovery;
  • software development and change controls;
  • personnel security;
  • physical security where relevant;
  • subcontractor and subprocessor management;
  • data residency;
  • regulatory compliance;
  • financial or operational stability; and
  • exit or transition capability.

Servana may rely on suitable independent assurance where appropriate rather than conducting direct audits of every supplier.

Examples may include recognised certifications, independent audit reports and other credible third-party assurance.

Approval

The level of approval required must reflect the supplier's assessed risk.

At a minimum:

Supplier riskApproval
HighManaging Director and an additional Director
MediumManaging Director or Director
LowManaging Director or Director

Approval must be obtained before a supplier begins processing protected information or receives material access to Servana or customer systems.

Information security requirements

Supplier security requirements must be proportionate to the nature of the service provided.

Where relevant, requirements should address:

  • confidentiality, integrity and availability;
  • access control;
  • authentication;
  • least privilege;
  • encryption;
  • data handling;
  • incident management;
  • vulnerability management;
  • service resilience;
  • backup and recovery;
  • business continuity;
  • change management;
  • logging and monitoring;
  • subcontracting;
  • secure information transfer;
  • data retention and deletion; and
  • termination of access.

Suppliers must not receive broader access to information or systems than is reasonably required to provide their services.

Contractual controls

High- and medium-risk supplier relationships should be governed by an appropriate written agreement or equivalent contractual arrangement.

Depending on the nature of the supplier relationship, contractual requirements may include:

  • scope of services;
  • responsibilities of each party;
  • confidentiality obligations;
  • information-security requirements;
  • protection of customer and Servana information;
  • service availability and performance;
  • incident notification;
  • business continuity and recovery;
  • change management;
  • data protection;
  • subprocessors and subcontractors;
  • intellectual property;
  • termination;
  • data return or deletion;
  • transition arrangements; and
  • dispute resolution.

The contractual control applied should be proportionate to the service and risk.

Standard provider terms may be accepted where they provide appropriate protection and the residual risk is understood.

Personal data and subprocessors

Suppliers processing personal data on behalf of Servana must be assessed and engaged in accordance with applicable data-protection requirements.

Where required, an appropriate data-processing agreement or equivalent contractual terms must be established.

Relevant considerations include:

  • processing purpose and scope;
  • categories of information;
  • security controls;
  • confidentiality;
  • subprocessor use;
  • international transfers;
  • incident notification;
  • assistance with applicable data-subject rights;
  • retention and deletion; and
  • termination of processing.

Use of subprocessors must be managed consistently with applicable customer commitments and data-processing agreements.

Supplier access

Supplier access to Servana or customer systems must be controlled according to the Access Control Policy.

Where suppliers require system access:

  • access must be authorised;
  • least privilege must be applied;
  • individual identities should be used where practical;
  • privileged access must be appropriately protected;
  • access should be time-limited where appropriate;
  • activity should be auditable where technically supported; and
  • access must be removed when it is no longer required.

Shared privileged credentials should be avoided.

Cryptographic protection

Suppliers storing or processing confidential or customer information must provide appropriate cryptographic protection.

Where relevant, this includes:

  • encryption in transit;
  • encryption at rest;
  • appropriate key management;
  • secure handling of credentials and secrets; and
  • protection of backups and replicated information.

Cryptographic controls must be appropriate to the information and consistent with Servana's Cryptographic Controls Policy and applicable customer requirements.

Resilience and continuity

Supplier resilience must be considered where the supplier supports a critical or material service.

Assessment may include:

  • redundancy;
  • geographic resilience;
  • backup arrangements;
  • disaster recovery;
  • recovery objectives;
  • service availability;
  • incident response;
  • capacity management; and
  • dependency on additional third parties.

Servana should seek to avoid unnecessary single points of failure where commercially and technically reasonable.

Where a supplier represents a material dependency, appropriate contingency or recovery arrangements should be understood.

Supplier changes

Material changes to a supplier or supplied service must be assessed where they could affect security, resilience or contractual obligations.

Relevant changes may include:

  • major service architecture changes;
  • new subprocessors;
  • changes in hosting location;
  • changes affecting data residency;
  • significant changes in security controls;
  • acquisitions or ownership changes;
  • significant service degradation;
  • material contractual changes;
  • withdrawal of important functionality; or
  • end-of-life or end-of-support announcements.

Where necessary, supplier risk must be reassessed following such changes.

Security incidents

Suppliers must provide appropriate mechanisms for reporting security incidents that affect Servana, StackTrack services or protected information.

Material supplier incidents must be evaluated in accordance with Servana's incident-management processes.

Where applicable, suppliers may be required to provide information necessary to:

  • assess impact;
  • contain risk;
  • communicate with customers;
  • meet legal or contractual notification requirements;
  • restore services; and
  • investigate causes.

Supplier incidents should also be considered as part of subsequent supplier review where appropriate.

Monitoring and reassessment

Material suppliers are subject to periodic review.

The frequency and depth of reassessment should reflect:

  • supplier risk classification;
  • service criticality;
  • information processed;
  • previous assessment findings;
  • significant incidents;
  • service changes; and
  • changes in applicable requirements.

Review activities may include:

  • security questionnaires;
  • review of certifications;
  • independent assurance reports;
  • supplier meetings;
  • service-performance reviews;
  • incident history;
  • contractual reviews; and
  • reassessment of identified risks.

High-risk suppliers should normally receive greater scrutiny than lower-risk suppliers.

Supplier performance

The performance of significant suppliers should be considered as part of Servana's management and service-review activities.

Relevant factors may include:

  • reliability;
  • availability;
  • security performance;
  • incident handling;
  • responsiveness;
  • contractual performance;
  • quality of technical support;
  • change management; and
  • continued suitability for the services being provided.

Material concerns should be recorded and addressed according to their significance.

Independent assurance and audit

Where appropriate, Servana may request or review independent assurance regarding a supplier's controls.

This may include:

  • recognised security certifications;
  • independent audit reports;
  • penetration testing summaries;
  • compliance attestations; or
  • other suitable assurance evidence.

Direct supplier audits should generally be used where justified by risk, contractual requirements or applicable legal obligations.

The absence of direct audit does not prevent Servana from relying on credible independent assurance where this provides appropriate evidence of control effectiveness.

Supplier risk

Information-security and operational risks arising from suppliers must be managed through Servana's established risk-management processes.

Where material risk cannot be adequately mitigated, Servana may:

  • require additional controls;
  • restrict the supplier's access or use;
  • introduce compensating controls;
  • seek an alternative supplier;
  • modify the service architecture; or
  • discontinue use of the supplier.

Termination and exit

Supplier relationships must be terminated in a controlled manner.

Where applicable, termination activities include:

  • revoking access;
  • disabling credentials;
  • returning or deleting protected information;
  • recovering Servana assets;
  • confirming data disposition where appropriate;
  • transferring required services or data;
  • removing integrations;
  • reviewing continuing dependencies; and
  • maintaining information required by legal or contractual retention obligations.

Exit requirements should be considered before adopting a supplier where supplier dependency is material.

Environmental and quality considerations

Where appropriate to the supplier relationship, Servana may also consider:

  • environmental practices;
  • energy efficiency;
  • service quality;
  • operational maturity;
  • support capability; and
  • continual-improvement practices.

These considerations complement, rather than replace, information-security and resilience requirements.

Responsibilities of suppliers

Suppliers are expected to:

  • comply with applicable contractual requirements;
  • protect information entrusted to them;
  • limit access to authorised personnel;
  • maintain controls appropriate to the services they provide;
  • notify Servana of material incidents where required;
  • manage subcontractors appropriately;
  • support reasonable security-assurance activities; and
  • cooperate with Servana where necessary to manage material security or operational risks.

Exceptions

Exceptions to this policy must:

  • have a documented business or technical justification;
  • identify the affected supplier and services;
  • assess the associated risk;
  • identify appropriate compensating controls where required; and
  • receive appropriate approval.

Exceptions should be reviewed when the supplier, service or associated risk materially changes.

This policy should be read alongside StackTrack's:

  • Information Security Policy;
  • Information Classification and Handling Policy;
  • Access Control Policy;
  • Cryptographic Controls Policy;
  • Incident Management Policy;
  • Business Continuity controls; and
  • Secure by Design framework.

Operational supplier assessments, risk decisions and supplier records are maintained separately from this publicly available policy.

Policy availability

This policy is publicly available as part of StackTrack's Governance documentation.

Publication supports transparency regarding the controls Servana applies when selecting and managing suppliers that may affect StackTrack services and protected information.

Policy review

This policy is reviewed at least annually and following significant changes to:

  • Servana's supplier relationships;
  • material technology dependencies;
  • information-security requirements;
  • customer or contractual requirements;
  • applicable legal or regulatory obligations; or
  • Servana's supplier-risk management processes.

Material changes will be published as a new version of this policy.

Related governance