> 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-8.2.md).
# PA-DSS requirement 8.2
Use only necessary and secure services, protocols, components, and dependent software and hardware, including those provided by third partie
Maitre’D has very few dependencies in regards to 3rd party software, services or protocols. These will vary depending on the modules that are used.
\
Hardware dependencies
Maitre’D has no specific hardware dependency.
### Software dependencies
**EFT Client software**
When an integrated solution is in use, a 3rd party client software or “middleware” needs to be used. Maitre’D will pass the credit card information to the middleware for processing. Information coming back from the acquirer/processor takes the opposite way, from the internet to the middleware, and then back to Maitre’D.
Supported EFT middleware for integrated credit card payments:
* Datacap DSIClientX version 3.86 (File version 3.8.6.0, dated December 3rd, 2012)
### Service dependencies
**Crypkey License**
The Crypkey license service is required to validate the Maitre’D license activation key, and needs to be running all the time.
**Protocol dependencies TCP/IP**
The TCP/IP protocol is required for network communication
---
# 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-8.2.md?ask=&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.