Cybersecurity - Protecting the Organisation's Technological Assets
summary
Third-party supplier breaches are rising and language models add new verification risk; companies use third-party supplier breaches tracking, threat modeling and a prioritized risk register to decide what to fix first. Practical controls cited: MDM and disk encryption, least‑privilege access, separate AWS account for backups, CI code scans and monthly vulnerability scans, staged pen tests and architecture reviews. A cyber insurance policy often supplies incident response help; startups start with architecture and external experts, then scale tests as users and budget grow.
AI-written summary · about
chapters (13)
- 0:00Introduction and panel setup
- 3:56Current cyber threats overview
- 6:47Strategic security planning
- 9:32Human factor in cybersecurity
- 13:04Balancing speed and compliance
- 18:21Getting board buy-in for security
- 26:09Incident response strategies
- 28:38Advice for new CTOs in security
- 32:50LLMs and data verification
- 34:58Backup strategies for AWS data
- 36:02Balancing governance and speed
- 39:30Cyber insurance considerations
- 41:13Final thoughts and takeaways
related talks
28mImplementing Critical Cybersecurity Controls in a DevOps Environment
45mProtecting you from you: Misconfiguration-caused breaches
51mImportance of Cyber Diligence in Third Party Risk Management
35mEffective Handling of Third-Party Supplier Incidents
29m3rd-Party Cyber-Risk Mitigation by Using ISO Standards
26mBuilding and Verifying Security Trust in Today’s Complex Tech Stacks ...
48mRemaining Resilient in the Supply Chainpocalypse
51mThe Overlooked Security Risk: 3rd Party Risk Management