This option, the Local iFrame Login Form, is the most insecure option. All data is transferred between the vendor and the web server multiple times, opening the customer to packet sniffing attacks that we can’t stop because it happens in between the vendor and the website. This would open Community Bank to liability if customer data was compromised.
Local iFrame Login Form
This option is a sample login form using code copied directly from the vendor’s login page that they host on their website. If it works as intended, this method would only be considered insecure in the passing of the username and password to the vendor website. If compromised, these can be changed easily. This is your middle-security option with minimal liability in the event of a breach.
This option is simply a dressed-up button that will bring the customer to the vendor-hosted online banking login form. Although not entirely what you have expressed that you want, I felt the need to present this option as it is the most secure and liability-free option that we can implement.
