ACM Public Policy

7/ ACM ETPC supports the overall direction — digital identity inclusion, post-quantum requirements, ransomware data coordination. But resilience requires specificity, not just intent. Full response: acm.org/public-policy/…

6/ Broader fixes needed: clearer definitions for "sensitive information," standardized reporting structures to end duplicative questionnaires, and firm deadlines for entities entering scope.

Removing small DNS providers from EU cybersecurity law sounds like smart deregulation. @acmpolicy's Europe Tech Policy Committee warns it could create a "security vacuum." New consultation response 🧵 acm.org/public-policy/…

7/ The goal of EU digital policy must be agility — not reduced visibility. A resilient Europe needs a regulatory framework as technically adaptive as the models it governs. @AISI_UK @enisa_eu @Europarl_EN @EUAIOffice Full analysis: acm.org/public-policy/…

6/ ACM ETPC recommends a Risk-Triggered Continuous Technical Assurance framework: automated telemetry reporting to the EU AI Office — activated only when capability benchmarks cross defined safety thresholds.

AI systems can now autonomously complete 32-step enterprise cyberattacks. @acmpolicy's Europe Tech Policy Committee warns EU oversight may not be keeping pace. New analysis 🧵 acm.org/public-policy/…

Read ACM's full TechBrief on vibe coding—what it means for software quality, security, the workforce, and what organizations need to do now: [link] @acmpolicy #VibeCoding #AIPolicy dl.acm.org/doi/full/10.11…

🔧 ACM's call: organizations must compensate with governance and technical checks. Formal verification methods and AI models tuned for security vulnerability detection are key to making vibe coding safe and cost-effective at scale. #ResponsibleAI

Vibe coding—using AI to write software from plain-language prompts—is reshaping software development. ACM's new TechBrief breaks down the real benefits and systemic risks. 🧵 [dl.acm.org/doi/full/10.11… ] #VibeCoding #AIPolicy