Security, Fraud, and Compliance
summary
Claims concrete fixes: adopt FIDO authenticators to eliminate shared secrets, move keys out of software into HSM-backed key management, and encrypt in the application layer so compromised apps can’t read sensitive fields. Cites real breaches (Marriott, Voya, Uber 57M, Anthem) and weak ops like leaked GitHub creds and misconfigured S3 (53% observed). Uses numbers: $148 per breached record, 60% of small firms fold after breach. Hardware tokens and cloud config hygiene are shown as essential.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:43About StrongKey
- 2:10Why are there so many breaches
- 3:47What can you do
- 6:06Trivia
- 8:10Breach Costs
- 8:51Regulations
- 9:45Security
- 10:45Technology
- 14:54Outro
related talks
16mInnovation in Authentication and More
26mThe Risky Business of Risk Illiteracy (Sean Juroviesky)
22mSecurity and Risks
10mBe Agile with Security
22mSecurity and Risks
43mUncertain Times: Securing Rails Apps and User Data
30mProfessionals hack people, not systems
58mKeynote: What Got Us Here Wont Get Us There
