Question 50

Hashing best provides the functionality to ensure that a script has not been modified before it is launched.

Hashing creates a unique fixed-size string from the original data, allowing the engineer to verify the integrity of the script by comparing the hash values before and after launch.

A) Masking

Masking involves altering data to hide its original content, typically for privacy or security purposes. It does not provide a means to verify if the script has been modified, as it does not generate a unique representation of the data that can be compared for integrity.

B) Obfuscation

Obfuscation makes code difficult to understand by altering its appearance while maintaining its functionality. While this can deter tampering, it does not provide a definitive method to verify whether the script has been changed, as it does not create a unique identifier for comparison.

C) Hashing

Hashing is the correct choice as it generates a unique hash value for the script. If the script is modified in any way, the hash will change, thereby allowing the engineer to detect any alterations effectively and ensuring the script's integrity.

D) Encryption

Encryption secures data by transforming it into an unreadable format that can only be reverted to its original state with a key. However, it does not inherently provide a method to check if the script has been modified, as the original content is not directly compared.

Conclusion

Hashing is the definitive method for ensuring that a script has not been modified prior to launch, as it allows for easy verification of integrity through unique hash values. The other options—masking, obfuscation, and encryption—fail to provide this specific functionality, as they either alter the data for security or do not create unique identifiers for comparison.