> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/security-and-support/security/iso-27001-compliance.md).

# ISO 27001 Compliance

## Overview

Datalink's Information Security Management System is ISO 27001 certified, and contains a comprehensive set of technical and organisational controls to operate securely in line with industry best practice.

* Information Security governance is driven at the top level
* Its Information Security Management System implements a range of controls to protect customer data
* Its Crisisworks application is engineered with security in mind, and provides security features to its customers for access control and audit.
* Our network infrastructure (operated by AWS) is highly secure.
* Datalink handles its customer data with great care, with numerous controls to manage PII and sensitive data from staff, contractors and other tenants.

Our information security management system and controls are audited annually.

<div align="left"><figure><img src="/files/0gN92IkEUvLXR5smM3Nk" alt="" width="188"><figcaption><p>ISO 27001 Certification Mark</p></figcaption></figure></div>

## Controls

The following ISO 27001 Annex A controls are applicable to Datalink’s ISMS and are subject to annual external audit.

### Annex A.5

A.5.1 Policies for information security

A.5.2 Information security roles and responsibilities

A.5.3 Segregation of duties

A.5.4 Management responsibilities

A.5.5 Contact with authorities

A.5.6 Contact with special interest groups

A.5.7 Threat intelligence

A.5.8 Information security in project management

A.5.9 Inventory of information and other associated assets

A.5.10 Acceptable use of information and other associated assets

A.5.11 Return of assets

A.5.12 Classification of information

A.5.13 Labelling of information

A.5.14 Information transfer

A.5.15 Access control

A.5.16 Identity management

A.5.17 Authentication information

A.5.18 Access rights

A.5.19 Information security in supplier relationships

A.5.20 Addressing information security within supplier agreements

A.5.21 Managing information security in the ICT supply chain

A.5.22 Monitoring, review and change management of supplier services

A.5.23 Information security for use of cloud services

A.5.24 Information security incident management planning and preparation

A.5.25 Assessment and decision on information security events

A.5.26 Response to information security incidents

A.5.27 Learning from information security incidents

A.5.28 Collection of evidence

A.5.29 Information security during disruption

A.5.30 ICT readiness for business continuity

A.5.31 Legal, statutory, regulatory and contractual requirements

A.5.32 Intellectual property rights

A.5.33 Protection of records

A.5.34 Privacy and protection of PII

A.5.35 Independent review of information security

A.5.36 Compliance with policies, rules and standards for information security

A.5.37 Documented operating procedures

### Annex A.6

A.6.1 Screening

A.6.2 Terms and conditions of employment

A.6.3 Information security awareness, education and training

A.6.4 Disciplinary process

A.6.5 Responsibilities after termination or change of employment

A.6.6 Confidentiality or non-disclosure agreements

A.6.7 Remote working

A.6.8 Information security event reporting

### Annex A.7

A.7.7 Clear desk and clear screen

A.7.10 Storage media

A.7.14 Secure disposal or re-use of equipment

### Annex A.8

A.8.1 User endpoint devices

A.8.2 Privileged access rights

A.8.3 Information access restriction

A.8.4 Access to source code

A.8.5 Secure authentication

A.8.6 Capacity management

A.8.7 Protection against malware

A.8.8 Management of technical vulnerabilities

A.8.9 Configuration management

A.8.10 Information deletion

A.8.11 Data masking

A.8.12 Data leakage prevention

A.8.13 Information backup

A.8.14 Redundancy of information processing facilities

A.8.15 Logging

A.8.16 Monitoring activities

A.8.17 Clock synchronization

A.8.18 Use of privileged utility programs

A.8.19 Installation of software on operational systems

A.8.20 Networks security

A.8.21 Security of network services

A.8.22 Segregation of networks

A.8.23 Web filtering

A.8.24 Use of cryptography

A.8.25 Secure development life cycle

A.8.26 Application security requirements

A.8.27 Secure system architecture and engineering principles

A.8.28 Secure coding

A.8.29 Security testing in development and acceptance

A.8.30 Outsourced development

A.8.31 Separation of development, test and production environments

A.8.32 Change management

A.8.33 Test information

A.8.34 Protection of information systems during audit testing

## Audits

Datalink's information security management system and controls are annually audited by:

* NPX (internal audit)
* Global Compliance & Certification (external audit)

### Certificate

The ISO/IEC 27001:2022 Certificate can be downloaded below.

{% file src="/files/iKqyBf5RVdXacpXGSyjq" %}

| **Approved by CISO**   | 6 March 2025 |
| ---------------------- | ------------ |
| **Next review before** | 6 March 2026 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cw.crisisworks.com/security-and-support/security/iso-27001-compliance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
