Special Ops is being built for ranked play. That means we treat cheating the way we treat netcode: as infrastructure, not a feature you bolt on after launch. Our answer is two linked systems - a restrictive kernel-level anti-cheat running at ring 0, and a dedicated matchmaking queue for operators who have completed identity verification through KYC and CIP.
One protects the simulation. The other protects the people inside it.
Kernel anti-cheat at ring 0
User-mode anti-cheat can only see what the operating system allows. Kernel-level protection operates at ring 0 - the same privilege tier as the OS itself - which gives us the visibility and enforcement depth a 128-tick tactical shooter actually needs.
Our approach is deliberately restrictive. Unauthorized memory injection, tampered overlays, and known cheat frameworks are blocked before they can influence shot registration or movement authority. The client is not trusted to police itself. Validation runs deep, pairs with server-side checks, and feeds a ban pipeline built for permanent enforcement on confirmed integrity failures.
We are not building a light touch. Competitive shooters live or die on whether a round feels honest. Ring-0 is the cost of that honesty.
Why verification matters
Hardware bans and account bans help. They do not solve the problem of disposable identities. Smurfs, ban evasion, and serial offenders are a matchmaking problem as much as a security problem - especially in a game where ranked standing is supposed to mean something.
That is where Customer Identification Program (CIP) and Know Your Customer (KYC) verification come in. Operators who complete identity verification receive access to a separate queue - matchmaking reserved for verified users only. Same rules. Same tick rate. A higher trust floor.
The verified queue
The verified queue is not a cosmetic badge. It is a dedicated matchmaking path where every player in the lobby has passed identity checks tied to real-world accountability. Queue times may differ from open matchmaking. The experience inside should not - same simulation, same objectives, same extraction pressure.
Verification status is enforced at matchmaking time. Lose verified standing and you lose access to the queue until the issue is resolved. The goal is simple: if you are grinding ranked Special Ops, you are doing it against other operators who chose to stand behind their name.
Privacy and proportionality
Strong protection does not mean careless data handling. Identity verification flows through established KYC/CIP providers. We collect what is required to verify an operator and maintain queue integrity - not more. Anti-cheat telemetry is scoped to integrity signals, not unrelated personal data.
Players who prefer not to verify can still access other modes as those become available. The verified queue is for people who want the strictest competitive environment we can offer.
What this means for launch
Both systems are on the roadmap as launch-critical infrastructure - not post-release experiments. Kernel anti-cheat ships with the competitive stack. The verified queue opens when identity verification is wired end-to-end through our live services.
Special Ops is a simulation where milliseconds decide rounds. We intend to run it on a network where those milliseconds are earned, not stolen - and where the ranked ladder points at real operators, not throwaway accounts.