4 ms·
Some years ago I was consulting for a new credit union; they found their implementation choices very constrained by the NCUA (regulators). I had to walk away
by h2odragon 3y ago
Some years ago I was consulting for a new credit union; they found their implementation choices very constrained by the NCUA (regulators).
I had to walk away from that job. I told them I could not take responsibility for the stability and security of their systems with the constraints they required.
Was a horror show. No logs. Public IPs for the DB server, for vendor remote access. "We don't know what our originating networks might be, so no firewalls on that." "systems" networks and "public" network is too confusing, we need to be able to access our porn from any terminal, alongside client financial data.
That place was not representative of the industry, I think; but I still hope that the situation improved.
- ru552 3y agoThis is either false or just a shit show of a business. I’ve done work with several credit unions. They operate their IT just like any other business. The NCUA doesn’t make IT decisions for them.
- h2odragon 3y agoThis was a shit show of a business, fer sure. I only met one actual NCUA person myself, he was not technical and was not the person I had needed to talk to. Its entirely possible (likely) the people I was dealing with were shifting blame to NCUA where they thought they could. To be clear: the "shared terminals" thing was not NCUA, that was the dipskiff boss's decision. My meeting with the regulator was an attempt to get that one changed.