This is the eleventh in a series of messages describing new features in Isode R14.4, scheduled to ship in April 2009. You can see all of the messages on this blog relating to R14.4 by clicking on this link R14.4 makes a number of updates to this infrastructure:
- Support of NATO Security Categories. Security Categories are used within Security Labels to provide finer grained control than Security Classification. R14.3 supported only US MISSI Security Categories, as defined in SDN.801c. NATO ACP 322 defines Security Categories with similar semantics to MISSI, but different syntax. R14.4 adds support for these categories, and control within the SPIF as to which syntax is used. This change means there is support for the two major definitions of Security Category, and that ACP 322 and UK JSP 457 can be fully supported.
- The Isode Security Policy has been extended to support Equivalent Policies in line with SDN.801c definitions. This enables a Security Policy to define labels from other policies that are equivalent to the local ones. These labels will then be verified according to this equivalence.
- Support of ESS Security Label formats in addition to X.501/X.411. This includes conversion between the formats.
- Security Clearances can now be included in certificates. Where there is a Security Clearance in a directory entry, Sodium can now include this in a PKCS#10 CSR (Certificate Signing Request) which will result in the Security Clearance being included with the X.509 Certificate as part of the Subject Directory Attributes Extension.
- Formal XML schema specifications of the Isode XML Security Label and Clearance formats are now provided. Basic XML style sheets are also provided. This will facilitate external use and management of data in these formats.
Comments