> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/other-features/security-and-compliance/identity-and-access-management.md). # Identity and Access Management Juspay Hyperswitch Identity and Access Management (IAM) is designed to provide a secure, user-friendly, and well-regulated environment. By implementing best practices for authentication and access control, Hyperswitch ensures data confidentiality, operational efficiency, and compliance with global standards. ### Authentication Methodology for Hyperswitch APIs **1. Admin Services Authentication** Administrative services require robust, multi-layered authentication. Access is limited to specific personnel within the Hyperswitch team via an additional API key to maintain backend security. **2. Merchant Authentication** Merchants accessing Hyperswitch APIs benefit from strong authentication mechanisms to safeguard their accounts and transactions. For detailed guidance on merchant authentication, refer to the API documentation. **3. Vault Authentication** The Hyperswitch Vault employs a distributed key management approach. Key custodians must collaborate to initiate the application, ensuring no single individual can independently alter or access the vault. This design prevents unauthorized tampering and enhances the overall security framework. ### Identity and Access Management in AWS **1. User Authentication** Hyperswitch employs Multi-Factor Authentication (MFA) in conjunction with network and device whitelisting to ensure secure user access. **2. Access Controls and Role-Based Access Control (RBAC)** * **Granular Permissions:** Administrative roles are clearly defined with specific permissions, ensuring users only access functionalities necessary for their roles. * **Distributed Access Model:** Hyperswitch employs a distributed model where no individual has complete control over administrative operations. * **Principle of Least Privilege:** Permissions are restricted to essential tasks to mitigate unauthorized access risks. ### Benefits of Hyperswitch IAM 1. **Enhanced Security:** Multi-layered authentication, key management, and RBAC reduce vulnerabilities. 2. **Operational Efficiency:** Clear role definitions and access models ensure streamlined workflows. 3. **Compliance Assurance:** Meets global regulatory requirements, including PCI DSS and ISO 27001 standards. 4. **User Trust:** By minimizing risks and safeguarding data, Hyperswitch fosters confidence among merchants and partners. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hyperswitch.io/other-features/security-and-compliance/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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.