> 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/physical-security.md). # Physical Security The physical security requirements, roles and responsibilities, as well as the security areas and controls to be implemented and maintained, are defined in the Physical and Environmental Security Standard. There are four physical security levels, which are based on the type of information, assets, processes, and services managed within office areas. Each security area has adequate physical security controls such as access control systems, CCTV surveillance, and environmental protection to safeguard information and other assets. Access rights to security areas are provided based on the "need to know" and "least privilege" principles, and are reviewed, withdrawn, and audited accordingly. Rules have been defined for issuing, wearing, and returning physical access cards, as well as managing physical keys. Turnstiles, automated doors or other physical barriers are set, and may only be passed with the access cards & rights. Specific instructions to provide visitors with access and accompany them in designated areas have been defined as well. An access log of visitors is kept in each location. Physical security measures are be implemented to prevent or mitigate damage by fire, flood, earthquake, explosion, civil unrest, and other forms of natural or man-made disasters. The standard also covers security aspects regarding external areas, delivery and loading areas, and discontinued offices. --- # 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/physical-security.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.