Mark Xamarin as end of support

[Diolor]

Xamarin is past its EoS (end of support) https://dotnet.microsoft.com/en-us/apps/xamarin

We should mark it accordingly in all areas and remove it from other minor mentions.

.NET MAUI should be used instead.
https://dotnet.microsoft.com/en-us/apps/maui

[viso27]

Hi @Diolor,

I’ve prepared documentation updates marking Xamarin as End of Support across the relevant MASTG sections.

May I please be assigned to this issue so I can reopen the PR?

Thank you!

[Diolor]

Hi @viso27

Before we assign a ticket, we need to verify that you have relevant experience with mobile application security. Based on your profile, I don't immediately see any relevant projects. Can you share your expertise in mobile security? The company you're working for? Other relevant open source project contributions? LinkedIn profile, personal website, or similar.

We are unfortunately forced to ask for this as we are being overrun with unverified AI generations, which greatly reduce the quality of the project. Without existing experience, it's impossible to know if the AI is hallucinating or not. Are you planning to use AI?

[viso27]

Hi @Diolor

Thank you for checking and for explaining the context — I completely understand the concern around unverified AI-generated contributions.

I am a student and early-stage contributor, and my experience in mobile application security comes primarily from academic study and hands-on practice using OWASP resources (MASTG, MASVS), Android/iOS testing labs, and tools such as Burp Suite, MobSF, and static/dynamic analysis workflows.
While I may not yet have extensive professional experience, I am actively learning and contributing to open-source security documentation to build that experience.

Regarding this PR specifically the changes were made by manually reviewing existing Xamarin references in MASTG and updating them based on Xamarin’s official End of Support status . I did not rely on AI to invent new content or security guidance. AI was used only as a writing assistant for clarity and consistency, while all technical decisions, scope, and edits were manually verified against the existing documentation and official sources.

[viso27]

Hi @Diolor
Just checking in on this when you have a moment

[sushi2k]

Hi @viso27. Thanks for your interest.

The intention of this ticket, as described by Diolor is "We should mark it accordingly in all areas and remove it from other minor mentions.".

This means to remove Xamarin where it is just part of a listing in a sentence, as it's not relevant anymore. But also highlight that .NET MAUI should be used instead and that Xamarin is EoS, which can be done for example for the techniques that are specifically for Xamarin (e.g. https://github.com/OWASP/mastg/blob/master/techniques/generic/MASTG-TECH-0125.md). You can add a note about this (formatting example here:

mastg/techniques/ios/MASTG-TECH-0060.md

Line 30 in 152375d

!!! note

) right after the meta-data in the technique to summarise this.

Techniques about Xamarin can be marked as deprecated in the meta data of the technique (see line here:

mastg/tests/android/MASVS-CODE/MASTG-TEST-0042.md

Line 12 in 152375d

status: deprecated

).

Simply adding "(End of Support)" is not sufficient to work and close this ticket. I will assign the ticket to you and please update your PR accordingly.

Please also get familiar with the contribution guidelines: https://mas.owasp.org/contributing/1_How_Can_You_Contribute/#contribution-flow