# How to prevent Last-Mile Manipulation to Flows

**URL:** <https://discourse.nodered.org/t/how-to-prevent-last-mile-manipulation-to-flows/100546>\
**Category:** General\
**Tags:** security\
**Created:** [13 March 2026 04:40 UTC](https://discourse.nodered.org/t/how-to-prevent-last-mile-manipulation-to-flows/100546 "2026-03-13T04:40:40Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [18 March 2026 09:40 UTC](https://discourse.nodered.org/t/how-to-prevent-last-mile-manipulation-to-flows/100546/9 "2026-03-18T09:40:59Z")

</div>

I think what @AllanOricil describes here is really relevant. If you use NR in production I can image the tool can help in the verification process, especially if shared nodes are being used (for free) in the customer delivery

> [@NRG Sentinel, runtime security for Node-RED](https://discourse.nodered.org/t/nrg-sentinel-runtime-security-for-node-red/100515/32):
>
> In what circumstances would my Node-red installations benefit from this additional runtime security? Who are the attackers you have protected from - my own staff / family , Internet based users of my dashboard, authorised but malicious logged-in editors?

---

_[View the full topic](https://discourse.nodered.org/t/how-to-prevent-last-mile-manipulation-to-flows/100546)._