Testing Information

Introduction

This document describes the objective and provides the testing scripts necessary for a Candidate to demonstrate that their system configuration meets the S.E.E. Mail Business Requirements.

Objective

To demonstrate that the system submitted for testing will:

• Provide a trusted environment in which Participating Agencies can confidently transmit information classified up to 'SENSITIVE' classification (or its equivalent), by email.

• Interoperate as expected with all other "S**MAIL" Participating Agencies .

• Interoperate as expected with "XS**MAIL" External Agencies.

Implementation

Testing requires at least two implementations of S.E.E. Mail (the Candidate's implementation and one other) to carry out the tests. At various points of the Site Certification process the implementations may be, at the S.E.E. Manager's direction, one or more of:

• An Implementation of Accredited Software designated by the S.E.E. Manager as a Reference Test Server for a particular instance of the Site Certification process, and/or

• Two implementations of the proposed software implemented by the Candidate and/or

• Implementations of Accredited Software in Participating Agencies or elsewhere that have been designated by the S.E.E. Manager as Operational Reference Sites for a particular instance of the Site Certification process, and/or

• Implementations of Accredited Software within a laboratory environment designated by the S.E.E. Manager as suitable for a particular instance of a Site Certification process.

The Candidate should address any local configuration issues, such as content or virus checking, separately.

Message Types

A "normal" message is plain US-ASCII text and/or attachments encoded in MIME format.

Use of S.E.E. Mail Warnings

Agencies must use the generic S.E.E. Mail Warnings. They are permitted to append an additional line, referring their users to a link for additional information e.g. "For further information on this error, click here, http://www.agency.govt.nz/seeinfo/warning5.html".

The agency can decide whether further rules will be checked OR processing will stop. IF further rules are checked, it is permitted that further warning messages are generated.

Decryption Failures

When a message cannot be decrypted, the receiving agency should treat the message as per their policy for unknown encrypted messages. This may mean the original message is NOT attached to the S.E.E. Mail warning for the recipient.

Out of scope

The following scenarios are not tested:

• Handling of encrypted messages, that were encrypted by a non S.E.E. Mail sender

• Alteration of contents of S.E.E. Mail encrypted message, in transit.

• Mail loops caused by a S.E.E. Mail recipient auto-forwarding a message containing "[S**MAIL]" to an external address.