> For the complete documentation index, see [llms.txt](https://connectify.gitbook.io/iot-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://connectify.gitbook.io/iot-protocol/safety-and-traceability.md). # Safety and traceability In addition to its complexity, the IoT also faces major challenges in terms of data security and traceability. Security is critical in the IoT, as the data collected is often sensitive, and the consequences of hacking can be dramatic. Yet many connected objects still present vulnerabilities. The radio protocols used often lack encryption. Object firmware is rarely updated, leaving backdoors. Authentications are weak, allowing access to object networks. On the infrastructure side, the vulnerabilities of centralized cloud servers or insecure databases also express IoT data. The issue of traceability is just as critical. Once collected by objects, it is impossible to guarantee the integrity and origin of the data in transit. Data can be lost, corrupted or modified before it reaches business applications. How can we trust this data if we can't trace its precise path? CONNECTIFY places security and traceability at the heart of its approach, thanks to the contribution of blockchain. --- # 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://connectify.gitbook.io/iot-protocol/safety-and-traceability.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.