how to reconcile high-performance hosting and innovation projects with IT security
summary
Claims that time-to-exploit collapses from weeks to hours, supported by a data project and a daily newsletter tracking real incidents; shows attackers use AI tools like FraudGPT/WarmGPT to automate phishing and scale attacks. Recommends concrete fixes: daily and weekly threat hunting, formal stop-before-deploy process, clear patching cadence with clients, segmentation/zero-trust and DevSecOps pipelines. Notes regulatory gap around “state of tech,” urges small daily documentation habits and a tested incident playbook so uptime loss per hour or day can be quantified and mitigated.
AI-written summary · about
chapters (9)
- 0:00Cyber security challenges
- 2:58Hosting innovation vs security
- 4:44Why outdated systems attract hackers
- 7:33AI and quantum threats
- 9:41AI tools in social engineering
- 12:09DevOps with security integration for developers
- 16:25Threat response and patching
- 18:10Compliance and tech standards
- 19:55Documentation for resilience
related talks
34mSecDevSecOpsSec
57mBuilding a Modern Security Engineering Organization
46mRugged Software Engineering
33mFrom Boardrooms to Polling Places: Securing Critical Infrastructure in 2024
20mCalcifying Crisis Readiness
39mProactive Security, less buzzword, more action
37mPlatform and Security Engineering
27mBridging the Dev-Sec divide: Three tips for agile developers