🖋️
Learn Write Share
  • About me
  • Android Bits
    • The Other Side to Usability - Part 1
    • The Other Side to Usability - Part 2
    • Building a synthetic task stack of multiple activities in Android
    • Linking a text having a phone number in Android
    • DROIDCON Italy
  • Security Bits
    • Threat Modelling for AI - Changing the way you view Trust Boundaries
    • Who Do You Think Owns Your Android Application?
    • Secure Infrastructure: Tools & Techniques
    • DNS rebinding attacks - Useful resources
    • Semgrep and Dependabot in path to production - SAST and SCA Tooling
  • AWS
    • AWS account access using saml2aws and assume-role
  • MySQL
    • Setting up MySQL
Powered by GitBook
On this page

Was this helpful?

  1. Security Bits

Who Do You Think Owns Your Android Application?

PreviousThreat Modelling for AI - Changing the way you view Trust BoundariesNextSecure Infrastructure: Tools & Techniques

Last updated 4 years ago

Was this helpful?

This is the scene; on one side, we have the Android platform developers and on the other, the hackers. Just as with any software system, Android has its list of security problems. And it’s a pretty close race between the two sides.

In spite of the world’s most accomplished security professionals working on the Android platform’s, there have been cases where a user should not have ‘trusted’ the released application.

The flexible platform works on heavy collaborations between applications and dependencies can range from simple to complex. In this scenario, the dependencies are bound to be exploited to acquire data, passwords, and eventually control over the application.

In these two part series I have share my learning around security measures developers must take into consideration to avoid introducing vulnerabilities in our Android apps. You can read them below

LogoWho do you Think Owns Your Android App - Part One
LogoWho do you Think Owns Your Android App - Part Two