ebBP 2/3/2005: Additional Criteria for Pattern Matrices: DocumentSecurity

["Monica J. Martin" <Monica.Martin@Sun.COM>]

In line with Tuesday's session (this is the last one from the meeting 
minutes), we discussed the pattern criteria. One area is guaranteed 
delivery and the other is the assumptions surrounding the business 
document (Document Envelope Type). I'd like to encourage your comments 
on this proposed change to my conclusion and offer other solutions if 
required. Reference Section 4.7.5 Document security (wd 06):

4.7.5 Document security
FROM:
The value of isConfidential, isTamperDetectable, isAuthenticated at the 
Document Envelope always applies to the primary Business Document. It 
also applies to each of the attachments unless specifically overridden 
at the Attachment level. These parameters can have four possible values: 
none, transient, persistent, transient-and-persistent.

    * The communications channel used to transport the Message provides
      transient authentication. The specific method will be determined
      by the communications protocol used.
    * Persistent authentication means the Business Document signer’s
      identity SHALL be verified at the receiving application level.
      Authentication assists in verification of role identity of a
      participating party.
    * Transient confidentiality is provided by a secure network
      protocol, such as SSL as the document is transferred between two
      adjacent ebXML Messaging Service (MSH) or other transport
      messaging nodes.
    * Persistent confidentiality is intended to preserve the
      confidentiality of the message such that only the intended party
      (application) can see it. The message SHALL remain in encrypted
      form after it is delivered to the messaging node and will be
      decrypted only by the authorized application. S/MIME MAY be used
      to provide that functionality, independent of the transient
      confidentiality.
    * Transient isTamperDetectable is the ability to detect if the
      information has been tampered with during transfer between two
      adjacent MSH nodes.
    * Persistent isTamperDetectable is the ability to detect if the
      information has been tampered with after it has been received by
      messaging node, between the messaging node and the application.
      Tamper detection assists in verification of content integrity
      between and within a participating party.

TO:
all above - [add at the end of this section]
As with reliability, the parties may establish the assurance parameters, 
for example. Agreements may be relevant to establishing these 
capabilities (See earlier subsections in Section 4 for further detail). 
If non-repudiation of content is required, these attributes SHOULD be 
enabled (i.e. the enumeration selected for each of these values is other 
than 'none.'). Typically, this occurs in intentional situations.