CloudSecurity

Using the AWS RMiT workbook and ISO Compliance Guides to support your BNM submissions


Your next Bank Negara Malaysia (BNM) notification submission needs auditable evidence of how Amazon Web Services (AWS) controls align with Risk Management in Technology (RMiT) requirements. Two resources now exist to support that work: the AWS Workbook for BNM RMiT and the compliance guides published by AWS Security Assurance Services (AWS SAS).

The AWS Workbook for BNM RMiT, available through AWS Artifact, maps each RMiT provision to AWS Control Objectives (AWS responsibilities under the AWS Shared Responsibility Model) and AWS Well-Architected Framework best practices (your responsibilities). It tells you, for every RMiT requirement, what AWS is responsible for and what you implement.

The compliance guides published by AWS SAS over the past year provide implementation guidance for International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) standards that complements the workbook. These guides show how to implement controls that meet the requirements of specific standards and frameworks using AWS services, giving your technical and compliance teams a clear path from regulatory expectation to deployed architecture.

Malaysian financial institutions can now trace from BNM regulatory requirement, through AWS control implementation, to the evidence that demonstrates it: AWS third-party attestations for AWS-side controls, and your own workload evidence for customer-side controls. BNM expects this specificity in notification documentation.

AWS Workbook for BNM RMiT

The workbook is a structured Excel document available through AWS Artifact. For each of the 394 RMiT provisions, it identifies:

  • Whether the requirement is an AWS responsibility or a customer responsibility under the Shared Responsibility Model
  • The specific AWS Control Objective that addresses the requirement (where AWS is responsible)
  • The relevant AWS Well-Architected Framework best practice for customer implementation (where the customer is responsible)
  • Supporting information and references for each mapping

The following is a sample entry from the workbook:

RMiT RequirementResponsibilitySourceAWS supporting information
10.49: A financial institution should ensure network resilience…AWSAWS Control ObjectivesAWS Control Section: Network Security. AWS maintains redundant network connectivity with multiple tier-1 transit providers across each Availability Zone.
10.49: (Customer responsibility)CustomerWell-ArchitectedREL 2: How do you plan your network topology? Implement multi-AZ deployments. Configure VPC flow logs and use AWS Network Firewall.

The workbook currently includes 394 rows across all RMiT appendix requirements, with 208 mapped to AWS responsibilities and 186 to customer responsibilities.

Why this matters now

BNM revised RMiT guidelines effective 28 November 2025, and updated them on 25 September 2026 to add requirements for National Critical Information Infrastructure (NCII) entities. Financial institutions operating under both BNM Outsourcing and BNM RMiT must demonstrate that their cloud service providers maintain controls aligned with regulatory expectations. Institutions preparing notification submissions for material cloud workloads need auditable evidence of this alignment.

The revised guidelines set higher expectations for evidence quality. Institutions submitting notifications without clear, structured control mapping evidence might face extended review cycles and requests for additional information from BNM. Workloads that could be deployed in weeks remain in governance queues for months when supporting documentation lacks the specificity regulators expect.

Compliance guides from AWS Security Assurance Services

Start with the RMiT workbook to identify which provisions AWS addresses and which you implement. Then use the following compliance guides to design and implement your customer-side controls. The guides are implementation guidance for your teams. Audit evidence comes from two places. For AWS-side controls, use AWS third-party attestations, such as ISO certificates and System and Organization Controls (SOC) reports, available in AWS Artifact. For your workload, use evidence from your own environment, including configurations, logs, and AWS Config conformance pack results. Auditors can also use the guides as a reference for how a control is typically implemented on AWS.

AWS SAS has published five compliance guides over the past year. Each guide provides control-level implementation guidance on the customer side of the Shared Responsibility Model, showing how AWS services can be configured to meet the requirements of specific standards and frameworks. These guides were written by AWS SAS practicing security assessors and auditors holding Payment Card Industry Qualified Security Assessor (PCI QSA), Certified Information Systems Security Professional (CISSP), Certified Information Security Manager (CISM), ISO 27001 Lead Auditor, and Certified Cloud Security Professional (CCSP) certifications, drawing on experience from hundreds of cloud security assessments across financial services globally.

The following is the list of guides AWS SAS practicing auditors have published, which include control mapping information relevant to BNM RMiT:

How these resources work together

A Malaysian financial institution preparing a BNM notification can use these resources together:

  • The RMiT workbook identifies which RMiT provisions are AWS responsibilities and which are customer responsibilities.
  • For AWS responsibilities, the workbook references the specific AWS Control Objective.
  • AWS third-party reports in AWS Artifact, such as the AWS ISO/IEC 27001 certificate and SOC reports, attest to those AWS Control Objectives. For customer responsibilities, the ISO compliance guides show how to implement the corresponding controls using AWS services.
  • The ISO 31000 guide can inform the risk management methodology you apply to your cloud workloads.
  • AWS Config Conformance Packs for BNM RMiT provide automated, continuous monitoring of deployed controls.

Resources also supporting this approach:

Compliance teams across Association of Southeast Asian Nations (ASEAN) financial services have already begun referencing the AWS Guide to BNM RMiT and associated resources in their cloud risk assessment processes and BNM notification documentation.

Looking ahead: AI governance

For institutions deploying generative AI and machine learning, ISO/IEC 42001:2023 (Artificial Intelligence Management Systems) is relevant to BNM technology governance expectations. In November 2024, AWS became the first major cloud provider to announce ISO/IEC 42001 certification for AI services. AWS passed its first surveillance audit in November 2025 with zero findings. The ISO 42001 compliance guide published in May 2026 supports institutions building their own responsible AI systems on their side of the AWS Shared Responsibility Model.

How to get started

  • Access the RMiT workbook through AWS Artifact and review with your compliance lead to identify which provisions apply to your material cloud workloads.
  • Download the relevant ISO compliance guides to plan how you implement your customer-side controls. Download AWS ISO certificates and SOC reports from AWS Artifact for AWS-side evidence.
  • Map your workload-specific controls using the workbook as the RMiT baseline and the ISO guides as implementation guidance.
  • Implement automated compliance monitoring using the BNM RMiT conformance pack for AWS Config to maintain continuous visibility over your control posture.
  • Engage your AWS account team or AWS SAS for additional guidance on implementing customer-side controls referenced in the workbook.

As BNM updates its regulatory expectations, AWS will update these resources to reflect revised requirements. Subscribe to the AWS Security Blog for update notifications.

Additional resources

If you have questions about this post, contact AWS Support or start a new thread on AWS re:Post.


Jonathan Jenkyn

Jonathan (JJ) is a Senior Security and Compliance Solutions Architect with AWS Security Assurance Services and a published cybersecurity author. He has over 30 years of experience across penetration testing, incident response, cyber resilience, and security governance. He helps customers build practical security programs. He champions disability inclusion and neurodiversity at Amazon. Outside work, he runs, cycles, swims, and enjoys family time.

Matthew Nixon

Matthew Nixon

Matt is a Principal in the AWS Asia Financial Services Security and Compliance team. He has 20 years of experience in technology risk, audit, and information security, including leading a cloud risk team in financial services. Matt co-founded an award-winning AI/ML startup, authored books on IT and cloud risk, and won the Singapore ISACA 2024 IT Risk Leader Award.



Source link