R6 Player Protection
What Anti-Cheat Does Rainbow Six Siege Use?
Rainbow Six Siege uses BattlEye — a kernel-level anti-cheat driver — on Windows PC, layered with Ubisoft's own server-side detection, telemetry analysis and Match Replay review. On console, a separate system called MouseTrap targets unsupported mouse-and-keyboard adapters. Here is exactly how each layer works and what it means for you.
- BattlEye — the kernel-level anti-cheat that ships with Siege on PC
- Ubisoft server-side detection — behavioural analytics and ban waves
- Match Replay — how player reports turn into manual bans
- MouseTrap — console-only, targets XIM/Cronus adapters
- What BattlEye can and can't detect in 2026
- HWID bans — what Siege fingerprints when it bans you
Confirm the current product state before each session.
Eligible orders are delivered through the customer dashboard.
Review platform and hardware requirements before checkout.
The short answer
Rainbow Six Siege's anti-cheat on PC is BattlEye. It has been part of Siege since 2016 and runs a signed Windows driver at kernel level — the same privilege level as Windows itself. That means it can scan every process, driver and piece of memory on your machine, not just the game. BattlEye is not the only layer, though. Ubisoft runs its own server-side detection on top of it, reviews suspicious matches through Match Replay, and issues hardware (HWID) bans to repeat offenders. On console, MouseTrap handles a completely different problem — players using mouse-and-keyboard adapters — and is often confused with the PC anti-cheat.
BattlEye on Siege — how it actually works
BattlEye is an independent German anti-cheat company, around since 2004 and kernel-level since 2015. Ubisoft contracts it per-game, and Siege is one of its longest-running deployments. What makes BattlEye different from signature scanners like VAC is its approach: instead of only looking for known cheat files, it watches behaviour — suspicious memory access patterns, unsigned drivers, injected code, unusual timing. BattlEye is also famous for ban waves: it will silently flag a cheat for days or weeks, then ban every detected account in one sweep. That's why Siege bans feel random — they're not, they're batched. Other games using BattlEye: DayZ, PUBG, Arma 3, Destiny 2, Escape from Tarkov.
Ubisoft's own layers on top of BattlEye
BattlEye handles the client side; Ubisoft handles everything else: • Server-side analytics — shot accuracy distributions, headshot ratios, reaction times and movement patterns are compared against legit player baselines. Statistical outliers get flagged for review even if BattlEye never fires. • Match Replay review — reported players' replays are reviewed, and obvious rage hacking (snapping through walls, pre-aiming every corner) converts reports into bans. • Data bans — Ubisoft periodically bans accounts whose stats are mathematically implausible, independent of any client detection. This is why 'undetected' only ever describes the BattlEye layer. A cheat can be invisible to the driver and still get an account banned through stats and replays.
MouseTrap — the console system everyone confuses with PC anti-cheat
MouseTrap is not PC anti-cheat. It's Ubisoft's system for detecting mouse-and-keyboard adapters (XIM, Cronus, ReaSnow) on PlayStation and Xbox. Detected players get input latency added to their device and are eventually moved into PC lobbies. It matters here because search results mix the two up constantly: if you're on Windows PC, MouseTrap does not apply to you at all. Your protection stack is BattlEye + Ubisoft server-side. If you're on console using an adapter, BattlEye is irrelevant to you — MouseTrap is the system watching.
HWID bans — what Siege fingerprints
When Ubisoft decides an account is a repeat offender, it doesn't just ban the account — it bans the machine. Siege's HWID ban fingerprints hardware identifiers so that new accounts on the same PC get banned on login or within their first matches. The identifiers commonly fingerprinted include motherboard/SMBIOS serials, disk volume serials, MAC addresses and TPM data. This is why the spoofer market exists: a HWID spoofer changes these values before the game reads them, making the ban non-portable to a new account. Spoofing after a ban without knowing exactly which identifiers were flagged is hit-and-miss — which is why full-suite spoofers cover all of them at once.
What BattlEye can't see
Even a kernel-level driver has a hard ceiling: it can only see what happens on your machine. Two categories of cheating sit outside its reach by design: • DMA hardware — a PCIe card in the gaming PC reads game memory and streams it to a second PC, where the cheat runs. On the gaming PC there is no cheat process, no injected code, no suspicious driver — nothing for BattlEye to find. Detection of DMA relies on PCIe device enumeration and firmware fingerprinting, which private DMA firmware is built to defeat. • Externals with clean read paths — overlays that read memory without writing or injecting leave far fewer traces than internal DLL cheats. This is the technical reason the cheat market split into 'internal' (stronger features, higher detection risk) and 'external/DMA' (fewer features, much harder to detect).
How to read a cheat status page honestly
A status label like 'Undetected' on any provider's page — including ours — records the latest check against BattlEye's client-side detection at that moment. It says nothing about Ubisoft's server-side analytics, nothing about Match Replay, and nothing about tomorrow's BattlEye update. Treat status as time-specific information: check it immediately before every session, never play during 'Updating', and remember that no status page can protect an account from a ban wave that was silently collected weeks earlier.
Frequently Asked Questions
Review notes and sources
Reviewed by the RageByte product team on . This supporting page is checked against the current product page, checkout options, status information and publisher documentation. Send corrections to [email protected].
Primary reference: Ubisoft Rainbow Six Siege Player Protection. Third-party software can violate publisher rules and lead to account or hardware penalties. A status label records a current check, not a guarantee against future detection.
Before checkout, read the refund policy and privacy policy.
Explore the Rainbow Six Siege hub
Product, aim and visual references with current publisher-source links.
Current plans, compatibility, media and live product status for Rainbow Six Siege.
How smoothing, FOV, target selection and visibility checks are configured.
Player, operator, gadget, drone and radar display options explained.
Check the current product state before every session.
Review the current product options
Confirm compatibility, live status and purchase terms before checkout.