This document describes standard governance controls. Customer-specific contractual commitments are defined in the applicable service agreement.
Objective
This policy defines the cryptographic controls used by StackTrack to protect confidential, customer and security-sensitive information throughout its lifecycle.
Cryptographic controls are applied as part of StackTrack's Secure by Design approach. Encryption and cryptographic isolation should be provided by the platform by default wherever practical, rather than relying on individual users or operators to enable them manually.
Scope
This policy applies to:
- StackTrack information systems and services;
- customer environments managed by StackTrack;
- customer data processed, stored or transmitted by StackTrack;
- backups, snapshots and replicas;
- employee and administrative devices;
- cryptographic keys, certificates and other cryptographic material; and
- third-party services used to process or store protected information.
General principles
Confidential, customer and security-sensitive information must be protected using cryptographic controls appropriate to the information and the system in which it is processed.
StackTrack applies the following principles:
- encryption in transit and at rest is the default for protected information;
- customer environments must remain cryptographically separated;
- cryptographic keys must not be shared between customers;
- keys must be protected independently from the information they secure;
- approved protocols, algorithms and cryptographic implementations must be used;
- access to cryptographic systems and key-management functions must follow least-privilege principles;
- obsolete or insecure cryptographic protocols must not be used; and
- cryptographic controls must not prevent authorised recovery of systems or customer information.
Information already intended for public disclosure does not require encryption solely because it is transmitted or stored electronically.
Encryption of data in transit
Confidential, customer and security-sensitive information must be encrypted when transmitted across public, untrusted or shared networks.
Approved secure transport protocols must be used for:
- customer-facing services;
- administrative interfaces;
- service-to-service communications where protected information is transmitted;
- transfer of backups and snapshots;
- database connections where applicable;
- remote administration; and
- transmission of authentication credentials or other security-sensitive information.
Transport security must use currently supported cryptographic protocols and configurations.
Obsolete or insecure protocols and unencrypted administrative access must not be used where protected information, credentials or privileged traffic are transmitted.
Certificates and associated private keys must be managed through approved processes and renewed, replaced or revoked when necessary.
Encryption of data at rest
Confidential and customer information must be encrypted at rest using cryptographic protection provided by an approved platform, storage service or cryptographic system.
This requirement applies where relevant to:
- databases;
- persistent storage;
- block and volume storage;
- object and file storage;
- uploaded files and attachments;
- backups;
- snapshots;
- replicas;
- system-generated reports and exports;
- logs containing protected information; and
- other persistent copies of customer or confidential information.
Encryption must remain effective throughout the lifecycle of the information, including replication, backup, restoration and migration processes.
Customer cryptographic isolation
StackTrack maintains cryptographic separation between customer environments.
Each customer is protected using unique private cryptographic key material. Customer key material is protected using approved key-management systems backed by Hardware Security Modules (HSMs).
Cryptographic keys used to protect one customer must not be reused to protect another customer.
Customer-specific cryptographic protection extends to retained copies of customer information, including:
- primary storage;
- backups; and
- snapshots.
The compromise or revocation of one customer's key material must not weaken the cryptographic protection applied to another customer's information.
Key management
Cryptographic keys must be generated, stored, accessed and managed through approved key-management systems.
Where StackTrack manages cryptographic keys protecting customer information, the underlying key protection must use HSM-backed cryptographic services where supported by the relevant platform or architecture.
Key-management controls must provide, where applicable:
- secure key generation;
- protection of private key material;
- least-privilege access;
- separation between keys and the data they protect;
- logging and auditing of key-management operations;
- key rotation or replacement;
- revocation;
- recovery where required for service continuity; and
- secure destruction at the end of the required lifecycle.
Access to key-management functions must be restricted to authorised systems and personnel.
Raw private key material must not be unnecessarily exposed to applications, users or operators.
Key rotation and replacement
Cryptographic keys must be rotated or replaced according to their purpose, platform capability, applicable cryptoperiod and risk.
Automated key rotation should be used where supported and operationally appropriate.
A key must be replaced or revoked where:
- compromise is known or reasonably suspected;
- an authorised user or system should no longer have access;
- a cryptographic algorithm or implementation is no longer considered appropriate;
- required by a customer, contract or regulatory obligation; or
- required as part of an infrastructure or security change.
Key rotation must not unnecessarily prevent access to information that remains subject to legitimate retention or recovery requirements.
Backups and snapshots
Backups and snapshots containing customer or confidential information must receive equivalent cryptographic protection to the source information.
This includes encryption:
- while the backup or snapshot is stored;
- while it is replicated or transferred; and
- during restoration where information passes across an untrusted or shared network.
Customer-specific cryptographic separation must be maintained for backups and snapshots.
Backup encryption and key-management arrangements must support authorised restoration within the applicable service recovery requirements.
Secrets and credentials
Passwords, API credentials, access tokens and other application secrets are not cryptographic encryption keys and must be managed separately.
Secrets used for automated systems must:
- be stored using an approved secrets-management mechanism;
- not be committed to source-code repositories;
- not be stored in plaintext configuration where a secure alternative is available;
- be accessible only to authorised users and workloads;
- be replaced when compromise is known or suspected; and
- be rotated where appropriate to the credential type and associated risk.
Long-lived credentials should be avoided where temporary or workload-based credentials are available.
Certificates and private keys
Private keys associated with digital certificates must be protected against unauthorised access and disclosure.
Certificate management must include:
- controlled issuance;
- appropriate validation;
- secure storage of private keys;
- renewal before expiry;
- revocation or replacement following compromise; and
- removal when a service is decommissioned.
Automated certificate issuance and renewal should be used where supported.
Administrative and remote access
Administrative access to StackTrack and customer-managed infrastructure must use encrypted protocols.
Unencrypted remote administration protocols must not be used.
SSH keys, certificates and other credentials used for privileged access must be:
- individually attributable where appropriate;
- protected from unauthorised access;
- revoked when no longer required; and
- replaced where compromise is suspected.
Shared administrative credentials should be avoided.
End-user devices
Devices used to access or process confidential or customer information must use appropriate device encryption where supported.
This includes laptops and other portable computing devices used by StackTrack personnel.
Devices must also be protected using appropriate authentication controls in accordance with the Access Control Policy.
Removable media
Confidential and customer information should not normally be stored on removable media.
Where there is a legitimate business requirement to use removable media for protected information:
- its use must be authorised;
- the media must be encrypted;
- access must be restricted to authorised individuals; and
- the information must be securely removed when no longer required.
Email and information transfer
Email should not be used as the primary mechanism for transferring highly sensitive information where a more appropriate secure system is available.
Confidential or customer information must be transferred using an approved method providing protection appropriate to the information involved.
Where email is used, appropriate transport protection must be applied. Particularly sensitive information or credentials should instead be shared through an approved secure file-transfer, secrets-management or collaboration system.
Passwords, private cryptographic keys and equivalent security credentials must not be sent in plaintext email.
Third-party and cloud services
Cloud platforms and third-party services processing confidential or customer information must provide cryptographic controls appropriate to the information being processed.
Where supported, StackTrack prefers platform-native encryption and managed cryptographic services that provide:
- encryption at rest;
- encryption in transit;
- controlled key access;
- auditability; and
- HSM-backed protection of cryptographic key material.
Third-party cryptographic controls must be considered as part of supplier and service security assessments.
Legal and regulatory requirements
Cryptographic controls must comply with applicable legal, regulatory, contractual and customer requirements in the jurisdictions in which StackTrack operates or processes information.
Where information is transferred between jurisdictions, applicable restrictions relating to cryptography, data protection and international transfer must be considered.
Cryptographic controls do not replace the requirement to comply with applicable data-transfer and information-handling obligations.
Avoiding adverse impacts from encryption
Encryption must not prevent authorised access to information required for:
- service operation;
- incident response;
- business continuity;
- disaster recovery;
- backup restoration; or
- applicable legal and regulatory obligations.
Access to recovery mechanisms and cryptographic key-management functions must remain appropriately restricted and audited.
Exceptions
Any exception to this policy must:
- have a documented business or technical justification;
- identify the information and systems affected;
- assess the associated security risk;
- define appropriate compensating controls where required; and
- receive approval from the appropriate authorised person.
Exceptions must be reviewed when the affected system or risk changes.
Related controls
This policy should be read alongside StackTrack's:
- Information Classification and Handling Policy;
- Access Control Policy;
- Backup Policy;
- Business Continuity and Disaster Recovery controls;
- Secure Development and Change Management controls; and
- Secure by Design framework.
Policy review
This policy must be reviewed periodically and whenever there is a material change to:
- StackTrack's infrastructure or cryptographic architecture;
- applicable legal or regulatory requirements;
- recognised cryptographic security guidance; or
- the threats affecting the confidentiality or integrity of information.
Cryptographic algorithms, protocols and configurations may be updated without requiring a fundamental change to this policy where necessary to maintain appropriate security.
Classification: Public Owner: StackTrack Review frequency: At least annually