298
edits
RidgeRun Platform Security Manual/Platform Security/OTA: Difference between revisions
RidgeRun Platform Security Manual/Platform Security/OTA (view source)
Revision as of 23:05, 27 January 2025
, 27 January→Over-the-Air Updates
No edit summary |
|||
| Line 17: | Line 17: | ||
As updating a system over-the-air makes the process easier and faster, it allows developers to maintain their system up to date with the latest version of their code to ensure the correct functionality and integrity of the product. This becomes specially relevant if '''bugs and vulnerabilities''' are discovered after the product has been released, so as soon as an updated version of the software with the corresponding fixes is ready, it can be shipped to all units remotely without having direct access to the device, '''minimizing the risk''' of the security vulnerabilities being exploited. | As updating a system over-the-air makes the process easier and faster, it allows developers to maintain their system up to date with the latest version of their code to ensure the correct functionality and integrity of the product. This becomes specially relevant if '''bugs and vulnerabilities''' are discovered after the product has been released, so as soon as an updated version of the software with the corresponding fixes is ready, it can be shipped to all units remotely without having direct access to the device, '''minimizing the risk''' of the security vulnerabilities being exploited. | ||
<br> | |||
While OTA provides a great solution to the problem of updating remote devices, there are aspects that developers need to keep in mind when implementing an OTA solution. For example, if a device is being updated remotely and the connection to the network is interrupted mid update, this could leave the device in an unusable state. The more important aspects to consider are the following: | |||
* Reliability: | |||
* Security: | |||
* Resource Constraints: | |||
* Version Compatibility: | |||
<noinclude> | <noinclude> | ||