Difference between revisions of "OWASP Game Security Framework Project"

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:

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) , which could have been prevented by DEFENSE.”

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
• QA
• Game designers
• Penetration testers
• Gaming executives
• Anyone else with a vested interest in game security

Project Leaders

• Jason Haddix
• Daniel Miessler

Contributors

• Kevin Hemmingsen
• Troy Cunefare
• Ryan Lawrence
• Martin Mendoza
• Koray Algan
• Tom Simkovic
• Matt Espinoza
• Chad Lynch

Related Projects

• OWASP Web Top 10
• OWASP Mobile Security

Collaboration

The Slack Channel

Quick Download

COMING SOON

News and Events

• January, 2017: Doing a complete redesign of the project.
• March 2017: Presenting version 1.0 at HouSecCon 2017.

Classifications