> 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/acceptable-user-of-assets.md). # Acceptable User of Assets A Standard has been developed to establish the security requirements for the acceptable use of corporate IT assets by all employees and third parties. It focuses on transparency when it comes to the responsibilities assigned to all Asset Users in complying with the acceptable use rules and reporting security incidents. IT assets are handed to users to carry out the professional activities required by NTT DATA EMEAL. It is prohibited to use NTT DATA EMEAL IT assets for activities that may violate company policies, laws, or cause damage to the company, its clients, or partners. IT assets, such as digital devices, user accounts, email and messaging, internet, networks, applications and services, storage media, are protected at all times. Requirements for the return of assets are also defined in this Standard. Breaches of acceptable use rules are to be investigated and, when deemed necessary, disciplinary actions will be taken proportional to the damage caused. --- # 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/acceptable-user-of-assets.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.