Frequently Asked Questions - janusSEAL suite

janusNET supports Blackberry devices.
Two whitepapers are available to enable the native classifcation capabilities of Blackberry devices (KB article), and to enable the filtering capability of the Blackberry Enterprise server (KB article).
janusNET do not have software that is installed on Blackberry devices.

janusSEAL for Outlook and janusSEAL Documents support the following operating systems

• Microsoft Windows 2000
• Microsoft Windows XP
• Microsoft Vista

Further specifications are available from the janusSEAL for Outlook and janusSEAL Documents specification pages.
 
janusSEAL for Pocket Outlook supports the following operating systems

• Windows Mobile 5
• Windows Mobile 6

Further specifications are available from the janusSEAL for Pocket Outlook specification pages.

janusSEAL for Outlook, janusSEAL for OWA and janusSEAL Documents are highly configurable using Group Policy Objects. This allows for centralised implementation of policy, such as controlling the range of classifications available according to the network’s security rating. Stock Administrative Templates are supplied for use in the Group Policy Editor. janusSEAL Schema can be used to develop more customized schemas and templates.
 
janusSEAL for Pocket Outlook is configured with the provision of a digitally signed settings installation file.

janusSEAL allows for the enforcement of policy so that documents and emails are marked in accordance with the Government Protective Marking Scheme (GPMS). (MoPI Guidance 4.2 Principles of Recording)
 
A GPMS specific schema is available for download (GPMS Schema)

By classifying documents and emails, you can use perimeter security systems to limit the egress of sensitive information.
 
janusSEAL Documents inserts the security classification marking into files as custom document properties. These properties are readable by other systems.
 
If a user attaches a document an email, janusSEAL for Outlook automatically inherits the security classification of the attachment. The user cannot set the email's classification lower than that of any attachment.
 
When the user sends the message, janusSEAL for Outlook inserts the protective marking into the email. The markings are inserted into pre-configured locations in the message, such as the subject line, X-Header and many more. These markings may be interpreted by perimeter security systems, such as email gateways, and filtered accordingly.
 
Further detail describing the structure of the custom document properties is available here, and detail of email markings is available here. (A site account is required to access these links.)
 
A whitepaper discussing the integration of janusSEAL and email gateway filtering is available here.

janusSEAL makes extensive use of Active Directory and Group Policy.
 
janusSEAL for Outlook, janusSEAL Documents and janusSEAL for OWA are configured using Group Policy Objects (GPOs). The ZIP packages for these products include a number of Group Policy Administrative Template (ADM) files for a several well known security classification schemas including those for Australian Government agencies and UK Government entities (GPMS). These Group Policy Administrative Template files are loaded into the Group Policy Editor. The domain administrator(s) use the Group Policy Editor to define one or more janusSEAL related Group Policy Objects; each Group Policy Object defines a set of secure policy settings (configuration parameters) for the janusSEAL product or products.
 
With the use of Active Directory groups (OUs) and security groups, the janusSEAL configuration can be easily customised for various machine and user groups based on which Group Policy Objects are linked with the group in Active Directory. This allows for additional capabilities for some groups, such as the ability to classify information at higher levels. Using the powerful features of Microsoft Group Policy management it is a simple matter to enable higher classifications for a group of users who have higher security clearance when working on more secure workstations. This example is fully explained in the janusSEAL product's Administration Guide.
 
Active Directory and Group Policy may also be used for deployment of the janusSEAL products to desktops in the Windows domain (or servers, in janusSEAL for OWA's case). Each product is packaged as a standard Microsoft Installer (MSI) file. With the janusSEAL MSI placed on a network fileshare, a GPO can have a link to the MSI defined under the Software Installation area of the GPO. For any machine that is in an Active Directory group linked to this GPO, the next time it reboots the janusSEAL software will be automatically installed on it.
 
janusSEAL Schema can be used to develop new organisation specific security classification schemas, or extend existing schemas. janusSEAL Schema can then be used to create Administrative Template (ADM) files for all janusSEAL products based on the schema definition. Pre-made schema definition (SCS) files, for use with janusSEAL Schema, can be downloaded from the janusSEAL Schema forum. Currently there are SCS files for use by Australian Government agencies, UK Government entities (GPMS compliant), Government of Canada agencies, Singapore Government, USA Government and a schema that complies with the Traffic Light Protocol.

Local Authorities in the United Kingdom (UK) can connect to the Government Connect Secure Extranet (GCSX) provided that have achieved Code of Connection (CoCo) compliance.
 
Products in the janusSEAL suite enable compliance against the protective marking (security labels) requirements of CoCo and of Her Majesty's Government Security Policy Framework. The janusSEAL products require senders of email messages to apply the Government Protective Marking System (GPMS) to all sent messages. This ensures all email messages are protectively marked as required by CoCo.
 
Further, by including janusSEAL for Outlook SafeDomain Extension in their GCSX architecture, Local Authorities can provide their staff with a simple single mailbox solution which is able to ensure sensitive messages (PROTECT or RESTRICTED) are always delivered by the secure GC Mail system of GCSX.
 
See this page for more information on the janusSEAL solution for CoCo compliance and simplified GC Mail.

Yes, janusSEAL products can easily be configured to use the Government Protective Marking System (GPMS) of the United Kingdom.
 
The GPMS is a security classification schema of five security classifications (in ascending order of sensitivity):

• PROTECT
• RESTRICTED
• CONFIDENTIAL
• SECRET
• TOP SECRET

The classification UNCLASSIFIED or NOT PROTECTIVELY MARKED is used for government information to assert that a protective marking is not needed because the information is not sensitive.
 
The GPMS also includes a number of descriptors that can be associated with each security classification. In janusNET's terminology for security classification schemas we would call these qualifiers.
 
janusSEAL products are supplied with a 'pre-made' security classification schema file (SCS) for the GPMS that includes these security classifications and descriptors. janusSEAL products also come supplied with 'pre-made' Group Policy Administrative Templates derived from the SCS file which are used to configure the products using Microsoft Group Policy technology.
 
Her Majesty's Government Departments, Agencies, Local Authorities and Police Forces can easily modify the 'factory supplied' GPMS security classification schema (SCS) file to meet their specific needs. They do so using the janusSEAL Schema software tool which allows them to add extra descriptors (qualifiers), change the tooltip text shown to users for each classification or change the text label for each security classification.
 
See this page for more information on how janusSEAL products can use the GPMS and how they enable compliance with the protective marking requirements of Her Majesty's Government Security Policy Framework.