> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/documentation/software/cybersecurity-and-secure-updates.md).

# Cybersecurity and Secure Updates

A connected mobility platform must treat cybersecurity failures as potential safety failures.

## Threat surfaces

* Firmware and software update channels
* BLE, Wi-Fi, mobile, cloud, and local APIs
* Debug/programming interfaces
* Repository workflows and release artifacts
* Credentials, signing keys, and configuration files
* Logs, images, audio, maps, and caregiver data
* Physical access to removable storage and connectors

## Controls

* Signed and authenticated releases
* Secure boot and rollback protection where supported
* A/B or recoverable update strategy
* Least-privilege services and disabled unused interfaces
* Unique device identity without exposed secrets
* Encrypted transport for sensitive communication
* Input validation, rate limits, replay protection, and timeouts
* Dependency scanning and reproducible builds
* Secret rotation and owner-controlled deployment access

An update is deferred during unsafe motion states. Failed boot, health check, configuration migration, or sensor validation triggers rollback and a visible fault.


---

# 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://carec.gitbook.io/carec-docs/documentation/software/cybersecurity-and-secure-updates.md?ask=<question>&goal=<endgoal>
```

`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.
