# Aligning AWS security capabilities with standards and security frameworks for the Betting and Gaming industry - Part 2

DevFeed: [Aligning AWS security capabilities with standards and security frameworks for the Betting and Gaming industry - Part 2](<https://devfeed.tech/articles/aligning-aws-security-capabilities-with-standards-and-security-frameworks-for-the-betting-and-gaming-industry-part-2-108414.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/gametech/aligning-aws-security-capabilities-with-standards-and-security-frameworks-for-the-betting-and-gaming-industry-part-2/>)

Author: Sirinda Glasgow

Published: 2026-10-30T14:37:21Z

Content type: article

Language: en

Sources: [AWS for Games Blog](<https://devfeed.tech/sources/aws-for-games-blog.md>)

Topics: [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [Security](<https://devfeed.tech/topics/security.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [federal information processing standards](<https://devfeed.tech/topics/federal-information-processing-standards.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [network security](<https://devfeed.tech/topics/network-security.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-fraud-detector](<https://devfeed.tech/tags/amazon-fraud-detector.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [amazon-sagemaker](<https://devfeed.tech/tags/amazon-sagemaker.md>), [audit](<https://devfeed.tech/tags/audit.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-cloudhsm](<https://devfeed.tech/tags/aws-cloudhsm.md>), [aws-codepipeline](<https://devfeed.tech/tags/aws-codepipeline.md>), [aws-control-tower](<https://devfeed.tech/tags/aws-control-tower.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-outposts](<https://devfeed.tech/tags/aws-outposts.md>), [aws-security-hub](<https://devfeed.tech/tags/aws-security-hub.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [aws-well-architected-framework](<https://devfeed.tech/tags/aws-well-architected-framework.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [betting](<https://devfeed.tech/tags/betting.md>), [change-management](<https://devfeed.tech/tags/change-management.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [fraud](<https://devfeed.tech/tags/fraud.md>), [games](<https://devfeed.tech/tags/games.md>), [gaming](<https://devfeed.tech/tags/gaming.md>), [gaming-industry](<https://devfeed.tech/tags/gaming-industry.md>), [generation](<https://devfeed.tech/tags/generation.md>), [geolocation](<https://devfeed.tech/tags/geolocation.md>), [industries](<https://devfeed.tech/tags/industries.md>), [information-security](<https://devfeed.tech/tags/information-security.md>), [multi-account](<https://devfeed.tech/tags/multi-account.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [security](<https://devfeed.tech/tags/security.md>), [standards](<https://devfeed.tech/tags/standards.md>)

## AI overview

GLI-19 and GLI-33 set gaming-specific expectations for areas including geolocation, random number generation, responsible gaming, anti-fraud, change management, and disaster recovery. AWS provides general-purpose infrastructure that operators can configure to support these objectives, but it does not design or certify gaming compliance solutions; operators and their licensed suppliers remain responsible for regulatory requirements, implementation, testing, and certification. Examples include Control Tower Region guardrails and API Gateway connections to selected geolocation vendors; KMS GenerateRandom and CloudHSM as general cryptographic capabilities, not gaming RNG products; analytics and machine learning services for operator-designed monitoring; CodePipeline approval gates and Step Functions incident workflows; and multi-AZ databases, cross-Region replication, AWS DRS, and AWS Backup for recovery architectures. The article recommends starting with a SIP assessment and foundational controls, then establishing jurisdiction-specific controls and continuous monitoring and testing. It emphasizes that service use alone does not establish compliance and that legal and regulatory input

## Source excerpt

In Part 1 of this series, we described how AWS security best practices, using the AWS Security Improvement Program (SIP) and the Security pillar of the AWS Well-Architected Framework, can help Betting and Gaming operators strengthen foundational cloud security, covering information security, identity and access management, audit and logging, network security, and multi-account strategy. Part 2 turns to gaming-specific controls and resilience: geolocation, random number generation, responsible gaming and anti-fraud, change management, and disaster recovery.