DMA setup for Overwatch 2: Defense Matrix, not a kernel driver
Overwatch has no published kernel-level anti-cheat, which moves the risk rather than removing it. Learn what Defense Matrix is and what a hero-shooter build needs.
Short answer
Overwatch runs Blizzard's Defense Matrix, a programme with no kernel-level driver on record, and Blizzard will not detail its client-side protections. The game PC is easier to set up, but the risk moves to server-side detection, account action and what players see. The store sells an Overwatch 2 external cheat at /products/overwatch-2 and a DMA cheat at /products/overwatch-dma.
On this page9
- What is Defense Matrix?
- Where detection happens without a kernel driver
- How the February 2026 relaunch reset the client
- Which layers does an Overwatch build need?
- The right order to start a session
- Overwatch checklist before each match
- Common Overwatch problems and fixes
- Overwatch setup questions
- What we can't confirm about Overwatch
What is Defense Matrix?
Blizzard does not license EAC or BattlEye for Overwatch, and it has not published a kernel-mode anti-cheat driver for the game either. Instead it publishes Defense Matrix, an umbrella programme for cheat detection, account security, reporting and work on player behaviour. The Defense Matrix posts are explicit on three points. Blizzard works with external anti-tamper and anti-reverse-engineering vendors, and it is building technology that stops hacks from working instead of only detecting them. In its own words, it will not go into details. Over a million accounts have been actioned for cheating since launch, and the Season 18 update raised the penalty under the console peripheral rules to full account bans.
Where detection happens without a kernel driver
For a title with no kernel driver, the useful question is which detection surfaces remain, and all of the surfaces listed here do.
| Surface | What it observes | What a two-machine build changes about it |
|---|---|---|
| Client-side protection | Anti-tamper and anti-reverse-engineering layers Blizzard declines to describe | This is the surface the architecture addresses: the reader is not on the game PC |
| Server-side behaviour | How a player performs, match after match, measured against models | Unchanged. Nothing about where a reader runs alters what the server is sent |
| Player reports | Eleven other people in every match, with a report flow Blizzard has repeatedly expanded | Unchanged, and it is the dominant surface in a game this legible |
| Replays | Recent matches can be rewatched from any player's point of view and shared | Unchanged. A suspicious round is reviewable after the fact, by humans, frame by frame |
| Peripheral detection | Input-device detection, deployed on console first and escalated in Season 18 | Relevant to the input layer of any build: the subject of that work is machine-shaped input |
Having no published kernel driver does not mean having no detection. The weight has moved from scanning a machine to watching a player, which is harder to reason about but no less strict.
Warning
How the February 2026 relaunch reset the client
On 10 February 2026 the game dropped the 2 and relaunched as Overwatch, with new heroes, a hero sub-role and perk system, and a rebuilt interface. A change on that scale amounts to a new client, so anything written against the previous build stopped matching it. The store still lists its products under the old name, and this guide keeps its old web address, for the same reason in both cases: people still type the same search phrases. Treat the relaunch as a measure of how far one Overwatch update can move, and compare the status row's date with the game's.
Which layers does an Overwatch build need?
Overwatch has twelve players, small maps, a lot of vertical geometry and ability cooldowns, so the information layer behaves differently than it does in an extraction game. Health and position data is useful right away, while a flat radar is worth less, because the kill feed and ability sounds already carry much of that information. The aim layer depends on the hero: machine-shaped input becomes obvious on hitscan heroes and less so on projectile heroes. If your build includes an input device, that is the layer eleven other people are watching, and it is also the layer a replay keeps.
The right order to start a session
There is no anti-cheat startup stage to wait for, and that tempts people to start things in a careless order. Keep the order anyway, because it is how you tell a reader problem from a game problem.
- Launch the game on its own on the game PC and reach the main menu with no reader attached
- Read today's status row for this title
- Boot the second PC and confirm the card enumerates
- Start the reader and attach it to the card
- Launch the game and attach to its process from the menu before you queue
- If a fuser is in the video path, set borderless fullscreen and match the resolution and refresh rate on both machines
- Check your own replay after a session if you want to see what other players could see
Overwatch checklist before each match
- The game launches and reaches the menu on its own
- You have read today's status row for this title
- You know the client's current patch and whether the status row is older than it
- The card is in its data port, and the reader was attached before you queued
- The game PC enumerates any input device as a standard mouse
- Borderless fullscreen is set if a fuser is in the video path
- You have accepted that a replay of your match can be rewatched from any angle
Common Overwatch problems and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| The reader attaches but reads nothing useful after a patch | The client build changed: Overwatch patches every season, with midseason and balance patches in between | Check the status board against the new build and wait for a published update |
| There is no anti-cheat error anywhere, but the build still does not work | There is no kernel driver to produce an anti-cheat error, so every failure shows up as a reader, memory-map or offset problem | Diagnose the stack one layer at a time (card, USB path, initialisation, then the game) instead of looking for an anti-cheat message that will never appear |
| Action was taken on the account with no warning and no error | Detection in this game is weighted towards server-side behaviour and player reports, and neither produces a client-side message | There is no technical fix, because this is the risk profile of the title and no hardware architecture removes it |
| The overlay is visible on a stream or in a clip | The overlay is composited into the game PC's output, or capture is set to the wrong source | Review the display path: a fuser puts the overlay into the video signal, so anything that captures that signal captures the overlay too |
Overwatch setup questions
Which anti-cheat does Overwatch 2 use?
Overwatch uses Blizzard's own Defense Matrix programme rather than a licensed third-party anti-cheat. It covers client-side protections that Blizzard does not detail, along with server-side detection, reporting, account security and console peripheral detection.
Is there a kernel-level anti-cheat in Overwatch?
Blizzard has not published one for Overwatch. ReportedIts Defense Matrix posts describe work with external anti-tamper vendors but do not name a kernel driver. The lack of a published driver says nothing about safety.
Does that make Overwatch an easier title for a DMA build?
It makes the game PC easier to set up, since there is no documented kernel driver and no published Secure Boot or TPM requirement. It does not make the title safer, because the risk sits in behaviour, in reports and in replays that anyone can rewatch.
What did the February 2026 relaunch change?
The game relaunched as Overwatch with new heroes, sub-roles and perks, and a rebuilt interface. In practice it became a new client, so anything written against the older build no longer matched it.
Does the console peripheral crackdown affect PC builds?
The Season 18 enforcement targets unapproved peripherals in the console Controller Pool. It matters for PC builds as proof that Blizzard is investing in input-behaviour detection, which is the layer where an input device operates.
Info
What we can't confirm about Overwatch
Whether an Overwatch build is working today is a question for the live status board, and we cannot tell you what Blizzard's client-side protections do. ReportedBlizzard says that it will not detail them. Anyone who claims to know exactly what those protections catch is therefore guessing. Read the status board, note the game's patch date, and ask support before you buy.
Sources
The Defense Matrix details are bench notes rather than something a published document backs, and the February 2026 relaunch showed how far one patch can move them.
Read next
- DMA setup for Marvel Rivals: NetEase anti-cheat and Kernel DMA Protection
- What are DMA cheats and how do they work
- KMBox Net, KMBox B+, MAKCU, Teensy or Arduino: which input device to buy
- Fuser and capture display path
- How to read the build status board
- DMA setup for Call of Duty: one anti-cheat, a new game every year
- DMA setup for FiveM: the server is the anti-cheat
- DMA setup for Fortnite: what the build needs
Still stuck? Open a ticket on Discord
All guides