> 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/people-security.md).

# People Security

People-related processes (e.g. onboarding, assignment of responsibilities, disciplinary processes, remote working, and offboarding, etc.) must also integrate corporate security controls, in accordance with applicable legislation, as defined in the HR Security Standard.&#x20;

Security responsibilities set out in corporate security policies and standards, are communicated by Corporate Security to the target audience. Contractual agreements must also include responsibilities related to confidentiality, non-disclosure, and intellectual property rights. Security responsibilities that remain after work hours, during remote working, and after the end of collaboration must also be communicated and acknowledged.&#x20;

Security training courses and awareness campaigns are planned with the aim of informing the staff about the requirements and expectations related to security, the main threats and risks, while indicating the best ways to avoid, mitigate and report them to preserve the organization’s security posture.&#x20;

Security courses are mandatory for all employees, with a renewal cycle of 3 years. This training is hosted on the organization’s corporate Learning Management System, managed by a dedicated team. Awareness campaigns are launched through a dedicated platform, on a bimonthly-basis, covering various interactive activities that deal with the main threats and risks (phishing, social media, secure passwords, remote working, etc.), helping staff stay alert, and providing them with ways to deal with such situations.&#x20;

Completion rates are monitored by Corporate Security, striving to achieve set objectives, and following-up whenever necessary to engage staff in fulfilling the activities.


---

# 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/people-security.md?ask=<question>&goal=<user_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.
