nerdexam
CompTIA

CAS-002 · Question #257

Ann, a software developer, wants to publish her newly developed software to an online store. Ann wants to ensure that the software will not be modified by a third party or end users before being…

The correct answer is C. Remote attestation. Remote attestation cryptographically verifies a software image has not been modified before permitting it to execute on a device, directly preventing tampered copies from running.

Enterprise Security

Question

Ann, a software developer, wants to publish her newly developed software to an online store. Ann wants to ensure that the software will not be modified by a third party or end users before being installed on mobile devices. Which of the following should Ann implement to stop modified copies of her software form running on mobile devices?

Options

  • ASingle sign-on
  • BIdentity propagation
  • CRemote attestation
  • DSecure code review

How the community answered

(29 responses)
  • A
    7% (2)
  • B
    3% (1)
  • C
    90% (26)

Why each option

Remote attestation cryptographically verifies a software image has not been modified before permitting it to execute on a device, directly preventing tampered copies from running.

ASingle sign-on

Single sign-on is an authentication mechanism enabling users to access multiple services with one credential set; it does not measure or verify the integrity of software code.

BIdentity propagation

Identity propagation passes authenticated user identity across application boundaries but does not inspect or validate the cryptographic integrity of software binaries.

CRemote attestationCorrect

Remote attestation uses cryptographic measurements of software code and configuration - typically anchored in a Trusted Platform Module (TPM) - to generate a hash that is compared against the developer's known-good signed value. If the measurement does not match the expected baseline, the platform refuses to load or execute the software. This mechanism directly addresses Ann's requirement by detecting any third-party or end-user modifications before the application is allowed to run on mobile devices.

DSecure code review

Secure code review is a development-phase practice for identifying vulnerabilities in source code; it does not prevent the runtime execution of modified compiled binaries after distribution.

Concept tested: Remote attestation for mobile software integrity verification

Source: https://trustedcomputinggroup.org/resource/tpm-library-specification/

Topics

#remote attestation#code signing#mobile security#software integrity

Community Discussion

No community discussion yet for this question.

Full CAS-002 Practice