top of page

Everyone Is Asking Why the Breaches Keep Happening. We Put the Question to the Co-Founder of HaqFre.

11 minutes ago
5 min read

A Capitol Times Media interview. Anil, Founder of Capitol Times Media, in conversation with Scott, Co-Founder of HaqFre.


Scott's opening statement, delivered before the questions began:


What if the breaches and failures recently are not a run of bad luck, but a property of the design?


Not a flaw in anyone's code. A property of the architecture itself, of how the whole system decides who belongs and who doesn't. A question the internet answered badly, decades ago, and then stopped asking. Now stack the what ifs. What if the largest security event in digital history is already on the calendar, not an attack, not a breakthrough, but something media coverage keeps filing under compliance? What if that event forces the system to finally answer the question it never really answered, not someday, but within the same few years, whether anyone is ready or not? And what if the ones quietly assembling that answer are not who everyone assumes will inherit the future? I've spent the last 6 years tracing that chain, and it leads somewhere, almost no roadmap goes. The full argument arrives soon. The short version: the thing everyone thinks is the prize never was, and for a few years, the real prize is still on the table.


On November 16, 2026, visitors to some of the busiest websites on Earth, the BBC, Zoom, CNN, HSBC, Equifax, IKEA, spent the day loading hostile code. Not one of those organizations was breached.


The code arrived inside a script their pages already trusted, served from a legitimate domain with a valid certificate: a supply-chain compromise of the Optimized platform that reached at least 178 organizations in a single day, swapping crypto wallet addresses, skimming payment cards, and stealing cookies from millions of visitors. Everything at the door checked out.


The door never asked the only question that mattered. It was the third week in a row of national-scale technology failures, a four-hour FAA ground stop, government websites across Europe taken offline over the most severe vulnerabilities AI has ever discovered, and the questions had stopped being technical.


Why does this keep happening? Why does record spending on security keep producing record failures? Is anyone actually working on an answer, or is everyone just patching? There was one obvious person to ask. Scott, co-founder of HaqFre (haqfre.com), has spent six years on a premise most of the industry has not yet confronted: that some of what we keep calling "breaches" are not break-ins at all. They are symptoms of design. Capitol Times Media put the questions to him directly. What follows is a condensed version of that conversation.



Anil: Let's start with the uncomfortable question. The industry has never spent more on security, and the failures keep coming anyway. What's going on?


Scott: The first thing to understand is that most of the discussion treats each incident as a separate story, a bug, a lapse, a bad actor. An optimized attack is a perfect example of why that framing fails. Take a step back and a pattern shows up. The system decides who belongs and who doesn't at a handful of chokepoints, and it makes those decisions the same way it made them decades ago: by pattern recognition. By resemblance. That script came from a trusted domain, with a valid certificate, from a vendor the site had done business with for years, so every gate on the internet waved it through. Nobody was standing at the door asking the three questions that actually matter: who is this, on whose orders, and is it intact? The system guesses from the silhouette. Attackers don't defeat that gate. They dress for it.


Anil: You're saying the failures aren't a run of bad luck.


Scott: Correct. A run of bad luck produces scattered failures. What we're seeing is structural. The perimeter was designed for a web where you could tell friend from stranger by how they looked, where a valid certificate and a familiar domain meant something. That assumption is now wrong on both ends. The attackers learned to wear exactly what the guards are trained to trust, and the legitimate new visitors, the automated ones doing real work on our behalf, look like nothing the gate has ever seen. So, the gate either waves through things it shouldn’t or interrogates things it should welcome. Both are failures. Only one of them makes the news each week.


Anil: So, if it's architectural, patching harder won't fix it. What does the fix look like?


Scott: It looks like replacing the guess with an answer. Instead of asking "does this look trustworthy?", a door that asks, "can you prove who you are, who authorized you, and that you haven't been tampered with?" and gets back something verifiable, not something estimable. Had that existed on November 16, the attack dies at load time: the injected code would have failed its provenance check the instant it stopped matching what its maker actually shipped. That answer exists as a design pattern; it's a chain of attestations, each one signed by a different authority that has real standing to vouch. None of the individual pieces are science fiction. The composition is what's missing.


Anil: Is anyone building this?


Scott: Parts of it, quietly, in places most people aren't watching. And there's a reason the timing matters now more than usual: the entire cryptographic foundation of the internet is scheduled for a once-in-a-generation replacement over the next several years, a mandate, not an option. When every key, certificate, and credential on Earth gets re-issued anyway, the door gets rebuilt whether anyone planned to or not. The question is only who sets the design.


Anil: You said, "most people aren't watching." Who's building it?


Scott: I'll go further than that, it's not who the headlines assume. It isn't the browser makers, and it isn't the AI labs. The infrastructure that has spent decades solving the harder version of the same problem: how do strangers exchange something of value and both walk away trusting the counter-party? Wherever that problem was solved, the answer was verifiable identity plus accountability. The door on the rest of the internet is being rebuilt by people who have already built that door once.


Anil: People hearing this will ask: what do you have, and when do we see it?


Scott: The Answer. To Be Determined. I have offered to meet with President Trump and will introduce the answer to who he advises me to meet with.


Anil: That's a confident name. Do others have the Answer also?


Scott: It's a truthful one. We didn't set out to build a product category. We set out to answer the question the internet never answered, who is this, on whose orders, in what condition, and what emerged is a system that does exactly that. Everything we've discussed today, from the optimized attack to the re-issuance window, is the same problem wearing different costumes. We named it what it is. The answer to your second question is "not likely or Band-Aid approach"


Anil: Last question. If you're right that this is architectural, what should the average person watching these headlines take away?


Scott: Two things. First, the failures you keep reading about are connected, not by a villain, but by a design decision made decades ago that nobody has been forced to revisit. That's about to change, and change is an opportunity as much as a warning. Second, watch who ends up holding the pen that certifies identity and authorization in the new design. Whoever signs the permission slips writes the rules of the next twenty years. That decision is being shaped right now, in windows most of the public never sees. My job is to make sure it gets shaped correctly.

READ NEXT

Heading 2

Disclaimer:
 

The views and opinions expressed in the articles or Interviews published in this magazine are solely those of the respective authors and do not necessarily reflect the official policy or position of the Capitol Times magazine or Capitol Times Media , its editors, or its staff. The authors are solely responsible for the content of their articles. The magazine strives to provide a platform for diverse voices and opinions, and we value the principle of free expression. The magazine assumes no responsibility or liability for any errors or omissions in the content of the articles. In no event shall the Capitol Times magazine or Capitol Times Media be liable for any special, direct, indirect, or incidental damages. Furthermore, the inclusion of advertisements or sponsored content in Capitol Times magazine does not constitute an endorsement or guarantee of the products, services, or views promoted by the advertisers. Readers are encouraged to conduct their own research and exercise caution when making decisions based on advertisements or sponsored content featured in this publication.

Thank you for reading and engaging with our publication. Your feedback is valuable to us as we continue to provide a platform for thought-provoking content and diverse perspectives.

 

Capitol Times Media is a privately owned and independently operated media that publish Capitol Times Magazine. It is not affiliated with, endorsed by, or connected to the United States government, the U.S. Capitol, Congress, or any federal, state, or local government agency. Content published by Capitol Times Magazine includes both editorial content and sponsored or paid content.


© 2026 by Capitol Times Media LLC - Privacy Policy

bottom of page