How to Detect Software Tampering After Final Version?

SY0-701 By islever Editorial Last updated

Short answer

A Hashing

Question

A company wants to ensure that the software it develops will not be tampered with after the final version is completed. Which of the following should the company most likely use?
  1. Hashing Correct Answer
  2. Encryption
  3. Baselines
  4. Tokenization

Key Takeaways

This question tests knowledge of data integrity mechanisms versus confidentiality or configuration management, with candidates often confusing hashing with baselines or encryption.

Hashing guarantees software integrity by generating unique cryptographic fingerprints to detect unauthorized modifications. The community overwhelmingly agrees that cryptographic hashing is the industry standard for verifying untampered software releases.

Common mistake: Baselines are frequently chosen because they track configuration changes, but they do not inherently provide cryptographic verification of file integrity like hashing does.

Expert Analysis

Why the Answer Is Correct

Hashing algorithms produce a fixed-size digest representing the exact contents of a file, making any alteration immediately detectable during verification. By storing the original hash securely, developers can recalculate and compare it against future copies to confirm the software remains unmodified. This aligns perfectly with Security+ objectives for maintaining application integrity post-release. Comment [2] correctly highlights how hashing creates a unique value that serves as a reliable tamper-evident mechanism.

Why the Other Options Are Wrong

Encryption focuses on confidentiality rather than integrity, meaning it protects data from unauthorized reading but does not inherently verify if the underlying software has been altered. Baselines establish reference configurations for change management but lack cryptographic validation, making them slower and less precise for detecting binary-level tampering. Tokenization replaces sensitive data with non-sensitive equivalents and is entirely irrelevant to software version control or integrity verification.

Community Comment Notes

Voters frequently split between hashing and baselines, reflecting a common conceptual overlap between cryptographic integrity and configuration tracking. Comment [3] argues baselines work for change detection, yet fails to address the cryptographic guarantee required for definitive tamper evidence. Most users ultimately recognize hashing as the correct choice, reinforcing CompTIA’s emphasis on algorithmic integrity checks over administrative baselines.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When faced with integrity-focused scenarios, prioritize hashing or digital signatures over encryption or access controls. Remember that integrity means verifying unchanged data, while confidentiality ensures secrecy and availability guarantees uptime.

Community Votes

A
75%
C
25%

75% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. jafyyy 👍 2
    A Hashing ensures integrity of software by detecting any unauthorized changes or tampering after its final version.
  2. laternak26 👍 1 Answered A
    A. Hashing: Hashing is a technique used to generate a unique, fixed-size value (hash) based on the contents of a file, such as a software application. After the final version of the software is completed, the company can create a hash of the software file and store it securely. Whenever the software is accessed or distributed, the company can recalculate the hash and compare it to the original hash. If the hashes match, the file has not been tampered with. This provides a way to verify the integrity of the software and ensure that it has not been altered after the final version. Why not C. Baselines: Baselines refer to a set of standards or configurations for systems and software that are considered secure. While baselines can be useful for ensuring that systems meet security standards, they do not directly address ensuring that the software has not been tampered with after it is finalized. Baselines help with ongoing security practices rather than tamper detection.
  3. 3b1fd98 👍 1 Answered C
    C. Baselines refer to a reference point or a final version of a system or software that is used as a standard for comparison. Once a baseline is established, any changes to the software can be detected by comparing it against the baseline version. This is crucial for ensuring that the software has not been tampered with after the final version is completed. The baseline provides a known and trusted version of the software, making it easier to spot any unauthorized modifications or tampering.
  4. qacollin 👍 2 Answered A
    A. GPT

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

CCTV and Surveillance Signs as Security Controls

S-grade

When Should an Engineer Decommission a Network Device?

S-grade

Which Controls Secure Remote Access to Sensitive PHI Applications?

S-grade

Which Zero Trust Component Belongs to the Data Plane?

S-grade

Practice All SY0-701 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SY0-701 Practice Test →

← Back to SY0-701 Study Guide