> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-10.2.1.md).

# PA-DSS requirement 10.2.1

Securely deliver remote payment application updates

### Maitre’D Hot Fixes and Service Packs

The Maitre’D software does not update itself remotely. Patches, hotfixes and service packs are all hand-tested in our QA labs before being released.

Once released, the hotfixes are stored on a secure server. Only authorized and qualified Maitre’D technicians are allowed to login to this server to download the hotfixes. Once downloaded, the hotfix needs to be installed manually by an authorized Maitre’D technician.

Authorized and qualified Maitre’D service technicians can download the latest service packs from the following secure website (Username and password required):

<https://distributors.maitredpos.com/distributors/support/softwareanddocumentation/Default.aspx>

Any file obtained by any other means than our secured website should be deleted and re-downloaded to preserve the integrity of the chain-of-trust.

Additionally, the SHA hash is displayed next to the service pack download link. This hash can be counter-verified with various checksum utilities that can be downloaded from the web.

<br>


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-10.2.1.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.