Security Considerations - Initial Proposal

The following is an initial proposal for text for a security
considerations section for WS-Addressing. We may need to add stuff to
this, but I think this provides a 'minimum bar'.

Comments welcome,



Security Considerations

EPRs SHOULD be integrity protected to prevent tampering. Such integrity
protection can be provided by transport or message level signatures.

Users of EPRs SHOULD only use EPRs from sources they trust. In practice
this is likely to mean that users of EPRs only use EPRs that are signed
by parties the user of the EPR trusts.

WS-Addressing headers (wsa:To, wsa:Action including those
headers present as a result of processing ReferenceParameters in an EPR
SHOULD be integrity protected. Such integrity protection can be provided
by transport or message level signatures.

To prevent information disclosure EPR issuers SHOULD NOT put sensitive
information into wsa:Address values or Reference Parameters. 

In addition to the above, the following text needs to be in a normative
section of the spec, probably in the SOAP binding somewhere. We really
need to do this otherwise we'll have to define a WS-A normalization
algorithm and I'd much rather not do that...

To avoid breaking signatures, intermediaries MUST NOT change the XML
representation WS-Addressing headers. Specifically, intermediaries MUST
NOT remove XML content that explicitly indicates otherwise-implied
content, and intermediaries MUST NOT insert XML content to make implied
values explicit. For instance, if a RelationshipType attribute is
present with a value of "", an
intermediary MUST NOT remove it; similarly, if there is no
RelationshipType attribute, an intermediary MUST NOT add one.

Received on Monday, 21 February 2005 15:09:59 UTC