







Securing our future: July 2026 progress report on Microsoft's Secure Future Initiative | Microsoft Security Blog
Microsoft’s latest Secure Future Initiative report outlines progress on secure foundations, AI-powered defense, and future-ready cybersecurity.

Developer Ecosystems for Software Safety
How to design and implement information systems so they are safe and secure is a complex topic. Both high-level design principles and implementation guidance for software safety and security are well established and broadly accepted. For example, Jerome Saltzer and Michael Schroeder’s seminal overview of principles of secure design was published almost 50 years ago,10 and various community and governmental bodies have published comprehensive best practices about how to avoid common software weaknesses—for example, Common Weakness Enumeration (CWE)a and Open Worldwide Application Security Project (OWASP) Cheat Sheet Series.b

Nicholas Carlini - Black-hat LLMs | [un]prompted 2026
Microsoft Build 2026: Securing code, agents, and models across the development lifecycle | Microsoft Security Blog
Discover how Microsoft enables fast, secure AI development with MDASH and new security capabilities.


The future of software In the limit, software won't mean anything anymore. But in the interim period we'll wander through an increasingly odd "in-between" age for software. This… | Thomas Wolf | 63 comments
The future of software In the limit, software won't mean anything anymore. But in the interim period we'll wander through an increasingly odd "in-between" age for software. This transition period will be defined by three new precepts. Everflux software - instead of stepping from release to release, software now evolves continuously. Software creation has broken the sound barrier of our own keystrokes, and every model release pushes it faster. There is no reason to wait weeks or months for the next release when a single company merges over 30,000 code changes a day. Bug and vulnerability fixes need to ship quickly and continuously. And every piece of software sits in a lattice of dependencies, each one now shipping at a blistering pace. Translucent sources – A new territory has opened between open source and closed source. Today Claude will happily pick apart any Electron app, and any binary shipped with debug symbols has become a reverse-engineering playground for LLMs. In other words, much so-called closed-source software is now open source in all but name, and keeping code closed makes less and less sense. Even the notion of IP and copyright is breaking in software. I'm writing this text on a personal text editor I prompted Claude to vibe-code from a few videos of people demoing editor features they liked. A mere description of the interface is increasingly enough for an LLM to rebuild the internals. Software IP seems to be dissolving like cotton candy in a raccoon's paws. Bespoke features - Now that all software is open source, nothing prevents us from modifying everything. And personalization is just one prompt and a couple million tokens away, so there is absolutely no reason anymore to wait for someone else to add this feature you want. Everyone becomes their own product manager. Want a search box, an API bridge, a custom button? It's a couple of minutes away. A major challenge appears when bespoke features crash into our first tenet: everflux software. I could fork it for good to add my search box, but I'd lose all future benefit from the software creator. How do you personalize software that was never meant to be personalized, without shouldering all of its future maintenance? Merge conflicts won't be the exception anymore; they'll be a constant of everflux software. Agents will rebase our personal features onto each new release overnight, and software will look less like a product and more like a living species, evolving through constant mutation. Substack post: https://lnkd.in/dw2Re-kA Image: M.C. Escher, Metamorphosis II, November 1939 - March 1940 | 63 comments on LinkedIn
Path to Astra: critical capabilities and frontier safeguards
Astra is the first OpenAI model to meet the Critical cybersecurity capability threshold under the Preparedness Framework, with stronger safeguards for release.

Today's PHP Security Release, and How We're Strengthening PHP Security
Describing the story behind how critical security vulnerabilities were found and fixed.

Today's PHP Security Release, and How We're Strengthening PHP Security
Describing the story behind how critical security vulnerabilities were found and fixed.

Opinion | Internet Hacking Is About to Get Much Worse (Published 2018)
We can no longer leave online security to the market.

imput
We develop private, efficient, and respectful software. We also do security research, reverse engineering, and develop network services.
Advanced web security topics
(Updated 22 May 2020) This post discusses web security issues that I come across – so far thankfully mostly by reading about them. It is a work in progress which I’ll keep updating. The…


Rethinking security for the age of AI - The Official Microsoft Blog
Editor’s note: Updates with additional details on the model’s crash score. Why security needs a new cyber stack — Introducing Project Perception The physics of cybersecurity are changing. Autonomous systems can now reason, adapt and operate continuously. At the same time, the cost of offense is falling, while the volume, velocity and complexity of what...


Top AI Security Incidents of 2025 Revealed | Adversa AI
Discover how AI systems are being hacked in the wild — from prompt injection to agent abuse — with real breaches, lessons, and defenses in Adversa AI’s 2025 report.
