# Securing Firmware Updates With AES Encryption | Interrupt
**URL:** https://community.memfault.com/t/securing-firmware-updates-with-aes-encryption-interrupt/711
**Category:** Blog
**Created:** [August 24, 2023, 2:35am UTC](https://community.memfault.com/t/securing-firmware-updates-with-aes-encryption-interrupt/711 "2023-08-24T02:35:11Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@discobot](https://community.memfault.com/u/discobot)
#### Post date: [August 24, 2023, 2:35am UTC](https://community.memfault.com/t/securing-firmware-updates-with-aes-encryption-interrupt/711/1 "2023-08-24T02:35:11Z")
Connected devices require a secure point-to-point channel to ensure that there is no possibility of exposing important data for the integrity of an embedded system. This is especially true when we talk about over-the-air (OTA) software updates, where the new firmware has a long way to go before reaching its destination and being installed by our bootloader.
* * *
This is a companion discussion topic for the original entry at [https://interrupt.memfault.com/blog/firmware-encryption-with-python](https://interrupt.memfault.com/blog/firmware-encryption-with-python)
---
### Author:  [@discobot](https://community.memfault.com/u/discobot)
#### Post date: [July 10, 2024, 6:57pm UTC](https://community.memfault.com/t/securing-firmware-updates-with-aes-encryption-interrupt/711/3 "2024-07-10T18:57:52Z")