I'm exploring the idea of starting up a bank and am still in the process of learning how and how they really work (so I'm not sure this is the right question to ask, but I'll try anyway). I could imagine online/mobile banking as one of the priority features because that'll be my USP (our local banks suck at those, really. I want to make software that'll eliminate the need for people to personally go to banks for transactions other than depositing money). That said, I'm thinking of using AWS for the back-end and storage of pretty much all of the data the bank will be processing--customer info, transactions, balances, etc. Is that safe? Or should I just go with in-house servers which require a huge upfront investment?ADD: My country's near the equator, almost 100 Fahrenheit everyday. Not so sure having our own data center here is a good idea.
[+] [-] dsl|13 years ago|reply
As far as your business idea, you should check out simple.com. They have been working on the problem for years and have just barely managed to cut enough red tape to provide a not terrible user experience for a handful of tasks.
Have a full accounting and audit of every VoIP device, VPN device, wireless device, switch, router, modem, firewall, and proxy server connected to the network.
Demonstrate physical access controls for employees, vendors, and anyone else who may have access your equipment.
Every single person with physical access to customer information devices must have a 10-year criminal background check performed (this is actually a federal law that applies to the Finance, public education, public transportation, etc industries).
Formal configuration and patch management procedures for all devices (including upstream routers and switches).
Diagrams of physical and logical network topologies.
The Fair and Accurate Credit Transactions Act of 2003 requires physical destruction of devices storing customer data.
Reporting of all physical security incidents to FDIC IT examination.
[+] [-] mattquiros|13 years ago|reply
[+] [-] mikiem|13 years ago|reply
[+] [-] t0|13 years ago|reply
[+] [-] brudgers|13 years ago|reply
Solution option A = Start a bank and create infrastructure to offer better online service
Solution option B = Create infrastructure to offer better online service and sell it to banks
Which one scales?
[+] [-] dear|13 years ago|reply
[+] [-] mattquiros|13 years ago|reply
[+] [-] lifeisstillgood|13 years ago|reply
On top of that, it is highly highly unlikely that the range of software a bank uses will install cleanly on say Ubuntu 12.04.
And the reason mobile sucks for almost all banks is
A) their back end software is twenty years old and was written before the Internet was even considered - the APIs are mostly screenscrapers
B) mobile security is hard
[+] [-] mattquiros|13 years ago|reply
Totally agree with A. What do you mean by B though? As in secure wireless transactions and maybe the crackability of Android phones?
*update, just started reading on mobile security now
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] stray|13 years ago|reply
[+] [-] mattquiros|13 years ago|reply