S90-18 practice question 13 of 15

The Data Origin Authentication pattern is applied to services throughout a service inventory. As a result, if malicious service intermediaries change data within messages exchanged by these services, such changes will be detected.

Full set: 98 questions
Answer options
A: True
B: False
Correct Answer:
TRUE
Explanation

The Data Origin Authentication pattern's primary goal is to verify the identity of the message originator. This is typically implemented using asymmetric encryption and digital signatures. A digital signature is created by generating a hash of the message content and then encrypting that hash with the sender's private key. This mechanism provides two fundamental security guarantees:
1. Authentication: Only the holder of the private key could have encrypted the hash, thus proving the origin.
2. Integrity: When the recipient validates the signature, it decrypts the hash using the sender's public key and compares it to a newly computed hash of the received message. If a malicious intermediary had altered the message data in transit, the hashes would not match. The signature validation would fail, thereby detecting the unauthorized change. Therefore, the application of the Data Origin Authentication pattern directly results in the detection of data modifications.

Why Incorrect

The statement is not False. While a separate pattern named Data Integrity focuses specifically on protecting data from modification, the mechanism used to implement Data Origin Authentication (digital signatures) inherently provides data integrity as a core feature. It is impossible to verify the origin via a digital signature without also implicitly verifying that the data has not been tampered with.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall. In the description of the Data Origin Authentication pattern, it is explained that the application of digital signatures provides both proof of origin and a guarantee of data integrity. A change in the message content will invalidate the signature, thus detecting the modification. (See Chapter 18: Message-Level Security Patterns).

2. Arcitura Education Inc. (2017). S90.09: Fundamental SOA Security Lab Manual. The lab exercises for implementing message-level security demonstrate that applying a digital signature to a SOAP message (as part of WS-Security) for origin authentication causes a fault if the message body is altered before it reaches the recipient, confirming that the change is detected. (See Lab 3: Applying and Verifying Digital Signatures).

3. Bellare, M., & Rogaway, P. (2005). Introduction to Modern Cryptography. University of California, San Diego, Course CSE 207. Chapter 10, "Message Integrity and Digital Signatures," explains that a secure digital signature scheme must be "existentially unforgeable under a chosen-message attack," which formally means that an adversary cannot produce a valid signature for any new message. This property ensures that any alteration to a signed message (which effectively creates a new message) will result in an invalid signature, allowing the change to be detected.

Scroll to Top