> For the complete documentation index, see [llms.txt](https://shiro.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shiro.gitbook.io/docs/security-protocols/security-infrastructure.md). # Security Infrastructure ### Secure Architecture The Shiro platform is built on a foundation of secure architecture designed to minimize risks and protect against potential threats. ### Key Components * **Network Security:** Utilizing firewalls and intrusion detection systems to monitor and protect data flow within the network. * **Encryption:** All sensitive data, such as transaction details and personal information, is encrypted using advanced cryptographic techniques to prevent unauthorized access. * **Access Controls:** Implementing role-based access controls (RBAC) to ensure that only authorized personnel have access to critical parts of the infrastructure. * **Redundancy and Backup:** Regular backups and redundant systems are in place to ensure that player data and assets can be recovered and protected in case of a hardware failure or cyber attack. ### Continuous Monitoring and Incident Response * **Monitoring:** The Shiro platform employs continuous monitoring tools to detect and alert on potential security threats in real time. * **Incident Response:** A well-defined incident response plan is ready to be executed in case a security breach occurs. This plan includes steps for containment, investigation, mitigation, and communication with users about the issue and resolution. --- # 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://shiro.gitbook.io/docs/security-protocols/security-infrastructure.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.