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
Jason Haddix (talk | contribs) (→OWASP Game Security Framework (GSF)) |
Jason Haddix (talk | contribs) (→Contributors) (Tag: Visual edit) |
||
| Line 4: | Line 4: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| − | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
==OWASP Game Security Framework (GSF)== | ==OWASP Game Security Framework (GSF)== | ||
| Line 49: | Line 49: | ||
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. | 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. | ||
| − | |||
{{Social Media Links}} | {{Social Media Links}} | ||
| − | | valign="top" | + | | valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the OWASP Game Security Framework? == | == What is the OWASP Game Security Framework? == | ||
| Line 73: | Line 72: | ||
== Contributors == | == Contributors == | ||
| − | * | + | * Kevin Hemmingsen |
| + | * Troy Cunefare | ||
| + | * Ryan Lawrence | ||
| + | * Martin Mendoza | ||
| + | * Koray Algan | ||
== Related Projects == | == Related Projects == | ||
| Line 80: | Line 83: | ||
* [[OWASP_Mobile_Security_Project|OWASP Mobile Security]] | * [[OWASP_Mobile_Security_Project|OWASP Mobile Security]] | ||
| − | | valign="top" | + | | valign="top" style="padding-left:25px;width:200px;" | |
== Collaboration == | == Collaboration == | ||
| Line 96: | Line 99: | ||
{| width="200" cellpadding="2" | {| width="200" cellpadding="2" | ||
|- | |- | ||
| − | | align="center" valign="top" width="50% | + | | rowspan="2" align="center" valign="top" width="50%" | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]] |
| − | | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] | + | | align="center" valign="top" width="50%" | [[File:Owasp-builders-small.png|link=]] |
|- | |- | ||
| − | | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]] | + | | align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=]] |
|- | |- | ||
| − | | colspan="2" align="center" | + | | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]] |
|- | |- | ||
| − | | colspan="2" align="center" | + | | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]] |
|} | |} | ||
| Line 113: | Line 116: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| − | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
== Game Security Attack Surfaces == | == Game Security Attack Surfaces == | ||
| Line 119: | Line 122: | ||
The following is a list of the attack surfaces that can be found in video games of various types. | The following is a list of the attack surfaces that can be found in video games of various types. | ||
| − | + | {| class="wikitable" border="1" style="text-align: left" | |
| − | {| | ||
! Attack Surface | ! Attack Surface | ||
! Description | ! Description | ||
| Line 142: | Line 144: | ||
|} | |} | ||
| − | |||
{{Social Media Links}} | {{Social Media Links}} | ||
| − | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Attack Surfaces Section? == | == What is the Attack Surfaces Section? == | ||
| Line 176: | Line 177: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| − | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
== Game Security Vulnerabilities == | == Game Security Vulnerabilities == | ||
| Line 182: | Line 183: | ||
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. | 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. | ||
| − | {| | + | {| class="wikitable" border="1" style="text-align: left" |
! Attack Surface | ! Attack Surface | ||
! Vulnerability Name | ! Vulnerability Name | ||
| Line 218: | Line 219: | ||
|} | |} | ||
| − | |||
{{Social Media Links}} | {{Social Media Links}} | ||
| − | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Game Security Vulnerabilities Project? == | == What is the Game Security Vulnerabilities Project? == | ||
| Line 252: | Line 252: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| − | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
== Game Security Vulnerabilities == | == Game Security Vulnerabilities == | ||
| Line 258: | Line 258: | ||
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. | 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. | ||
| − | {| | + | {| class="wikitable" border="1" style="text-align: left" |
! Attack Surface | ! Attack Surface | ||
! Description | ! Description | ||
| Line 294: | Line 294: | ||
|} | |} | ||
| − | |||
{{Social Media Links}} | {{Social Media Links}} | ||
| − | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Game Security Vulnerabilities Project? == | == What is the Game Security Vulnerabilities Project? == | ||
| Line 328: | Line 327: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| − | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
== Game Security Vulnerabilities == | == Game Security Vulnerabilities == | ||
| Line 334: | Line 333: | ||
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. | 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. | ||
| − | {| | + | {| class="wikitable" border="1" style="text-align: left" |
! Attack Surface | ! Attack Surface | ||
! Description | ! Description | ||
| Line 370: | Line 369: | ||
|} | |} | ||
| − | |||
{{Social Media Links}} | {{Social Media Links}} | ||
| − | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Game Security Vulnerabilities Project? == | == What is the Game Security Vulnerabilities Project? == | ||
| Line 404: | Line 402: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| − | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
== Common Game Security Defenses == | == Common Game Security Defenses == | ||
| Line 411: | Line 409: | ||
| − | + | ||
{{Social Media Links}} | {{Social Media Links}} | ||
| − | | valign="top" | + | | valign="top" style="padding-left:25px;width:300px;border-right: 1px dotted gray;padding-right:25px;" | |
== What is the Game Security Vulnerabilities Project? == | == What is the Game Security Vulnerabilities Project? == | ||
| Line 482: | Line 480: | ||
: "The attacker attacked and edited the <code>LOCAL GAME CLIENT (Attack Surface)</code>, which had a <code>LACK OF CLIENT INTEGRITY CONTROLS (Vulnerability)</code>, which allowed her to <code>ARTIFICIALLY INCREASE HER ABILITIES (Attacker Goal)</code>, ultimately leading to an <code>UNHAPPY PLAYER BASE (Negative Outcome)</code> and <code>DECLINING GAME REVENUE (Negative Outcome)</code> due to cheating.” | : "The attacker attacked and edited the <code>LOCAL GAME CLIENT (Attack Surface)</code>, which had a <code>LACK OF CLIENT INTEGRITY CONTROLS (Vulnerability)</code>, which allowed her to <code>ARTIFICIALLY INCREASE HER ABILITIES (Attacker Goal)</code>, ultimately leading to an <code>UNHAPPY PLAYER BASE (Negative Outcome)</code> and <code>DECLINING GAME REVENUE (Negative Outcome)</code> due to cheating.” | ||
| − | |||
{{Social Media Links}} | {{Social Media Links}} | ||
| Line 497: | Line 494: | ||
* Home Electronics | * Home Electronics | ||
* Public Infrastructure | * Public Infrastructure | ||
| − | + | ||
[http://builditsecure.ly BuildItSecure.ly] | [http://builditsecure.ly BuildItSecure.ly] | ||
| Line 508: | Line 505: | ||
* Curate informational resources | * Curate informational resources | ||
* Present research | * Present research | ||
| − | + | ||
[https://otalliance.org Online Trust Alliance] | [https://otalliance.org Online Trust Alliance] | ||
| Line 514: | Line 511: | ||
Addressing the mounting concerns, in January 2015 the Online Trust Alliance, established the [https://otalliance.org/initiatives/internet-things IoT Trustworthy Working Group (ITWG)], a multi-stakeholder initiative. The group recognizes “security and privacy by design” must be a priority from the onset of product development and be addressed holistically. The framework focuses on privacy, security sustainability. The sustainability pillar is critical as it looks at the life-cycle issues related to long- term supportability and transfers of ownership of devices and the data collected. | Addressing the mounting concerns, in January 2015 the Online Trust Alliance, established the [https://otalliance.org/initiatives/internet-things IoT Trustworthy Working Group (ITWG)], a multi-stakeholder initiative. The group recognizes “security and privacy by design” must be a priority from the onset of product development and be addressed holistically. The framework focuses on privacy, security sustainability. The sustainability pillar is critical as it looks at the life-cycle issues related to long- term supportability and transfers of ownership of devices and the data collected. | ||
| − | + | ||
[https://allseenalliance.org/framework AllSeen Alliance] | [https://allseenalliance.org/framework AllSeen Alliance] | ||
The AllSeen Alliance is a Linux Foundation collaborative project. They're a cross-industry consortium dedicated to enabling the interoperability of billions of devices, services and apps that comprise the Internet of Things. The Alliance supports the AllJoyn Framework, an open source software framework that makes it easy for devices and apps to discover and communicate with each other. Developers can write applications for interoperability regardless of transport layer, manufacturer, and without the need for Internet access. The software has been and will continue to be openly available for developers to download, and runs on popular platforms such as Linux and Linux-based Android, iOS, and Windows, including many other lightweight real-time operating systems. | The AllSeen Alliance is a Linux Foundation collaborative project. They're a cross-industry consortium dedicated to enabling the interoperability of billions of devices, services and apps that comprise the Internet of Things. The Alliance supports the AllJoyn Framework, an open source software framework that makes it easy for devices and apps to discover and communicate with each other. Developers can write applications for interoperability regardless of transport layer, manufacturer, and without the need for Internet access. The software has been and will continue to be openly available for developers to download, and runs on popular platforms such as Linux and Linux-based Android, iOS, and Windows, including many other lightweight real-time operating systems. | ||
| − | + | ||
[http://www.iiconsortium.org/ The Industrial Internet Consortium (IIC)] | [http://www.iiconsortium.org/ The Industrial Internet Consortium (IIC)] | ||
The Industrial Internet Consortium is the open membership, international not-for-profit consortium that is setting the architectural framework and direction for the Industrial Internet. Founded by AT&T, Cisco, GE, IBM and Intel in March 2014, the consortium’s mission is to coordinate vast ecosystem initiatives to connect and integrate objects with people, processes and data using common architectures, interoperability and open standards. | The Industrial Internet Consortium is the open membership, international not-for-profit consortium that is setting the architectural framework and direction for the Industrial Internet. Founded by AT&T, Cisco, GE, IBM and Intel in March 2014, the consortium’s mission is to coordinate vast ecosystem initiatives to connect and integrate objects with people, processes and data using common architectures, interoperability and open standards. | ||
| − | + | ||
[http://securingsmartcities.org/ Securing Smart Cities] | [http://securingsmartcities.org/ Securing Smart Cities] | ||
| Line 559: | Line 556: | ||
== Commonly Used Game Hacking Tools == | == Commonly Used Game Hacking Tools == | ||
| − | |||
{{Social Media Links}} | {{Social Media Links}} | ||
| Line 584: | Line 580: | ||
| links_url1 = | | links_url1 = | ||
| links_name1 = | | links_name1 = | ||
| − | |||
| − | |||
}} | }} | ||
| Line 592: | Line 586: | ||
| + | __NOTOC__ <headertabs></headertabs> | ||
| − | + | [[Category:OWASP_Project]] | |
| − | + | [[Category:OWASP_Document]] | |
| − | + | [[Category:OWASP_Download]] | |
| − | [[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]] | + | [[Category:OWASP_Release_Quality_Document]] |
Revision as of 05:49, 21 March 2017
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. In 2016 the videogame market became 99.6 Billion dollar industry... any why shouldn't it be? Some of the most prolific and complex software developed today are video games. They are professionally played, sponsored, scrutinized, monetized, and celebrated, just like many sports. They handle clients, servers, web components, monetary transfers, social interactions, virtual markets, etc, with every bit the need of security that most internet hosted apps have (if not more in some cases). The GSF is designed to help threat model gaming issues that have devastated new games. Most importantly we hope the GSF can help new developers and security testers alike root out bugs in your favorite titles. The framework is broken into three main concepts / sections:
LicensingThe 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:
Project Leaders
Contributors
Related Projects |
CollaborationQuick DownloadCOMING SOON News and Events
Classifications
| |||||||
