> 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/identity-and-access-management.md). # Identity and Access Management The roles and responsibilities related to identity and access management are defined for Corporate Security, System Administrator, System Owners and End Users in the Identity and Access Management Standard. Security requirements for end user accounts, privileged user accounts, break-glass user accounts and service/application accounts are also established, including aspects such as account differentiation, uniqueness, traceability, validity, access rights, lockout policy, deactivation and deletion. Access to corporate resources is only allowed via encrypted communication channels with multi-factor authentication. It also lists the accepted authentication methods, such as password, PIN and biometric factors. The security requirements for password and PIN creation, complexity, expiration and history are defined. Access rights management processes are guided by the "need to know" and "least privilege" principles. Privileged accounts and access rights go through a formal request and approval process. All accounts and access rights are reviewed at least annually to determine if they are still needed or not. --- # 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/identity-and-access-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.