Development tools and frameworks usually have options to make debugging easier for developers. Although these features are useful during
development, they should never be enabled for applications deployed in production. Debug instructions or error messages can leak detailed information
about the system, like the application’s path or file names.
Ask Yourself Whether
- The code or configuration enabling the application debug features is deployed on production servers or distributed to end users.
- The application runs by default with debug features activated.
There is a risk if you answered yes to any of those questions.
Recommended Secure Coding Practices
Do not enable debugging features on applications distributed to end users.
Sensitive Code Example
Setting isInspectable to true on a WKWebView makes it possible to inspect it using Safari’s web
inspector:
import WebKit
let webView = WKWebView()
webView.isInspectable = true // Sensitive
Compliant Solution
Setting isInspectable to false ensures that it is not possible for users to inspect the WebView.
import WebKit
let webView = WKWebView()
webView.isInspectable = false
If isInspectable has to be set to true for debugging purposes, it should be done only for DEBUG builds.
See
