AWS wellarchitected documentation change
Summary
Removed entire content including incident response best practices for player misconduct, abusive behavior handling, and account banning procedures.
Security assessment
The change deletes security documentation but provides no evidence of addressing a specific vulnerability. The removed content described standard security practices (incident response planning) without indicating any flaw or incident.
Diff
diff --git a/wellarchitected/latest/games-industry-lens/games-sec-bp-incid-resp.md b/wellarchitected/latest/games-industry-lens/games-sec-bp-incid-resp.md index be90d08f1..8b1378917 100644 --- a//wellarchitected/latest/games-industry-lens/games-sec-bp-incid-resp.md +++ b//wellarchitected/latest/games-industry-lens/games-sec-bp-incid-resp.md @@ -1 +0,0 @@ -[](/pdfs/wellarchitected/latest/games-industry-lens/games-industry-lens.pdf#games-sec-bp-incid-resp "Open PDF") @@ -3,36 +1,0 @@ -[Documentation](/index.html)[AWS Well-Architected](https://aws.amazon.com/architecture/well-architected/)[AWS Well-Architected Framework](games-industry-lens.html) - -# Incident response - -GAMESEC04 - How are you defining and enforcing policies to respond to player misconduct and abusive behavior? ---- - -**GAMESEC_BP10 - Implement an incident response plan to handle bad actors and abusive behavior.** - -Refer to the Well-Architected Framework whitepaper for best practices in [[**incident response**](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/incident-response.html)](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/data-protection.html) for security that apply to games workloads. - -**GAMESEC_BP11 - Ban accounts associated with bad actors.** - -If left unmitigated, abusive behavior in a game can continue to cause impact to the gaming experience for others and should be mitigated as soon as possible. You should implement a process to impose bans, or other forms of restrictions, on bad actors who are confirmed to be in violation of your terms of service. Typically, the rules and evaluation process for determining the circumstances for imposing these types of restrictions will be determined by personnel such as a player community team, or trust and safety team, within your organization. After bad actors have been flagged, you should have a pre-determined workflow that can be run to take action on the identified players. AWS Step Functions and Lambda functions can be used to run an automated workflow that accepts a batch of player accounts as input and updates entries in a DynamoDB table called `Bans`, which can include details on the player account, the ban reason, and duration. Depending on the way your game and account management system is designed, and the type of abuse, it is valuable to have a banning system of record that is separate than you account management system. You may not want to turn off the player's account from your account management system, opting instead to simply turn off their ability to play your game. This can be useful in situations where the player's account credentials are used to access multiple games with different terms of service or policies. - - **Javascript is disabled or is unavailable in your browser.** - -To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. - -[Document Conventions](/general/latest/gr/docconventions.html) - -Data protection - -Resources - -Did this page help you? - Yes - -Thanks for letting us know we're doing a good job! - -If you've got a moment, please tell us what we did right so we can do more of it. - -Did this page help you? - No - -Thanks for letting us know this page needs work. We're sorry we let you down. - -If you've got a moment, please tell us how we can make the documentation better.