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
(Project Leaders)
(IoT Vulnerabilities Project)
Line 175: Line 175:
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
== IoT Vulnerabilities Project ==
 
  
 
{| border="1" class="wikitable" style="text-align: left"
 
{| border="1" class="wikitable" style="text-align: left"
! Vulnerability
 
 
! Attack Surface
 
! Attack Surface
! Summary
+
! Description
|-
+
|-  
| '''Username Enumeration'''
+
| '''Local Game Client'''
 
|
 
|
* Administrative Interface
+
* The locally running game client that is accessible to the gamer because it's running on his/her machine.
* Device Web Interface
+
|-
* Cloud Interface
+
| '''Game Network Traffic'''
* Mobile Application
 
 
|
 
|
* Ability to collect a set of valid usernames by interacting with the authentication mechanism
+
* The network which game traffic traverses in order to reach the game's server or peers who are playing the game.
|-
+
|-  
| '''Weak Passwords'''
+
| '''Game Server'''
 
|
 
|
* Administrative Interface
+
* The game server that is hosting the instance that gamers connect to in order to play the game.
* Device Web Interface
+
|-
* Cloud Interface
+
| '''Game Economy'''
* Mobile Application
 
 
|
 
|
* Ability to set account passwords to '1234' or '123456' for example.
+
* The economic system that exists within the game.
|-
 
| '''Account Lockout'''
 
|
 
* Administrative Interface
 
* Device Web Interface
 
* Cloud Interface
 
* Mobile Application
 
|
 
* Ability to continue sending authentication attempts after 3 - 5 failed login attempts
 
|-
 
| '''Unencrypted Services'''
 
|
 
* Device Network Services
 
|
 
* Network services are not properly encrypted to prevent eavesdropping by attackers
 
|-
 
| '''Two-factor Authentication'''
 
|
 
* Administrative Interface
 
* Cloud Web Interface
 
* Mobile Application
 
|
 
* Lack of two-factor authentication mechanisms such as a security token or fingerprint scanner
 
|-
 
| '''Poorly Implemented Encryption'''
 
|
 
* Device Network Services
 
|
 
* Encryption is implemented however it is improperly configured or is not being properly updated, e.g. using SSL v2
 
|-
 
| '''Update Sent Without Encryption'''
 
|
 
* Update Mechanism
 
|
 
* Updates are transmitted over the network without using TLS or encrypting the update file itself
 
|-
 
| '''Update Location Writable'''
 
|
 
* Update Mechanism
 
|
 
* Storage location for update files is world writable potentially allowing firmware to be modified and distributed to all users
 
|-
 
| '''Denial of Service'''
 
|
 
* Device Network Services
 
|
 
* Service can be attacked in a way that denies service to that service or the entire device
 
|-
 
| '''Removal of Storage Media'''
 
|
 
* Device Physical Interfaces
 
|
 
* Ability to physically remove the storage media from the device
 
|-
 
| '''No Manual Update Mechanism'''
 
|
 
* Update Mechanism
 
|
 
* No ability to manually force an update check for the device
 
|-
 
| '''Missing Update Mechanism'''
 
|
 
* Update Mechanism
 
|
 
* No ability to update device
 
|-
 
| '''Firmware Version Display and/or Last Update Date'''
 
|
 
* Device Firmware
 
|
 
* Current firmware version is not displayed and/or the last update date is not displayed
 
 
|-
 
|-
 
|}
 
|}

Revision as of 05:13, 17 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.


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