Proxy betting is when one person uses another person’s authenticated account to place wagers, often from a different location. The account may pass login controls while still violating jurisdiction, consent, and fraud rules, which makes it an identity governance problem as well as a gambling integrity issue.
What Proxy Betting Means in Practice
Proxy betting is more than an account-sharing violation. The core issue is that the authenticated account holder and the actual wager placer are different people, so the event can satisfy login controls while still breaking rules tied to consent, location, jurisdiction, and fraud. That makes proxy betting a governance and integrity problem, not just an authentication problem.
Because the platform sees a valid session, organisations can miss the real actor unless they correlate identity signals with behavioural and contextual evidence. The practical question is not only whether the account was logged in, but whether the person placing the bet was authorised to act for that account under the relevant rules and terms.
Why Proxy Betting Is Hard to Trust
Proxy betting undermines the assumption that successful authentication means legitimate use. A wager may appear technically valid, yet still be invalid if the user is operating from a prohibited location, acting without the account holder’s consent, or using the account to evade controls that depend on the true actor’s identity.
This is why proxy betting sits at the intersection of fraud prevention, responsible gambling controls, and identity governance. The platform has to care about who actually made the decision, where the action occurred, and whether the account relationship itself is being abused rather than simply used.
When proxy activity is allowed to continue, it can distort risk scoring, anti-fraud decisions, dispute handling, and regulatory reporting. It also creates a misleading trust signal for downstream systems that assume the authenticated session reflects the real user.
How Organisations Detect Exposure to Proxy Betting
Exposure is usually assessed by comparing the account’s normal behaviour with the session’s real-world context. Location anomalies, device changes, repeated handoff patterns, velocity spikes, and inconsistent behavioural signals can all indicate that the authenticated account is not being used by the genuine holder.
Controls work best when they combine account history, device and session telemetry, and policy checks that are designed to detect account delegation or misuse. This is also where a broader access-control view matters, because the issue is not only login success, but whether access is being exercised in a way that matches the account’s permitted use.
For a control-oriented baseline on authentication, logging, and access governance, NIST SP 800-53 Rev 5 Security and Privacy Controls is a useful reference point. For session and identity assurance, NIST SP 800-63 Digital Identity Guidelines helps frame why authentication strength alone does not prove legitimate account use.
Controls, Enforcement, and Consequences
The most effective response is usually policy enforcement plus evidence preservation. Organisations need clear terms that prohibit account lending or proxy use, controls that can challenge suspicious sessions, and review processes that preserve the facts needed for dispute resolution, abuse investigation, or regulatory reporting.
Where proxy betting is tied to location restrictions or other eligibility rules, enforcement should be based on the specific rule being protected rather than generic account access alone. The key operational question is whether the platform can reliably distinguish the permitted account holder from a third party acting through that account.
Proxy betting is also a useful example of why least-privilege thinking matters in identity and session design. If a session can be used by anyone who has the credentials or a live handoff, the control surface is too weak for environments where the identity behind the action matters.
For a broader control and monitoring lens, NIST Cybersecurity Framework 2.0 is helpful for organising governance, detection, response, and recovery around the abuse of trusted access.
Risk and Threat Considerations
Proxy betting creates a material abuse path because it allows a legitimate session to be used by an unauthorised actor. The main risk is not credential theft alone, but the misuse of a trusted account to bypass jurisdictional, consent, and fraud controls.
Failure mechanism: The platform validates the login, but not the legitimacy of the person behind the action, so a third party can place wagers under a trusted identity and evade rule enforcement.
Impact: This can lead to regulatory exposure, dispute inflation, failed fraud detection, unfair-play concerns, and compromised trust in the account and transaction trail.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST SP 800-63 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Proxy betting relies on trusted account use despite a different real actor. |
| AC-6 — Least Privilege | Proxy betting abuses more authority than the real actor should have over the account. | |
| Recommendation — Strengthen account authentication and session controls to reduce misuse of authenticated access. Limit account capabilities so trusted access cannot be casually delegated or misused. | ||
| NIST SP 800-63 | Digital Identity Guidelines | Defines assurance ideas showing authenticated access may still need contextual validation. |
| Recommendation — Apply identity assurance checks that go beyond password success to confirm legitimate use. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions and Authorizations | Proxy betting is an access-authorisation misuse problem after authentication succeeds. |
| DE.CM-01 — Monitoring for Unauthorised Use | Detection depends on spotting anomalous sessions, locations, and behaviour. | |
| Recommendation — Verify that permitted account use matches the action, context, and policy being enforced. Monitor for anomalous account use patterns that suggest proxy activity or handoff. | ||
Practitioner Guidance
What to watch for: Treat repeated location mismatch, unusual device switching, and account handoff patterns as signs that the authenticated user may not be the real actor. Those signals matter most when policy depends on who is actually placing the wager, not just on whether the account was successfully accessed.
Governance implication: Define proxy use as a prohibited account-abuse scenario and make ownership clear for investigation, enforcement, and customer disputes. That keeps the operational response aligned with the integrity rule being protected, rather than reducing the issue to a simple login failure.
Related resources from NHI Mgmt Group
- Who is accountable when authentication satisfies policy but proxy betting still occurs?
- How should online betting platforms handle location verification when users may be using VPNs or proxy servers?
- Why does biometric authentication reduce account takeover and proxy betting risk in online gambling?
- How should sports betting operators use digital identity and MFA to stop proxy betting without creating unnecessary friction for legitimate players?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org