Review and enhance iOS Binary Protections

[cpholguera]

Task

enhance the following Test Case:

https://github.com/OWASP/owasp-mstg/blob/master/Document/0x06i-Testing-Code-Quality-and-Build-Settings.md#make-sure-that-free-security-features-are-activated-mstg-code-9

using this article:

https://sensepost.com/blog/2021/on-ios-binary-protections/

Summary

The decision regarding which protections can and should be enabled is heavily influenced based on if Swiftlang is involved and whether the target binary is an executable or a library.

• PIE – Add the -fPIC compiler flag to the projects build settings. This will only be applicable to the main executable.
• ARC – This will be automatically enabled for Swift only projects (via the swiftc compiler), and added by setting YES to the Objective-C Automatic Reference Counting section in the projects configuration.
• Canary – Enabled by adding the -fstack-protector-all compiler flag to Objective-C projects. If Swift is involved its possible to have it enabled when the library is a hybrid of Objective-C and Swift, but it could show as disabled which is okay.
• Both static and dynamic analysis are possible

[su-vikas]

You can assign this to me

[cpholguera]

This will also make a nice replacement for what was removed in #1900