> For the complete documentation index, see [llms.txt](https://trustcenter.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trustcenter.syntphony.com/trust-center/security/suppliers-security-management.md). # Suppliers Security Management Security requirements applicable to suppliers and supplier relationship management are defined, implemented and improved continuously in NTT DATA EMEAL. A security homologation process is implemented to ensure suppliers are assessed and selected taking into consideration the applicable security requirements. Security requirements applicable to suppliers are captured in contractual agreements, policies, procedures and other authoritative documents. Risks originating from the supply chain are managed through the corporate security risk management process, and treatment measures are defined to reduce the risk impact on NTT DATA EMEAL’s operations. Throughout their relationship with NTT DATA EMEAL, suppliers are expected to implement and improve the agreed security controls, and undergo audits as needed. Assets to which the suppliers have access are handled in accordance with NTT DATA EMEAL’s requirements and returned in accordance with the established ownership. --- # 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://trustcenter.syntphony.com/trust-center/security/suppliers-security-management.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.