Posted by:
admin
15 years, 10 months ago
and information security.
I just finished reading the Undercover Economist by Tim Hartford. Great Read. He has a chapter on externality charges. While he doesn't use the term, he's talking about Lexus Lanes - toll lanes that charge a fee for access - think a paid HOV lane.
The Safety Spike (TM) is my interpretation of the economic idea of removing a moral hazzard. Economists might argue the safety belts and airbags increase the likelihood of accidents. Indeed, accidents have increased - but fatalities have not. To reduce accidents, an economist suggested installing a sharp spike in the steering column pointed at the driver. (The Safety Spike is my term for it - trademark is pending once I get around to filing it.)
I was hoping to apply these ideas to information security, in particular vis-a-vis the externalities of unpatched servers and desktop PCs on the Internet and online banking. Some pundits have suggested making the banks responsible for online fraud. If we do that, what incentive do users have to buy anti-spyware? Attackers are already using SSL-session hijackers. While transaction authentication could potentially solve this, a better solution for spyware exists, it's called anti-spyware. People just need to be incented to use it.
Could you create a Lexus Lane for users that have anti-spyware? Maybe. The problem is that you can't trust the user's PC. How about this: the anti-spyware company sends the bank a history of user's updates with some type of trust score based on how long the user has been a customer and how frequent the user updates. I would suggest that the user gets a discount on the anti-spyware software to ease the cost. I would think that an anti-spyware company would jump at that.
In general, I think the Lexus Lane is preferable to spreading the liability across all the banking customers, which is what making the banks liable would do. Users that don't have third-party validated security should be charged for banking online.
Share on Twitter Share on FacebookRecent Posts
- Blast-RADIUS attack
- The latest WiKID version includes an SBOM
- WiKID 6 is released!
- Log4j CVE-2021-44228
- Questions about 2FA for AD admins
Archive
2024
2022
- December (1)
2021
2019
2018
2017
2016
2015
2014
- December (2)
- November (3)
- October (3)
- September (5)
- August (4)
- July (5)
- June (5)
- May (2)
- April (2)
- March (2)
- February (3)
- January (1)
2013
2012
- December (1)
- November (1)
- October (5)
- September (1)
- August (1)
- June (2)
- May (2)
- April (1)
- March (2)
- February (3)
- January (1)
2011
2010
- December (2)
- November (3)
- October (3)
- September (4)
- August (1)
- July (1)
- June (3)
- May (3)
- April (1)
- March (1)
- February (6)
- January (3)
2009
- December (4)
- November (1)
- October (3)
- September (3)
- August (2)
- July (5)
- June (6)
- May (8)
- April (7)
- March (6)
- February (4)
- January (427)
2008
- December (1)
Categories
- PCI-DSS (2)
- Two-factor authentication (3)
Tags
- wireless-cellular-mobile-devices (7)
- Two-factor authentication (10)
- Wireless, cellular, mobile devices (6)
- NPS (1)
- Phishing and Fraud (111)
- Active Directory (1)
- pam-radius (3)
- privileged access (2)
- Cloud Security (10)
- Mutual Authentication (60)
- Web Application Authentication (1)
- Authentication Attacks (99)
- pci (50)
- Security and Economics (97)
- WiKID (133)
- pam (2)
- VPN (1)
- Installation (2)
- RADIUS Server (1)
- Open Source (64)
- Tutorial (2)
- Strong Authentication (35)
- Information Security (137)
- Transaction Authentication (13)
- Miscellaneous (100)
- Linux (2)
- transaction-authentication (6)
- Two Factor Authentication (254)