This repository contains Xamarin.iOS bindings for the IOSSecuritySuite swift library.
🔒📌 Note: I highly encourage you to install BreachDetector instead, which will allow you to work in a cross platform way.
by @_r3ggi
🌏 iOS Security Suite is an advanced and easy-to-use platform security & anti-tampering library written in pure Swift! If you are developing for iOS and you want to protect your app according to the OWASP MASVS standard, chapter v8, then this library could save you a lot of time. 🚀
What ISS detects:
- Jailbreak (even the iOS 11+ with brand new indicators! 🔥)
- Attached debugger 👨🏻🚀
- If an app was run in emulator 👽
- Common reverse engineering tools running on the device 🔭
Download the package from NuGet.
Install-Package IOSSecuritySuite
After adding ISS to your project, you will also need to update your main Info.plist. There is a check in jailbreak detection module that uses CanOpenURL()
method and requires specyfing URLs that will be queried.
<key>LSApplicationQueriesSchemes</key>
<array>
<string>cydia</string>
<string>undecimus</string>
<string>sileo</string>
<string>zbra</string>
</array>
- The simplest method returns True/False if you just want to know if the device is jailbroken or jailed
if(Securing.IOSSecuritySuite.AmIJailbroken())
{
// This device is jailbroken
}
else
{
// This device is not jailbroken
}
var amIDebugged = Securing.IOSSecuritySuite.AmIDebugged() ? true : false;
Securing.IOSSecuritySuite.denyDebugger();
var runInEmulator = Securing.IOSSecuritySuite.AmIRunInEmulator() ? true : false;
var amIReverseEngineered = Securing.IOSSecuritySuite.AmIReverseEngineered() ? true : false;
Before using this and other platform security checkers you have to understand that:
- Including this tool in your project is not the only thing you should do in order to improve your app security! You can read a general mobile security whitepaper here.
- Detecting if a device is jailbroken is done locally on the device. It means that every jailbreak detector may be bypassed (even this)!
- Swift code is considered to be harder to manipulate dynamically than Objective-C. Since this library was written in pure Swift, the IOSSecuritySuite methods shouldn't be exposed to Objective-C runtime (which makes it more difficult to bypass ✅). You have to know that attacker is still able to MSHookFunction/MSFindSymbol Swift symbols and dynamically change Swift code execution flow.
- It's also a good idea to obfuscate the whole project code including this library. See Swiftshield
Yes, please!
- r3ggi for creating the swift library
- kubajakowski for pointing out the problem with
canOpenURL(_:)
method - olbartek for code review and pull request
- benbahrenburg for various ISS improvements
- fotiDim for adding new file paths to check
- gcharita for adding the Swift Package Manager support
- rynaardb for creating the
amIJailbrokenWithFailedChecks()
method - undeaDD for various ISS improvements
This binding library is licensed under MIT.
While creating this tool I used: