This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Game Security Framework Project"

From OWASP
Jump to: navigation, search
(→‎Game Security Vulnerabilities)
Line 439: Line 439:
 
= Examples =
 
= Examples =
  
−
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
 
  
−
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
+
{| class="wikitable"
−
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
+
! style="font-weight: bold;" | Vulnerabilty Name
−
 
+
! style="font-weight: bold;" | Description
−
== Game Security Vulnerabilities ==
+
! style="font-weight: bold;" | Surface Area
−
 
+
! style="font-weight: bold;" | Attacker Goal
−
The following is a list of the vulnerabilities that can be found in video games of various types, and the attack surfaces they're likely to be associated with.
+
! style="font-weight: bold;" | Negative Outcome
−
 
+
! style="font-weight: bold;" | Tester Tool
−
{| border="1" class="wikitable" style="text-align: left"
+
! style="font-weight: bold;" | Defense
−
! Attack Surface
+
! Ref
−
! Description
+
! Genre
−
|-  
+
|-
−
| '''Local Game Client'''
+
| Local Resource Modification, Client-side Logic Flaw
−
|
+
| In 2015 The Division experienced an exploit that allowed an attacker to switch weapons rapidly, applying weapon buffs in a stacking manner, with no cap.
−
* Ability to edit in-game resources
+
| Game Client
−
* Ability to bypass license requirement
+
| Unfair Player Advantage
−
|-
+
| Player Anger, Lost Revenue
−
| '''Game Network Traffic'''
+
| Game Client
−
|
+
| Cryptographic Integrity Checks on Game Client
−
* Network Denial of Service (player)
+
| http://www.gamesradar.com/theres-a-division-damage-stacking-glitch-if-youve-got-fast-fingers/
−
** Player bandwidth exhaustion
+
| 3PS/1PS/MMO
−
** Player game client resource exhaustion
 
−
|-
 
−
| '''Game Application Traffic'''
 
−
|
 
−
* Application Level Denial of Service (Player)
 
−
** Player application logic Denial of Service
 
−
|-  
 
−
| '''Game Server'''
 
−
|
 
−
* Application Level Denial of Service (Server)
 
−
** Server application logic Denial of Service
 
−
* Ability to modify game ladder rankings
 
−
* Ability to modify own player resources
 
−
|-  
 
−
| '''Game Economy'''
 
−
|
 
−
* Ability to generate unlimited money on client side
 
−
* Ability to generate unlimited money through network/application traffic modification
 
−
* Ability to modify prices for in-game items
 
−
* Ability to replay financial actions such as buying or selling through network/application manipulation
 
 
|-
 
|-
 
|}
 
|}
Line 487: Line 466:
 
{{Social Media Links}}
 
{{Social Media Links}}
  
−
| valign="top"  style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" |
 
−
 
−
== What is the Game Security Vulnerabilities Project? ==
 
−
 
−
The Security Vulnerabilities Project provides information on what types of vulnerabilities exist within games, and which attack surfaces they fall under.
 
−
 
−
== Project Leaders ==
 
−
 
−
* Jason Haddix
 
−
 
−
== Related Projects ==
 
−
 
−
* [[OWASP_Mobile_Security_Project|OWASP Mobile Security]]
 
−
* [[OWASP_Top_Ten_Project|OWASP Web Top 10]]
 
−
 
−
== Collaboration ==
 
−
[https://game-security.slack.com The Slack Channel]
 
−
 
−
== Resources ==
 
−
* [https://www.owasp.org/index.php/Top_IoT_Vulnerabilities Top 10 IoT Vulnerabilities from 2014]
 
−
 
−
== News and Events ==
 
−
* Coming Soon
 
−
 
−
|}
 
  
 
= Community =
 
= Community =

Revision as of 02:14, 18 January 2017

OWASP Project Header.jpg

OWASP Game Security Framework (GSF)

The OWASP Game Security Framework (GSF) represents a modular approach to understanding the security issues that surround video game ecosystems.


The framework is broken into three main concepts / sections:


1. Identifying and clustering the components of risk within the overall game security space, and then giving instances of each component.


Components include the following:


  • Attack Surfaces: the various surface areas that can be attacked by attackers in order to cause harm to the gaming ecosystem.
  • Vulnerabilities: the specific weaknesses in design or implementation that allows attackers to successfully target a given game.
  • Attacker Goals: a list of the reasons that an attacker might want to attack a given game.
  • Negative Outcomes: a collection of ways that the gaming company could ultimately be impacted negatively by attacks to its game and associated infrastructure.


2. A natural language semantic structure for thinking about and articulating game security issues, which uses the modular risk components as sentence structure.


Example:


"The attacker attacked and edited the LOCAL GAME CLIENT (Attack Surface), which had a LACK OF CLIENT INTEGRITY CONTROLS (Vulnerability), which allowed her to ARTIFICIALLY INCREASE HER ABILITIES (Attacker Goal), ultimately leading to an UNHAPPY PLAYER BASE (Negative Outcome) and DECLINING GAME REVENUE (Negative Outcome) due to cheating.”


Using this structure, security testers can clearly communicate the various aspects of a game security issue to many different types of stakeholder—from pentesting peers to business executives in the gaming industry.


3. Examples of real-world examples of previous attacks against games, and how the attacks map to the GSF framework components.

Licensing

The OWASP Game Security Framework is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.


Share this:  E-mail this story Bookmark with Facebook Share on Digg.com Share on delicious Share on reddit.com Share on stumbleupon.com Share on LinkedIn.com Share on twitter.com Seed on Newsvine

What is the OWASP Game Security Framework?

The goal of the OWASP Game Security Framework is to provide a structure for discussing the various aspects around the security of video games.

The target audience for the project includes:

  • Gamers
  • Game designers
  • Penetration testers
  • Gaming executives
  • Anyone else with a vested interest in game security

Project Leaders

  • Jason Haddix
  • Daniel Miessler

Contributors

  • LFG

Related Projects

Collaboration

The Slack Channel

Quick Download

COMING SOON

News and Events

  • [JANUARY 2017] Doing a complete redesign of the project.

Classifications

Owasp-incubator-trans-85.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Game_Security_Framework_Project&oldid=225299"