When using the SimpleUpdate action for FW updates with SCP, how can we prevent MITM attacks? We thought of transferring the server fingerprint in addition to server IP, username and password, but we haven't found a suitable field for that except for "RemoteServerCertificates".
Any suggestions or insights on these matter would be most welcome.
Without having any sort of SSH public key installation, you're correct in that we don't have a standard method of preventing man in the middle attacks. Within the "AggregationSource" schema, we did add TrustedPublicHostKeys, and it seems reasonable to me to add something similar to UpdateService for this case.