Governance · Policy

Information Security Policy | StackTrack Governance

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 is committed to protecting the confidentiality, integrity and availability of the information entrusted to it.

This policy establishes the principles through which Servana manages information security across its operations and the StackTrack services it provides.

Our objectives are to:

  1. protect information assets that Servana owns, processes, manages or can access;
  2. maintain the confidentiality, integrity and availability of information and systems;
  3. implement security controls proportionate to the value, sensitivity and criticality of information and the threats to which it may be exposed;
  4. comply with applicable legal, regulatory, contractual and other information-security requirements;
  5. identify and manage information-security risk systematically;
  6. maintain effective security, resilience and recovery capabilities; and
  7. continually improve Servana's Information Security Management System and its ability to respond to changing threats.

Scope

This policy applies to all people, processes, technology, services and information assets within the scope of Servana's Information Security Management System.

This includes, where applicable:

  • employees;
  • directors;
  • contractors and consultants;
  • cloud infrastructure;
  • customer environments managed by StackTrack;
  • internal business systems;
  • software and SaaS platforms;
  • information-processing facilities;
  • suppliers and service providers;
  • networks and communications;
  • endpoint devices; and
  • information in electronic or physical form.

All personnel and contractors whose activities can affect information security are expected to comply with this policy and the controls relevant to their responsibilities.

Information Security Management System

Servana maintains an Information Security Management System to provide a structured framework for managing information-security risk.

The ISMS is independently certified against ISO/IEC 27001 within its defined certification scope.

The ISMS supports:

  • systematic identification of information-security risk;
  • selection and implementation of appropriate controls;
  • monitoring of control effectiveness;
  • management of security incidents;
  • business continuity and recovery;
  • internal audit;
  • management review;
  • corrective action; and
  • continual improvement.

Certification does not remove the need to continually assess and improve controls as technology, services and threats evolve.

Secure by Design

Information security should be incorporated into the design and operation of systems from the beginning rather than added only after implementation.

StackTrack's Secure by Design approach seeks to establish secure defaults and repeatable controls across infrastructure and Managed Services.

Where appropriate, this includes:

  • least-privilege access;
  • strong identity and authentication;
  • encryption by default;
  • customer isolation;
  • infrastructure automation;
  • controlled change;
  • secure configuration;
  • vulnerability management;
  • logging and monitoring;
  • backup and recovery;
  • resilience; and
  • lifecycle management.

Security controls should reduce dependence on individual judgement where effective platform-level or automated controls can provide more consistent protection.

Risk management

Information-security risks must be identified, assessed and treated according to Servana's established risk-management processes.

Risk assessments should consider, where relevant:

  • confidentiality;
  • integrity;
  • availability;
  • customer impact;
  • business impact;
  • legal and regulatory obligations;
  • contractual requirements;
  • threat likelihood;
  • vulnerability;
  • technical dependencies;
  • supplier dependencies; and
  • existing controls.

Controls must be proportionate to the identified risk.

Risk treatment may include:

  • reducing risk through technical or organisational controls;
  • avoiding activities that create unacceptable risk;
  • transferring appropriate risk through contractual or insurance arrangements; or
  • formally accepting residual risk where authorised and justified.

Material risks must be subject to appropriate oversight.

Information classification and handling

Information must be handled according to its sensitivity, purpose and applicable obligations.

Appropriate controls may include:

  • classification;
  • access restrictions;
  • encryption;
  • secure transmission;
  • retention requirements;
  • disposal requirements;
  • logging; and
  • restrictions on sharing.

Customer and confidential information must not be made available to individuals, systems or suppliers without an authorised business purpose.

Detailed requirements are defined through Servana's Information Classification and Handling Policy.

Access control

Access to information and systems must be based on business need and least-privilege principles.

Controls should include, where appropriate:

  • unique user identities;
  • appropriate authentication;
  • multi-factor authentication;
  • role-based or policy-based access;
  • privileged-access controls;
  • periodic access review;
  • prompt removal of unnecessary access;
  • separation of duties; and
  • logging of security-relevant activity.

Shared privileged accounts should be avoided where individual accountability can reasonably be provided.

Access requirements are further defined through the Access Control Policy.

Cryptographic controls

Confidential, customer and security-sensitive information must be protected using appropriate cryptographic controls.

Servana's cryptographic principles include:

  • encryption in transit and at rest for protected information;
  • approved algorithms and protocols;
  • appropriate certificate management;
  • customer-specific cryptographic separation;
  • HSM-backed protection of customer key material where applicable;
  • controlled key access;
  • secure management of secrets and credentials; and
  • protection of backups and snapshots.

Detailed requirements are defined in the Cryptographic Controls Policy.

Infrastructure and platform security

Infrastructure used to deliver StackTrack services must be designed and operated with appropriate security controls.

Where relevant, controls include:

  • secure baseline configuration;
  • infrastructure as code;
  • network segmentation;
  • access restrictions;
  • automated configuration;
  • hardened administrative access;
  • patch and lifecycle management;
  • vulnerability management;
  • monitoring;
  • backup and recovery; and
  • resilience across appropriate infrastructure boundaries.

Security architecture should seek to minimise unnecessary exposure and reduce the number of manually maintained controls.

Vulnerability and lifecycle management

Systems and software must be maintained at supported and secure lifecycle states where reasonably practicable.

Servana monitors relevant vulnerabilities and evaluates their potential impact based on factors including:

  • exploitability;
  • exposure;
  • data sensitivity;
  • service criticality;
  • existing mitigating controls; and
  • vendor guidance.

Security updates and remediation should be prioritised according to risk.

Unsupported or end-of-life technology should be avoided or subject to specific risk treatment and compensating controls.

Change management

Changes that could materially affect information security must be controlled according to their risk.

Appropriate controls may include:

  • peer review;
  • automated validation;
  • testing;
  • staged deployment;
  • approval;
  • rollback capability;
  • post-change verification; and
  • monitoring.

Emergency changes may use accelerated procedures where necessary to address an immediate security or operational risk, but must remain appropriately controlled and reviewed.

Monitoring and detection

Systems and services must be monitored at a level appropriate to their criticality and security risk.

Monitoring may include:

  • authentication events;
  • privileged activity;
  • service health;
  • security events;
  • infrastructure changes;
  • vulnerability information;
  • backup failures;
  • unusual network activity; and
  • other indicators of potential compromise or control failure.

Security-relevant events must be reviewed and escalated where appropriate.

Security incidents

Information-security incidents must be identified, reported, assessed and managed through established incident-management processes.

Incident handling should support:

  • containment;
  • investigation;
  • recovery;
  • preservation of relevant evidence;
  • communication;
  • legal and contractual notification requirements;
  • identification of contributing causes; and
  • corrective action.

Servana seeks to prevent security incidents through appropriate controls, but recognises that no security programme can guarantee that all incidents will be prevented.

The objective is therefore to reduce the likelihood and impact of incidents while maintaining effective detection, response and recovery capabilities.

Backup, resilience and recovery

Information and systems requiring protection against loss must have appropriate backup and recovery arrangements.

Backup controls include:

  • encryption;
  • geographic resilience;
  • retention;
  • monitoring;
  • restore testing; and
  • defined recovery objectives.

Detailed Managed Service backup and recovery requirements are defined through the Backup Policy and applicable service commitments.

Servana also maintains business-continuity arrangements appropriate to identified operational risks.

Supplier security

Suppliers whose products or services could affect information security must be assessed according to risk.

Supplier controls may include:

  • security assessment;
  • contractual requirements;
  • data-protection arrangements;
  • access controls;
  • independent assurance;
  • incident requirements;
  • resilience review;
  • subprocessor consideration; and
  • periodic reassessment.

Detailed supplier controls are defined in the Supplier Security Policy.

Personnel security

Personnel must understand and fulfil their responsibilities for protecting information.

Servana supports this through appropriate:

  • onboarding;
  • confidentiality obligations;
  • access management;
  • security awareness;
  • role-specific training;
  • acceptable-use requirements;
  • reporting mechanisms; and
  • offboarding controls.

Security responsibilities continue to apply to contractors and other authorised personnel according to their role and access.

Security awareness and competence

Personnel whose work can affect information security must receive information, instruction or training appropriate to their responsibilities.

Awareness should include topics such as:

  • phishing and social engineering;
  • credential protection;
  • information handling;
  • incident reporting;
  • acceptable use;
  • secure remote working;
  • access control; and
  • relevant organisational policies.

Specialist personnel must maintain appropriate technical competence for security-sensitive responsibilities.

Business continuity

Servana maintains business-continuity and recovery arrangements designed to support continued or restored operation following significant disruption.

Continuity planning should consider:

  • personnel;
  • technology;
  • cloud infrastructure;
  • suppliers;
  • communications;
  • customer services;
  • data availability; and
  • recovery dependencies.

Continuity and recovery arrangements must be periodically reviewed and tested at a level appropriate to the associated risk.

Servana must identify and comply with applicable requirements affecting information security.

These may include:

  • data-protection law;
  • contractual security commitments;
  • confidentiality obligations;
  • intellectual-property requirements;
  • customer security requirements;
  • regulatory requirements; and
  • other applicable legal obligations.

Changes to applicable requirements must be considered through the ISMS and relevant governance processes.

Audit and assurance

The effectiveness of Servana's information-security controls is subject to periodic review.

Assurance activities may include:

  • internal audit;
  • independent certification audit;
  • technical testing;
  • vulnerability assessment;
  • penetration testing;
  • control review;
  • supplier assurance;
  • management review; and
  • service-specific security assessment.

Findings must be assessed and addressed according to their significance.

Continual improvement

Servana is committed to continually improving its ISMS and security controls.

Improvement may be driven by:

  • incidents;
  • audit findings;
  • vulnerability assessments;
  • changes in threats;
  • customer feedback;
  • technology changes;
  • service changes;
  • supplier changes;
  • risk assessments; and
  • lessons learned through normal operations.

Corrective and improvement activities should address underlying causes where reasonably practicable rather than repeatedly treating symptoms.

Responsibilities

The Directors of Servana are responsible for:

  • establishing information-security objectives;
  • maintaining appropriate oversight of the ISMS;
  • ensuring appropriate resources are available;
  • reviewing material information-security risks;
  • supporting continual improvement; and
  • ensuring the ISMS remains aligned with Servana's business and strategic direction.

All personnel and contractors are responsible for:

  • complying with information-security requirements relevant to their work;
  • protecting information entrusted to them;
  • using systems and information appropriately;
  • reporting suspected security incidents or weaknesses;
  • maintaining the confidentiality of protected information; and
  • supporting the effective operation of the ISMS.

Policy compliance

Violations of this policy or associated security requirements may result in appropriate corrective action.

For employees, serious or repeated violations may be addressed through applicable disciplinary procedures.

For contractors, suppliers or other third parties, breaches may be addressed through contractual, access-control or other appropriate measures.

Exceptions

Exceptions to information-security requirements must:

  • have a documented business or technical justification;
  • identify the affected systems, information or services;
  • assess the associated risk;
  • define compensating controls where appropriate;
  • receive suitable approval; and
  • be reviewed when circumstances or risk materially change.

This policy should be read alongside StackTrack's:

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

Policy availability

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

Publication supports transparency regarding the information-security principles and governance controls used by Servana Managed Services Ltd in operating StackTrack services.

Policy review

This policy is reviewed at least annually and whenever there is a material change to:

  • Servana's information-security risk;
  • StackTrack's infrastructure or services;
  • the ISMS;
  • applicable legal or contractual requirements;
  • relevant threat conditions; or
  • the organisation's strategic direction.

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

Related governance