Policies to suit security requirements

Options

Requirement

Clients has keys

Username Token

Single message

Multiple messages (SC)

Single message

Multiple messages (SC)

Authentication Only

2

9

1

N/A

Integrity only

2

9

4

12

Confidentiality only

3

10

5

13

Confidentiality & Authentication

3

10

7

14

Confidentiality & Integrity

3

11

6

12

Confidentiality & Integrity & Authentication

3

11

8

15

Non-repudiation

2

Not Possible with SC

Not Possible

Not Possible

Policy

Description

Available now

1

Transport Binding, Username Token

YES

2

Asymmetric Binding, Sign Body and Headers

YES

3

Asymmetric Binding, Sign Body and Headers, Encrypt Body

YES

4

Symmetric Binding, Sign Body and Headers

NO

5

Symmetric Binding, Encrypt Body

NO

6

Symmetric Binding, Sign Body and Headers, Encrypt Body

NO

7

Symmetric Binding, Encrypt Body, Username Token

NO

8

Symmetric Binding, Sign Body and Headers, Encrypt Body , Username Token

NO

9

Secure Conversation - boot strap policy 3, Sign Body and Headers

NO

10

Secure Conversation - boot strap policy 3, Encrypt Body

NO

11

Secure Conversation - boot strap policy 3, Sign Body and Headers, Encrypt Body

NO

12

Secure Conversation - boot strap policy 6, Sign Body and Headers

NO

13

Secure Conversation - boot strap policy 6, Encrypt Body

NO

14

Secure Conversation - boot strap policy 8, Encrypt Body

NO

15

Secure Conversation - boot strap policy 8, Sign Body and Headers, Encrypt Body

NO

WSAS 2.1 has some policies not mentioned above.