Difference between revisions of "OWASP Video Game Security Framework"

Revision as of 17:57, 26 April 2019

OWASP Video Game Security Framework (VGSF)

OWASP Video Game Security Framework (VGSF) defines an approach to discovering solutions for strategy, development, operations, and management surrounding security for video game industry business models

Most organizations that operate in the digital landscape approach security as a last afterthought when compared to the overall business strategy and operations. In the recent years it has become more apparent the consequences of such behavior with increasingly amounts of data breaches happening. The cost associated with an organization’s loss of intellectual property and other digital assets has reached the millions.

With the fast growth of the video game industry (174 billion by 2021 - Newzoo Global Game Forecast) in recent years, it is critical that organizations operating in this space have a strong security posture. Cyber-attacks aimed at various components of a business can affect the interoperability, user protected info, end-game product, and overall business model. As more businesses and clients operate in the cyber space its important to leverage security as a way to create sustainable trust, lead competitively, and operate more agile with different types of data.

The framework is comprised of five discipline areas that could produce many best practice methodologies:

I. Business Strategy & Risk

II. Governance & Compliance

III. Prevention

This will be one of the largest sections as it is comprised of many different aspects of overall cyber security

IV. Management

V. Service Delivery & Support

Licensing

The OWASP Video 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:

What is the OWASP Video Game Security Framework?

The goal of the OWASP Video Game Security Framework is to provide an adaptable blueprint to guide the development and deployment of cyber resiliency within a video game enterprise operation.

The target audience for the project includes:

Game Publishers
Game Developers
Security Professionals
Consumer Gamers
Quality Assurance Testers
Business Stakeholders in the Gaming Industry
Industry Enthusiasts

Project Leaders

Romen Brewer

Contributors

TBD

Related Projects

Collaboration

Join the discord channel: [1]

Quick Download

COMING SOON

News and Events

April, 2019: Site Creation and Discord channel creation.

Classifications

@@ Line 111: / Line 111: @@
 == Business Strategy & Risk ==
-The following is a list of the attack surfaces that can be found in video games of various types.
+The purpose of Strategy & Risk in the framework is to layout a guiding path to creating and completing security related initiatives in gaming.
+Strategy & Risk Process
+# Establish Purpose
+# Triage Capabilities
+# Define Vision
+# Plan Next steps
+'''Establish Purpose'''
+Its important to understand in detail the goal of the overall security strategy and how can you capture requirements to ensure this phase is properly completed.
+'''What''' do we want our security posture to look like in the future?
+# Better alignment with the business Budget planning, security is apart of future business decisions
+# Improve financials decisions (Decrease spending, smarter spending)
+# Return on Investment (ROI) (competitive advantage, increase market share, consumer trust)
+#
+'''Which''' resource provider and type is this policy targeting? Example: Microsoft.Network/networkInterfaces
+'''What''' is the use case for the policy? Example: Block all Public IPs within the Dow tenant
+'''Which''' scope, such as management group, subscription, or resource group, should the policy target? ''Example:'' CloudAll
+'''Which''' policy effect? Example: Deny
+.    Disabled – Useful for testing situations or for when the policy definition has parameterized the effect. This flexibility makes it possible to disable a single assignment instead of disabling all of that policy's assignments.
+.    Append – Add additional fields to the requested resource during creation or update. Common example is adding tags on resources such as costCenter or specifying allowed IPs for a storage resource
+.    Deny – Prevent a resource request that doesn't match defined standards through a policy definition and fails the request.
+.    Audit – Create a warning event in the activity log when evaluating a non-compliant resource, but it doesn't stop the request. Can then use Azure Monitor to trigger serverless compute and automate more complex remediations.
+.    AuditIfNotExists – Enables auditing on resources that match the if condition, but doesn't have the components specified in the details of the then condition.
+.    DeployIfNotExists – Executes a template deployment for resources that match the if condition, but doesn't have the components specified in the details of the then condition.
+What is the name of the policy definition? Development environments should be Prefixed with (Dev).
+Examples: Restrict Public IP; (Dev) Deny SQL database TDE disablement
+Naming convention:
+•    Allow = “Deny” with whitelist
+•    Deny = “Deny” with blacklist
+•    Limit = "Deny" if not in specific set
+•    Enforce = "Deny" with specific expected value
+•    Restrict = "Deny” with specific unexpected value
+•    Apply = “Append”
+•    Deploy = "DeployIfNotExist”
+•    Audit = “Audit” or “AuditIfNotExists”
+•    Require = "Deploy", “Deny”, or “DeployIfNotExists”
 {| class="wikitable" style="text-align: left" border="1"

ID	Vulnerabilty Name	Description	Surface Area	Goal	Techical Impact	Business Impact	Defense	Ref	Genre
V1	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.	Game Client	Unfair Player Advantage	Player Anger	Players leave, Lost Revenue	Cryptographic Integrity Checks on Game Client	http://www.gamesradar.com/theres-a-division-damage-stacking-glitch-if-youve-got-fast-fingers/	3PS/1PS/MMO
VN1	"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, which could have been prevented by `CRYPTOGRAPHIC INTEGRITY CHECKS ON GAME CLIENT`”