@buherator<\/a> @drwhax<\/a> I sometimes advise investors (poor life choices I guess) on how to deal with the increased risk of Mythos & others. And this was the bottom line.<\/p> I don't even need AI specifically to argue for that. The time-to-exploit has been dropping forever. We've built better catalogs and more versatile infrastructure and complex automations. It's very clear that this includes vuln research as well.<\/p> We had this already with static analysis hitting the field. We answered with \"shift left\": Building security into the dev process, since the earlier you do it, the less issues you'll end up with. Every step earlier has more downstream impact.<\/p> We've finally reached the stage where security as part of your design & architecture is not only best practice but becoming a hard requirement. Our automations (including LLMs) pushed us there and we need to deal with the outcome.<\/p> Or should. Because I'm a cynic and I've seen what's happened, I doubt that engineering will follow through with this. I see two paths and we'll move along both, and I don't like either: Acceptance and few centralized Oligopols.<\/p> 1\/2<\/p>","generator":{"id":"tag:gnusocial.jp,2026-09-07:notice-source:ActivityPub","objectType":"application","status_net":{"source_code":"ActivityPub"}},"id":"https:\/\/todon.eu\/users\/ljrk\/statuses\/116997333273553968","object":{"id":"https:\/\/todon.eu\/users\/ljrk\/statuses\/116997333273553968","objectType":"note","content":" @buherator<\/a> @drwhax<\/a> I sometimes advise investors (poor life choices I guess) on how to deal with the increased risk of Mythos & others. And this was the bottom line.<\/p> I don't even need AI specifically to argue for that. The time-to-exploit has been dropping forever. We've built better catalogs and more versatile infrastructure and complex automations. It's very clear that this includes vuln research as well.<\/p> We had this already with static analysis hitting the field. We answered with \"shift left\": Building security into the dev process, since the earlier you do it, the less issues you'll end up with. Every step earlier has more downstream impact.<\/p> We've finally reached the stage where security as part of your design & architecture is not only best practice but becoming a hard requirement. Our automations (including LLMs) pushed us there and we need to deal with the outcome.<\/p> Or should. Because I'm a cynic and I've seen what's happened, I doubt that engineering will follow through with this. I see two paths and we'll move along both, and I don't like either: Acceptance and few centralized Oligopols.<\/p> 1\/2<\/p>","url":"https:\/\/todon.eu\/@ljrk\/116997333273553968","status_net":{"notice_id":null},"inReplyTo":{"objectType":"note","id":"https:\/\/infosec.place\/objects\/cd1478c3-3bf9-4a16-ab0b-9b34c20bad34","url":"https:\/\/infosec.place\/objects\/cd1478c3-3bf9-4a16-ab0b-9b34c20bad34"}},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/person","id":"https:\/\/infosec.exchange\/users\/drwhax"},{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/person","id":"https:\/\/infosec.place\/users\/buherator"},{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:gnusocial.jp,2026-07-28:objectType=thread:nonce=c43a830d39affe5f","notice_info":{"local_id":"12960221","source":"ActivityPub"}},"published":"2026-07-28T11:29:53+00:00","provider":{"objectType":"service","displayName":"GNU social JP","url":"https:\/\/gnusocial.jp\/"},"verb":"post","url":"https:\/\/todon.eu\/@ljrk\/116997333273553968"}],"links":[{"url":"https:\/\/gnusocial.jp\/conversation\/6582967","rel":"alternate","type":"text\/html"}]}