European Cybersecurity Regulations who's who
summary
A rapid map of current EU rules and concrete mandates: GDPR starts privacy rules but shows gaps, NIS 2 treats cyber incidents as societal risk, CRA/product liability force vendors to provide security updates and accountability, and proposed AI rules carve out a private LLM requirement for incident handling (never send active-incident data to cloud AI). Key claims: digital attacks scale to billions of phishing messages at near-zero cost, so regulators enforce risk-based obligations, mandatory patching and vendor liability, and open source tooling as a cost-effective way to comply.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:33Why cybersecurity regulation is complex
- 2:37Key European cybersecurity regulations overview
- 5:30NIS 2 and societal impact of cybercrime
- 8:24DORA and product liability in digital safety
- 9:28Organizational regulations and AI protection
- 11:42AI regulation challenges and risk-based approach
- 12:48Protecting society through software safety
- 13:11Italy’s role and open source opportunities
related talks
01h 12mCYBERSECURITY FOR EUROPE: FOSTERING RIGHTS THROUGH TECHNOLOGY
01h 12mThe Transformation of EU Cybersecurity Law
01h 09mAligning Cybersecurity Information Sharing with the European Data Protection Framework
22mEU Cyber Resilience Act - A Product Owner’s Approach
01h 05mDigital Sovereignty in Wartime: Legal and Cybersecurity Considerations
44mThey're coming to regulate you!
59mMerging Security and Compliance: Perspectives on Emerging Regulations and Best Practices
27mEU Cyber Resilience Act: What Every Manufacturer Needs to Know