Safety & Security

Block is building AI-powered security on OpenAI technology

Block says it is building AI-powered security with OpenAI, with its security team investigating threats faster and proposing patches in minutes.

By Sophie Lindqvist3 min read

Updated

Why it matters

  • Block is building AI-powered security tooling with OpenAI technology.
  • Block's security team investigates threats faster with the AI tooling.
  • Patch proposals that previously took longer now arrive in minutes.
  • The deployment covers a major payments company operating Square and Cash App infrastructure.

Block is using OpenAI's technology to run AI-powered security, and the company says the results show up in its threat-response times: its security team now investigates threats faster and proposes patches in minutes, not days.

That single shift matters more than it might sound. Block — the company behind Square and Cash App, co-founded by Jack Dorsey — operates payment infrastructure that handles real money for millions of users. Security work at that scale is normally a bottleneck. If patch proposals that once took a security engineer hours or days now arrive in minutes, the economics of defense change.

What is Block actually doing?

According to the source material, the arrangement is straightforward: Block is building AI-powered security tooling with OpenAI. Its security team uses that tooling to investigate threats and to draft patch proposals.

The two concrete claims Block makes are:

  • Threat investigations run faster than before.
  • Patch proposals arrive in minutes.

The mechanism is not mysterious. Large language models are strong at a narrow set of tasks: reading code, summarizing logs, correlating signals across systems, and drafting fixes. Security operations are full of exactly that kind of work. An analyst who used to read alerts line by line can hand the triage to a model and review its output.

That's why the claim is plausible even though it's thin on numbers. The source doesn't publish benchmark figures, incident counts, or pricing for the OpenAI deployment. What it does establish is the direction: a major fintech company has moved from experimenting with AI in security to building production tooling on it.

Takeaway: Block is treating AI as security infrastructure, not a demo.

Why does this matter for the market?

Block's move lands in a market where AI-assisted security is becoming table stakes. Vendors across the industry are bolting language models onto threat detection, and buyers increasingly expect it. When a company of Block's size builds directly with OpenAI rather than only buying packaged tools, that says something about where the value sits — in custom workflows built on top of foundation models.

There's a second layer. OpenAI's enterprise business grows through exactly these deployments: a named customer using its models for internal, security-critical work is a stronger signal than a marketing partnership. For OpenAI, a fintech anchor use case helps counter the argument that foundation models are only good for chatbots and content.

And for the security profession, the stakes are concrete. If patch proposals land in minutes, the unit of work shifts from "one analyst, one ticket" to "one analyst reviewing many AI-drafted fixes." That changes staffing, training, and how teams measure themselves.

Takeaway: the story is less about Block's tooling than about who builds AI security and who buys it.

What are the limits of the claim?

It's worth being precise about what Block has and hasn't said. The source reports faster investigations and minute-scale patch proposals. It does not report incident reduction numbers, false-positive rates, or how much human review each AI-drafted patch requires.

That last gap is the important one. A patch proposal is not a deployed patch. Someone still has to validate that a machine-suggested fix doesn't break production systems — especially in payments, where a bad patch can be as damaging as the vulnerability it closes. The claim "proposes patches in minutes" tells us about drafting speed, not about the full path to deployment.

Takeaway: the bottleneck may have moved from writing fixes to approving them.

What comes next?

The source doesn't detail a roadmap, but the trajectory it describes points one way. If AI-assisted investigation and patch drafting hold up at Block's scale, expect the pattern to spread: more financial-technology companies building security tooling directly on foundation models, and more pressure on vendors to justify packaged products against homegrown ones.

For now, Block has put a number-free but meaningful marker down — minutes instead of longer cycles — and the industry will read it as a data point in the argument that AI belongs inside the security operations center.

Source: OpenAI News

Share this article:

More from Sophie Lindqvist

Sophie Lindqvist

Show full bio

Staff writer covering regulation, policy and their impact on artificial intelligence and machine learning at AI In Context.

265 articles

Related articles

  1. OpenAI's Daybreak Launches Patch the Planet for Open-Source Security
  2. OpenAI Commits $1 Billion to Protect Essential Services With AI
  3. OpenAI cyber capability scores jump from 27% to 76% in three months
  4. OpenAI and Paradigm Launch EVMbench for Smart Contract Security
  5. OpenAI Rolls Out GPT-5.4-Cyber to Vetted Defenders

« Previous article