# AASE: adversarial attack simulation exercises in Singapore

Framework, read 16 November 2026

**The short answer.** AASE is the red team method for Singapore's financial industry, set out in guidelines from the Association of Banks in Singapore (version 1 in 2018, current edition September 2024). The Monetary Authority of Singapore's January 2021 guidelines say a firm should perform such an exercise. Read 16 November 2026.

## What is AASE?

AASE stands for adversarial attack simulation exercises. The Association of Banks in Singapore guidelines set out the method for the financial industry, and the Monetary Authority of Singapore's Technology Risk Management Guidelines of January 2021 say a financial institution should perform an adversarial attack simulation exercise to test its cyber defense and response plan.

The MAS guidelines add that the objectives, scope and rules of engagement should be defined first and the exercise run in a controlled way under close supervision. The detailed method is an industry guideline, not a regulator rule.

## What are the AASE phases?

Five: planning, attack preparation, attack execution, exercise closure and post-exercise actions. Planning defines goals, scope and parameters, risk management, provider selection, concessions and communications. Execution uses a test and halt model in which the exercise director can proceed, pause or end. Closure covers clean-up, reconciliation, an attack and defense joint replay and the reports.

## How often and how long?

The guidelines recommend an exercise at least once every 24 months, with the option of every 12 months, chosen on risk. A large institution may run a cycle of four to six months for complex scenarios, including attack modeling. Some choose continuous simulation, and exercises can be open-ended until goals are met.

## What does AASE say about providers?

Providers should give assurance on methodology, data handling, criminal background checks for consultants, and adequate insurance and indemnity. Reputation, experience, references and recognized accreditations count. The guidelines list technical areas such as cloud, DevOps, Internet of Things and operational technology, and defense evasion.

The provider should ask for consent before high-risk actions and report signs of a real attack at the same time.

## Related pages

- [Red team frameworks by regulator: TIBER-EU, DORA, CBEST, iCAST, AASE and CORIE](/frameworks/)
- [Red team vs penetration testing: goals, scope and secrecy](/compare/red-team-vs-penetration-testing/)
- [Emergency stop and deconfliction in a red team test](/engagement/emergency-stop-and-deconfliction/)
- [What to ask a red team provider: twelve questions and why](/services/what-to-ask-a-red-team-provider/)
- [Red team legal authorization: the letter and the law](/engagement/red-team-legal-authorization/)
- [Red team for financial services: what regulators ask of a red team](/services/red-team-for-financial-services/)
- [CBEST: the Bank of England's threat intelligence-led assessment](/frameworks/cbest/)
- [CORIE: Australia's Cyber Operational Resilience Intelligence-led Exercises](/frameworks/corie/)

## Sources

- Association of Banks in Singapore, Red Team: Adversarial Attack Simulation Exercise Guidelines, September 2024: https://abs.org.sg/docs/library/abs-red-team-adversarial-attack-simulation-exercises-guidelines----september-2024.pdf (read 16 November 2026)
- Monetary Authority of Singapore, Technology Risk Management Guidelines, January 2021: https://www.mas.gov.sg/-/media/mas/regulations-and-financial-stability/regulatory-and-supervisory-framework/risk-management/trm-guidelines-18-january-2021.pdf (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://redteamvsblueteam.com/frameworks/aase/
