> 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/security-in-it-operations.md). # Security in IT Operations Security requirements related to IT Operations are defined and integrated in processes and technologies to protect information at rest, in transit, and in use, and ensure secure configuration of endpoints, networks, and cloud environments. Endpoints are centrally managed and secured through next-gen malware detection & response, software installation controls, configuration management, and monitoring solutions. Systems are hardened to reduce the attack surface. Strong authentication mechanisms are enforced, including automatic session termination in case of inactivity. Corporate networks are protected by strict security mechanisms (e.g., access control, segregation, secure protocols and connection, firewalls, IDS, IPS, etc.). Suspicious connections are filtered. Access to cloud-based environments and services must comply with the identity and access management security requirements, including MFA. IT resources are regularly backed up to support the continuity of business operations and information security. Systems are be calibrated, maintained, and assessed regularly to ensure their availability, efficiency, and performance. Patch management processes are executed to remediate vulnerabilities. Encryption controls using industry-accepted parameters are defined, and are implemented in accordance with the applicable legislation, considering the criticality of information and systems as well. IT assets are managed and tracked throughout their lifecycle, to ensure they remain up-to-date. --- # 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/security-in-it-operations.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.