Security : protect the body of your app
summary
Shows concrete defenses: implement TLS pinning and AES payload encryption, remove plaintext endpoints and hide strings so the binary reconstructs them at runtime, detect jailbreak by checking for cgi and unusual files, and use ix guard to apply API renaming, control‑flow flattening and runtime string deciphering. Swift inlining covers about 90% automatically and devs must inline the remaining 10%. Switching frameworks to static libraries removes .framework folders and can increase binary size ~16–20%. Use Apple DeviceCheck to validate device tokens server‑side.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:43Bad Practices
- 5:34Swift Inline Features
- 7:00Api Renaming
- 8:16Jailbreak Detection
- 9:22Static Libraries
- 9:44Example To Find and Locate Frameworks
- 10:36Control Flow
- 12:20Code Integrity
- 15:42How To Install It
- 18:43How Can You Debug an Obfuscated App
- 20:40What Kind of Issue Can the Device Checker of Provided by Apple Can Detect
related talks
43miOS Application Defense - iMAS
27miOS Attack Vectors and how to protect your app
45mTen Secrets to Secure Mobile Applications
44mPractical Security
47mSecurity Threats & Mitigations for iOS Developers
49mContain Yourself: Building Secure Containers for Mobile Devices
37mOutsmarting Hackers before your App gets pwn'ed
52mBehind the Scenes of iOS Security