Skip to content

Port MASTG-TEST-0092: Testing Simulator checks (iOS)#3737

Draft
jacobocasado wants to merge 13 commits intoOWASP:masterfrom
jacobocasado:port-v1-test-0092
Draft

Port MASTG-TEST-0092: Testing Simulator checks (iOS)#3737
jacobocasado wants to merge 13 commits intoOWASP:masterfrom
jacobocasado:port-v1-test-0092

Conversation

@jacobocasado
Copy link
Collaborator

@jacobocasado jacobocasado commented Mar 5, 2026

This PR closes #3009

Description

I'm performing the PORT for MASTG-TEST-0092.

The idea is to have a KNOW file for the iOS Simulator, and port the "simulator" detection from V1 to "virtual devices" like Corellium, which are the real threats as they work on the app store applications.


AI Tool Disclosure

  • This contribution was performed with the help of AI tooling

If AI tools were used to generate or substantially modify code or text, complete the following.

  • AI tools used: e.g. ChatGPT Codex
  • Models and versions: e.g. GPT-codex-5.3 - xhigh
  • Prompt summary: Used to refine and detect wording gaps, not to generate content.
  • Your mobile security expertise level: high

Contributor Checklist

  • I have read and understood the contributing guidelines.
  • I followed the project style guide.
  • I validated the technical correctness of my changes and understand the topic.
  • This PR adds clear value and is not spam or low-effort content.

Relevant documentation.

Contributors are expected to understand basic git and GitHub workflows, including forks, branches, commits, and pull requests. The project does not provide training. Pull requests that do not meet these minimum requirements may be closed without review.

@cpholguera cpholguera changed the title Open Port MASTG-TEST-0092: Testing Simulator checks (iOS) Port MASTG-TEST-0092: Testing Simulator checks (iOS) Mar 5, 2026
@cpholguera cpholguera marked this pull request as draft March 5, 2026 19:34

## Limitations

Some of these checks are heuristic-based and can lead to false positives; they can also be spoofed (and bypassed) with sufficient time and resources, especially on rooted devices. These techniques should be part of a defense-in-depth strategy, not a standalone solution. It is recommended to apply a layered approach with other anti-reversing techniques like detecting a jailbroken environment (@MASTG-KNOW-0084).
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haven't given more details on other protection layers, because this will be done in the BEST file. Is that OK?

Corrected spelling of 'proprietary' and 'hypervisor' in the document.
masvs_category: MASVS-RESILIENCE
platform: ios
title: Emulator Detection
title: Simulator Detection
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For Simulator, only KNOW is done, as commented with @cpholguera; it is not needed to give more detail on the Simulator as it is not a real threat from apps that are from the app store due to the build differences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MASTG v1->v2 MASTG-TEST-0092: Testing Emulator Detection (ios)

1 participant