> 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-the-moveit-breach_.md).

# Is Nexthink affected by the MOVEit breach?

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

Is Nexthink affected by the recent MOVEit breach?

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

**No, Nexthink is not impacted.** Nexthink does not use MOVEit as a part of our products and services. There are no MOVEit components in our software.

In addition, there is no impact on the Nexthink production cloud environment. Nexthink security team has reviewed our AWS architecture, and there is no usage of any MOVEit within our cloud environment.

Nexthink continues to monitor the situation and other vulnerabilities as a part of our normal security operations.

### **Background**

On 31 May 2023, software provider Progress Software confirmed a vulnerability in the product MOVEit Transfer that can lead to escalated privilege and potential unauthorized access to their environment. There have been a number of large organizations and government customers that have confirmed potential compromises of their data as a result of this vulnerability.

### **How is Nexthink protecting its products against breaches like this?**

Nexthink applies an in-depth defense strategy, in which multiple controls are thoughtfully layered, providing together mitigation against a wide variety of threats. This includes:

* Multifactor authentication
* Host posture checks
* Restricted access to the management plane
* Continuous monitoring of any suspicious activity

**Nexthink has also achieved the ISO 27001, 27017, 27018, and 27701 and SOC 2 Type 2 certifications for the Nexthink Infinity 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-the-moveit-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.