> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/payment-passkeys-issuers/integrate-d1-sdk/deployment/security-guidelines/security-countermeasures.md).

# Security countermeasures

D1 SDK is designed to provide countermeasures against security threats. The following table shows the list of the known security threats and their corresponding SDK behaviors.

{% hint style="info" %}
If a detection occurs, an `ERROR_DEVICE_ENVIRONMENT_UNSAFE` exception will be thrown.
{% endhint %}

| Security threat          | Description                                                                                                 | Platform     | Build type        |
| ------------------------ | ----------------------------------------------------------------------------------------------------------- | ------------ | ----------------- |
| Root/Jailbreak detection | A rooted or jailbroken device is used to run the application.                                               | Android, iOS | Debug and Release |
| Hook detection           | An attempt is made to hook (intercept) method calls in order to monitor/modify the behavior of the methods. | Android, iOS | Debug and Release |
| Tamper detection         | An attempt is made to tamper with the binary data.                                                          | Android, iOS | Debug and Release |
| Emulator detection       | An Android emulator is used to run the application.                                                         | Android      | Debug and Release |
| Debugger detection       | An attempt is made to reverse engineer the application by attaching a debugger.                             | Android, iOS | Release           |


---

# 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.payments.thalescloud.io/payment-passkeys-issuers/integrate-d1-sdk/deployment/security-guidelines/security-countermeasures.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.