Let’s do it right this time: Security in Xamarin mobile apps
summary
Walks through the OWASP Mobile Top 10 with concrete fixes for Xamarin apps: shows plaintext SQLite credentials and screenshots leaking to OS cache, demonstrates authentication via Xamarin.Auth with Google OAuth, stores tokens with Xamarin.Essentials SecureStorage / AccountStore, and enforces TLS plus certificate pinning via ServicePointManager. Covers rooted-device risks, APK unzip + decompilation, limited value of obfuscation, and a working overlay blur to block background screenshots; Android emulator network hiccup prevents a live Google login demo but code-level solutions run.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:32Training by Gill Cleeren
- 4:11What is OWASP?
- 5:08OWASP Mobile Top 10
- 11:20M1: Improper Platform Usage
- 13:30M2: Insecure Data Storage
- 15:02Insecure Communication
- 24:36Insufficient Cryptography
- 27:39Insecure Authorization
- 30:35Poor Code Quality
- 31:24Code Tampering
- 33:27Reverse Engineering
- 35:32Extraneous Functionality
- 37:25114: Insecure Authentication Xamarin.Auth
- 50:38Using secure storage in Xamarin.Essentials
related talks
49mHow to Hack Your Own Mobile App
01h 02mDon’t get stung by OWASP: An intro into writing code for greater Android Security
37mPractical security for Android apps
45mTen Secrets to Secure Mobile Applications
29mSecuring Android Applications - The not so se…
46mA More Secure World for Android Apps
34mSecuring Android: Tackling Advanced Threats and Enhancing App Security
29mSecuring Android: Tackling Advanced Threats and Enhancing App Security