A security audit says card numbers, passwords, and PINs stay in process memory after they're entered and processed, so they can leak through a memory dump or a crash log. How far can you solve that in Swift and iOS?
Swift String and Data are immutable with copy semantics, so you can't control where the copies end up, and ARC deallocation doesn't wipe memory, which makes complete erasure impossible; the goal is to shrink how long and in how many places the plaintext exists.
SecurityShort answerAdvanced
In a financial app, how do you decide when a security requirement conflicts with user…
#fintech
SecurityShort answerExpert
Bots call your API directly and clear out the coupons. How do you use App Attest so the…
#secure-enclave
SecurityMultiple choiceAdvanced
Which statements about a key created with CryptoKit's…
#secure-enclave
ArchitectureMultiple choiceAdvanced
In this Coordinator implementation, LoginCoordinator stays in memory after the login flow…
#memory