What is one thing a tester can do to ensure that the software is trusted and is not changing or tampering with critical data on the back end of a system it is loaded on?

Question

Options

• AProper testing
• BSecure coding principles
• CSystems security and architecture review
• DAnalysis of interrupts within the software

• A
  4% (2)
• B
  2% (1)
• C
  8% (4)
• D
  85% (41)

Explanation

Analyzing interrupts within the software reveals the low-level system calls and hardware/software interrupt requests the application makes at runtime. Malicious or poorly written software may issue unauthorized interrupts to access, modify, or exfiltrate backend data outside of its intended scope. By monitoring and analyzing these interrupts, a tester can detect unexpected or unauthorized interactions with the underlying system. Proper testing (A) and secure coding (B) are development-phase practices that do not directly reveal runtime tampering behavior. A systems security and architecture review (C) is a design-level activity that does not capture dynamic runtime behavior the way interrupt analysis does.

No community discussion yet for this question.