[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-ai-agents-auto-patch-enterprise-networks-after-attacks":10,"sections":34},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":22,"persona_id":22,"persona_name":22,"section":24,"tags":25,"sources":29,"feedback":33,"feedback_at":22,"cost_usd":33,"total_tokens":33},2988,"ai-agents-auto-patch-enterprise-networks-after-attacks","AI Agents Auto-Patch Enterprise Networks After Attacks","A new multi-agent framework called COHORT cuts the weeks-long manual process of hardening networks after a cyberattack down to an automated pipeline.","An academic framework automates one of enterprise security's most tedious jobs: figuring out how to block a known attacker without breaking the network they were in.\n\nCOHORT uses a team of large language model agents to propose, implement, and stress-test network mitigations — firewall rules, switch configs, router changes — on a high-fidelity emulator running real vendor firmware rather than a toy simulation. The key test is what the researchers call offensive replay: after applying a candidate fix, the system re-runs the original attack and checks whether it still works. A separate check confirms the mitigation didn't accidentally kill legitimate traffic. The framework stacks approved mitigations cumulatively to catch compound effects. Across three network topologies and four attack types — ransomware, lateral movement, DNS exfiltration, and data theft — 46.7% of generated mitigations blocked the attack and kept the network functional, a rate 4.4 times higher than a single-agent baseline.\n\nThe gap between detecting a breach and actually fixing the configuration that allowed it is where most enterprise security teams bleed time and money. Automating that loop with verifiable, replay-tested mitigations — not just suggested ones — is a meaningful step toward closing it. It also matters that the emulator runs real vendor firmware rather than abstracted proxies, which has historically been where simulation-based security research falls apart.\n\nThe 46.7% success rate sounds modest until you remember the alternative is weeks of expert work per incident; the harder question is how well the emulated topology reflects the target network in production.","[\"security\",\"ai\",\"enterprise\",\"networking\"]","2026-06-30T04:00:00.000Z","2026-06-30T16:53:27.762Z","2026-06-30T16:53:30.742Z","published",null,[],"security",[24,26,27,28],"ai","enterprise","networking",[30],{"name":31,"url":32},"arXiv cs.AI","https:\u002F\u002Farxiv.org\u002Fabs\u002F2606.30479",0,{"sections":35},[36,40,44,49,54,59,64,69,74,79,84,88,93,98],{"name":37,"slug":26,"count":38,"latest_published_at":39},"AI",2590,"2026-07-16T04:00:00.000Z",{"name":41,"slug":24,"count":42,"latest_published_at":43},"Security",294,"2026-07-15T19:59:48.000Z",{"name":45,"slug":46,"count":47,"latest_published_at":48},"Deals","deals",179,"2026-06-29T20:02:07.000Z",{"name":50,"slug":51,"count":52,"latest_published_at":53},"Policy","policy",158,"2026-07-16T00:02:48.000Z",{"name":55,"slug":56,"count":57,"latest_published_at":58},"Hardware","hardware",122,"2026-07-14T19:46:26.000Z",{"name":60,"slug":61,"count":62,"latest_published_at":63},"Consumer Tech","consumer-tech",93,"2026-07-13T13:20:48.000Z",{"name":65,"slug":66,"count":67,"latest_published_at":68},"Software","software",70,"2026-07-13T19:52:25.000Z",{"name":70,"slug":71,"count":72,"latest_published_at":73},"Science","science",66,"2026-07-10T10:29:37.000Z",{"name":75,"slug":76,"count":77,"latest_published_at":78},"Dev Tools","dev-tools",59,"2026-07-07T04:00:00.000Z",{"name":80,"slug":81,"count":82,"latest_published_at":83},"Gaming","gaming",41,"2026-07-09T04:00:00.000Z",{"name":85,"slug":86,"count":82,"latest_published_at":87},"Startups","startups","2026-06-29T20:55:50.000Z",{"name":89,"slug":90,"count":91,"latest_published_at":92},"General","general",29,"2026-07-10T22:28:58.000Z",{"name":94,"slug":95,"count":96,"latest_published_at":97},"Reviews","reviews",20,"2026-06-24T12:00:01.000Z",{"name":99,"slug":100,"count":101,"latest_published_at":102},"How-To","how-to",6,"2026-06-16T09:00:00.000Z"]