> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/security/security-bulletins/is-nexthink-affected-by-solarwinds-breach_.md).

# Is Nexthink affected by SolarWinds breach?

## Question <a href="#isnexthinkaffectedbysolarwindsbreach-question" id="isnexthinkaffectedbysolarwindsbreach-question"></a>

Is Nexthink affected by the recent SolarWinds breach?

## Answer <a href="#isnexthinkaffectedbysolarwindsbreach-answer" id="isnexthinkaffectedbysolarwindsbreach-answer"></a>

**No, it is not**. Nexthink does not use SolarWinds Orion and has never used SolarWinds Orion. Therefore, we are not affected by this data breach. Even so, we took additional precautionary steps, including having an independent security company search for endpoint and network indicators of compromise (IoC) in our environment. This investigation confirmed that Nexthink is not affected.

### **Background**

SolarWinds offers a product family called [Orion Platform](https://www.solarwinds.com/solutions/orion) for IT monitoring. [According to SolarWinds](https://www.solarwinds.com/securityadvisory), versions 2019.4 HF 5, 2020.2 with no hotfix installed, and 2020.2 HF 1 had a vulnerability inserted in them which, if present and activated, could potentially allow an attacker to compromise the server on which the Orion products run. According to [media reports](https://www.washingtonpost.com/national-security/russian-government-spies-are-behind-a-broad-hacking-campaign-that-has-breached-us-agencies-and-a-top-cyber-firm/2020/12/13/d5a53b88-3d7d-11eb-9453-fc36ba051781_story/), this vulnerability was allegedly inserted by a state-sponsored threat actor to further compromise high-value targets including multiple US federal government agencies.

### **How is Nexthink protecting their products against supply-chain attacks like this?**

Secure software development is an integral part of our security program. As such, several security controls have been implemented to detect vulnerabilities from the early stages of the design to the release of products to customers. This includes, but is not limited to, design reviews, third-party library assessments, code reviews, continuous vulnerability scanning and penetration tests. In addition, we classify all components of our software supply chain as critical and apply additional security controls to them. Nexthink binaries are signed following a strict signature process that makes use of a Hardware Security Module (HSM) and ensures strong integrity and suitability requirements.

**Nexthink has also achieved the ISO 27001, 27017 and 27018 certifications for our Nexthink Experience cloud platform.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/security/security-bulletins/is-nexthink-affected-by-solarwinds-breach_.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
