owasp-mstg

The Mobile Security Testing Guide (MSTG) is a comprehensive manual for mobile app security development, testing and reverse engineering. (by julepka)

Owasp-mstg Alternatives

Similar projects and alternatives to owasp-mstg

  1. owasp-mastg

    The Mobile Application Security Testing Guide (MASTG) is a comprehensive manual for mobile app security testing and reverse engineering. It describes the technical processes for verifying the controls listed in the OWASP Mobile Application Security Verification Standard (MASVS).

  2. SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  3. reFlutter

    Flutter Reverse Engineering Framework

  4. android-udev-rules

    Android udev rules list aimed to be the most comprehensive on the net

  5. theos-jailed

    A Theos module to develop jailed tweaks for iOS 8 and up

  6. buildAPKs

    Really quickly build APKs on handheld device (smartphone or tablet) in Amazon, Android, Chromebook and Windows📲 See https://buildapks.github.io/docsBuildAPKs/setup to start building APKs. (by sdrausty)

  7. QuantumPuzzleGenerator

    Puzzle game for Android and iOS, written in F#

  8. website

    The elementary.io website (by elementary)

  9. neural-hash-collider

    Preimage attack against NeuralHash 💣

  10. Androl4b

    A Virtual Machine For Assessing Android applications, Reverse Engineering and Malware Analysis

  11. owasp-masvs

    The OWASP MASVS (Mobile Application Security Verification Standard) is the industry standard for mobile app security.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better owasp-mstg alternative or higher similarity.

owasp-mstg discussion

Log in or Post with

owasp-mstg reviews and mentions

Posts with mentions or reviews of owasp-mstg. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-03.
  • Google Play rolls out an "Independent security review" badge for apps
    2 projects | news.ycombinator.com | 3 Nov 2023
    I found a more detailed explanation of it: https://github.com/julepka/owasp-mstg/blob/master/Document/0...

    > Generally, you should provide compiled code with as little explanation as possible. Some metadata, such as debugging information, line numbers, and descriptive function or method names, make the binary or bytecode easier for the reverse engineer to understand, but these aren't needed in a release build and can therefore be safely omitted without impacting the app's functionality.

    I'm not a big fan of the reasoning, as it's security through obscurity. Which is not the worst tradeoff, but these days it just makes public bug bounties (and other public auditing) end up being less of an interesting prospect for improving security.

Stats

Basic owasp-mstg repo stats
1
1
10.0
over 2 years ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com