Different business modules may share one session. Policies should reflect each module's data and transaction risks rather than imposing one global response.
Evaluation approach
A common event model can coexist with operation-specific enforcement. Content access and wallet transactions may need different thresholds. Treat cross-module sharing and bridges as trust boundaries.
Application example
When a mini app invokes a privileged host function, verify origin and permitted action. Host integrity does not prove that loaded web content is safe.
Limits and considerations
One SDK may not cover every runtime equally. Document excluded JavaScript, dynamic content and native libraries.
Checks and decisions
- Inventory assets by module
- Constrain bridge calls
- Apply policy with transaction context
Shared protection infrastructure should not create unlimited shared authority.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.