Replies: 1 comment 5 replies
-
if the main concern here is supply chain attack, agent update is probably the least of your concerns. what about the dozens of 3rd party python packages the software uses, or the hundreds of npm packages? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is not a criticism as such more just thoughts.
I believe and could be wrong, that by default on a new installation, Agent Auto Update is enabled.
My thoughts are that due these coming from the source on Internet, in theory worst case scenario there could be a supply side attack that by whatever means creates a bad agent version and downloads to an entire corporate network where TRMM is running.
Could it be, that code signing helps with this (although in theory still a possibility - 3CX hack good example).
I would suggest at the very least, agent auto update is disabled by default.
But further to this could it be possible to have a more detailed agent update page, that would show the available agent versions (both existing and those new yet to install, when released and so on).
It could go one step further, that agent update page could allow an auto install after X number of days of updated agent release, for example maybe say 60 days, on the thought a delay like that should give time for any exploits to be found if it should happen.
Am I crazy and alone with my thoughts?
Beta Was this translation helpful? Give feedback.
All reactions