Before releasing an internal mobile app for code-enforcement officers, the city wants flaws found in source and assurance the binary is authentic. Which techniques fit?
Select an answer to reveal the explanation.
Short Explanation
Static analysis is the spell-check for source before officers install the app. Code signing is the wax seal that says this binary really came from the city. Unsigned mystery APKs from a file share are how you ship regret.
Full Explanation
Static application security testing examines source or bytecode for vulnerabilities before runtime. Code signing cryptographically associates a publisher identity with the released binary so devices can verify authenticity and integrity. Skipping both, or relying only on post-production complaints, leaves defects and supply-chain trust gaps. Using SAST plus code signing before releasing an internal municipal mobile app matches Domain 4.1 application security practice.