Frequently Asked Questions

janusGATE Mobile production licenses are provided on a perpetual basis. Fully functional time limited evaluation licenses are also available.

Seats are counted on a per network account basis.

• one person with one network account with two phones accessing the same mailbox will count as one seat.
• one person with one network account accessing their own mailbox and a common mailbox (eg ) will count as one seat.
• one person with two network accounts will count as two seats.

License are provided within specific bands of seats. For example, smaller organisations would order a license for up to 100 seats, and larger organisations with a license up to 1,000 or 10,000 seats.

Contact janusNET for further information.

janusGATE Mobile is available for evaluation with a time limited license.

1. If you do not have a web account with janusNET, you can request one by registering here.
2. Once you have your janusNET web account, you need to login, and then you can download a copy of janusGATE Mobile here.
3. You will also need an evaluation license key. These are available here.

A range of Knowledge Base articles to aid evaluation and configuration is available here.

janusGATE Mobile operates with the following smartphones:

• Windows Mobile 6 and higher
• iPhone 3 and 4
• Android 2.1 and 2.2
• Symbian (S60 3rd Edition or later with Mail for Exchange)
• Blackberry with Exchange e‑mail client

Further specifications are available here.

janusGATE Mobile operates with:

• Microsoft Exchange Server 2007
• Microsoft Exchange Server 2010

Further specifications are available here.

In most cases janusGATE Mobile does not require any additional software to be installed on the smartphone and uses the native e-mail application.

For iPhone, Windows Mobile and Android no additional software is required. These smartphones all have e-mail applications on the phone which utilise Exchange ActiveSync to synchronise e-mail, calendar and contacts between the Exchange server and the phone.

Many Nokia/Symbian smartphones come with Mail for Exchange. If not already present, it can be download from the Ovi store. Mail for Exchange utilises Exchange ActiveSync to synchronise e-mail, calendar and contacts between the Exchange server and the phone.

Blackberries require an Exchange e-mail client.

None.

janusGATE Mobile does not require any changes to the existing smartphone Exchange account configuration nor to the network settings.

janusGATE Mobile does not interfere with the mechanism used to connect the smartphone to MS Exchange Server. The enterprise can use well known and established security methods such as TLS or IPSec for channel authentication and encryption.

None.

janusGATE Mobile does not require any changes to the firewall configuration. janusGATE Mobile does not interfere with the mechanism used to connect the smartphone to  Exchange Server. The enterprise can use well known and established security methods such as TLS or IPSec for channel authentication and encryption.

In Outlook select the Tools menu and then Options...
From the Options dialog choose the janusSEAL tab which contains the product and licence information for your installed version of janusSEAL for Outlook.

The security classification drop down menu will not be available if Outlook has been set to use Microsoft Office Word to edit email messages.
This feature can be turned off in Outlook by going: Tools > Options... and choose the Mail Format tab. In this dialog, deselect both Use Microsoft Word to edit e-mail messages and, Use Microsoft Word to read Rich Text e-mail messages.

Please always consult the Administration Guide supplied with the latest version as this will contain comprehensive upgrade instructions.

Yes. In the ABNF syntax used by the standard, janusSEAL products can create subject line forms according to:

  protective-mark-short-form        = classification              ; as defined in
                                                                  ; AGIMO Protective
                                                                  ; Marking standard  
  jS-2-protective-mark-medium-form  = protective-mark-short-form
  jS-2-protective-marked-subject    = "Subject:" unstructured
                                        "[" jS-2-protective-mark-medium-form
                                        "]" [FWS] CRLF

Yes. In the ABNF syntax used by the standard, janusSEAL products can create X-header forms according to:

  protective-mark-short-form        = classification              ; as defined in
                                                                  ; AGIMO Protective
                                                                  ; Marking standard  
  jS-2-protective-mark-medium-form  = protective-mark-short-form     
  jS-2-protective-mark-long-form    = version
                                        comma-FWS namespace
                                        comma-FWS jS-2-protective-mark-medium-form
                                        comma-FWS origin
  jS-2-protective-marked-header     = "X-Protective-Marking:"
                                        [FWS] jS-2-protective-mark-long-form
                                        [FWS] CRLF

Yes.

To control the order of the message classifications as shown in the janusSEAL for Outlook Lite Classification Dialog simply edit the order of the classifications in the classifications XML file that is deployed at the client workstations.

The order of the message classifications in the Dialog, and in Outlook 2007 Professional's "permissions drop-list", is dictated by the order of the classifications in the XML file.

Use a text editor like Notepad to edit the XML file and careful adjust the ordering to that desired. Be careful to make a backup copy of the original XML file so you can readily revert to a working XML file if necessary. The new classifications XML file will have to be re-deployed to all client workstations.

Quick answer: automatically by janusSEAL for Outlook Lite.

Long answer: janusSEAL for Outlook Lite does so automatically because it uses the same configuration information used for Exchange 2007 message classifications. When configuring Exchange 2007 message classifications there is no setting for assigning short-cut keys for each message classification. janusSEAL for Outlook Lite that attempts to automatically and uniquely assign a short-cut key to each message classification.

Firstly, a character can become a short-cut key if it is:

1. unique in the dialog; and
2. alphabetic
   [a-z, A-Z]

janusSEAL for Outlook Lite iterates through each of the classifications and attempts to assign a short-cut key for each classifcation as follows. Once a short-cut key is assigned to a classification, or gives up looking for one, janusSEAL for Outlook Lite looks for a short-cut key for the next classifcation.

1. if message classification name is empty then no short-cut key is assigned;
2. if the first character of message classification name is valid, then assign it;
3. if the first character of next word in message classification name is valid, then assign it, otherwise try using the first character of each subsequent word;
4. if the second character of the first word is valid, then assign it, otherwise try using each subsequest character;
5. no valid character is available for this classification, so don't assign one.

janusNET have a solution that simplifies this administration task. The janusNET approach provides a means in which the classifications XML file and the registry settings required by Outlook 2007 or Outlook 2010 and janusSEAL for Outlook Lite can be centrally deployed and administered.

If you require more information about this solution then contact janusNET today.

janusSEAL for Outlook Lite is an Outlook add-in which enhances the native message classification capabilities of Outlook 2007/2010. janusSEAL for Outlook Lite uses the same configuration parameters for its message classifications as used by Outlook 2007/2010.

Once native message classifications are successfully working in Outlook 2007 Professional or Outlook 2010 Professional Plus, janusSEAL for Outlook Lite will be able to use the same information.

Detailed instructions for configuring native message classifications in Outlook 2007 are provided by Microsoft at http://technet.microsoft.com/en-us/library/aa998271.aspx

Yes.

In the janusSEAL for Outlook Lite Classification Dialog (popup), the end-user can obtain helpful descriptions of each message classification when they hover the mouse cursor over the classification. When they do so a tooltip is shown for a brief interval which can help the sender be sure they are using the correct message classification.

The text used for the tooltips is determined by the SenderDescription field that was assigned to the message classification when it was created on the Exchange 2007 Server in the Exchange Management Shell.

If you want to add or modify the SenderDescription field for a message classification then an Exchange Server administrator will have to use the Set-MessageClassification cmdlet in the Exchange Management Shell (see http://technet.microsoft.com/en-us/library/bb125250.aspx). Once the SenderDescription field(s) have been corrected then a new classifications XML file will have to be created and deployed to all end-user workstations.

Yes.

With Outlook 2007 Professional and native Exchange 2007 message classifications, meeting organisers cannot apply a message classification to appointment requests. However janusSEAL for Outlook Lite addresses this shortcoming. When the organiser goes to send an appointment request the janusSEAL for Outlook Lite Classification Dialog is shown and the request is only sent once a message classification has been specified.

janusSEAL for Outlook Lite writes the same classification labels to the sent message as when the sender uses the native message classifications of Outlook 2007 Professional or Outlook 2010 Professional Plus in an Exchange 2007/2010 environment. When the message is sent through the Exchange 2007/2010 Server it cannot tell whether the classification labels were written by the native classification capability of Outlook or janusSEAL for Outlook Lite.

This means any Exchange Server Transport Rules that rely on detection of a message classification will work for those classification labels written by janusSEAL for Outlook Lite.

janusSEAL for Outlook Lite cannot write other forms of classification labels like Subject line markings, X-header markings (X-Protective-Marking), Outlook User Properties, message body markings and so on. If you need to apply such labels or markings at the Outlook client then you need to use janusSEAL for Outlook.

janusSEAL for Outlook Lite is supplied as a Microsoft Installer (MSI) file.

This is the optimum format for:

• manual desktop installations
• centrally administered Group Policy installations
• centrally administered Systems Management Server (SMS) / Microsoft Operations Manager (MOM) deployments

Yes.
 
Version 2.1 of janusSEAL for OWA does require a license to successfully operate. Your organisation would have been supplied with license details when you purchased janusSEAL for OWA, or if evaluating the product janusNET would have sent you an evaluation license. These details must be supplied to janusSEAL for OWA via Group Policy administration.
 
Version 2.0 did not require a license to operate so if upgrading from that version be sure to specify the license details in Group Policy as part of the upgrade.

No.
janusSEAL for OWA will reject a janusSEAL for Outlook license. It will only successfully operate with a valid janusSEAL for OWA license.

There are two main possible causes for this:

1. the IIS World Wide Web Publishing Service has not been restarted, or
2. page caching at the web client

 
The first is the most likely cause. After making any changes to a janusSEAL for OWA Group Policy Object it is best to:

1. On the Exchange Server, bring up the Services manager via Start > Settings > ControlPanel > Administrative Tools > Services
2. In the list of services, select the World Wide Web Publishing Service
3. In the Microsoft Management Console toolbar, click the Restart Service button

 
If this does not resolve the problem then it may be due to content caching at the Web browser. Please consult the janusSEAL for OWA Administration Guide - Chapter "Administration Tasks"; Section "Troubleshooting Issues" for guidance on clearing the cache in a web client.

To determine the version of janusSEAL for OWA that is installed on an Exchange server:

1. Log onto the Exchange server
2. Open the Control Panel from Start > Programs > Control Panel
3. Open the Add or Remove Programs menu item
4. In the list of installed programs find janusSEAL for OWA
5. Click on the janusSEAL for OWA item so that it is selected in the list of installed programs
6. Against the listing of the janusSEAL for OWA installation item, the major and minorversion numbers will be visible as part of the product name.
7. To determine the point release and build numbers of the janusSEAL for OWA instance,click on the link "Click here for support information"
8. The precise version number information is available against the Version field of thedialog and is of the form M.N.P.R where M is the major version number, N is the minorversion number, P is the point release version number and R is the revision number

Yes.
Security update KB950159 for Exchange Server 2003 SP2 does not change the Outlook Web Access files that janusSEAL for OWA hooks into, so if you have an Exchange 2003 SP2 server upon which janusSEAL for OWA 2.1 is working there should be no issue with installing this security update on the server.
 

Yes.

Security update KB959897 for Exchange Server 2003 SP2 does not change the Outlook Web Access files that janusSEAL for OWA hooks into, so if you have an Exchange 2003 SP2 server upon which janusSEAL for OWA 2.1 is working there should be no issue with installing this security update on the server.

The Microsoft Knowledge Base article page has a listing of all the files which are modified by the security update and none of those files are used when integrating janusSEAL for OWA with the Exchange system.

janusSEAL for Pocket Outlook provides email protective marking capabilities for your mobile workforce. Its main features are:

• forces the end-user to classify each message before it is sent by prompting with a security classification dialog
• adds security classification protective markings to sent messages
• prevents end-users from reading, replying to or forwarding messages above a configurable threshold
• informs the end-user of the security classification of the message they are about open and gives them the option not to open it.
• operates on Windows Mobile 5 and 6

Further information is available from the janusSEAL for Pocket Outlook features page.

Security classifications are the terms used to classify (categorise) information according to its sensitivity or criticality to a business, organisation or entity. They tend to be broad categorisations, for example PUBLIC as opposed to CONFIDENTIAL information.

Qualifiers are a finer level of detail about one or more security classifications which does not necessarily change the broader sensitivity of the information. The qualifier provides some additional detail about a subject area of the information that may be relevant to the sender, recipient or an IT system. So, for example a qualifier may be COMPANY for when the information is related to something about the COMPANY. In the context of protective markings, the qualifier is not valid on its own but is bound to one or more security classifications via qualifier associations.

Qualifier associations are used to bind a qualifier to one or more security classifications. Hence the security classification may have an additional level of qualifying information about it, in the form of a qualifier. So going back to our examples, an organisation may choose to bind the qualifier COMPANY to the security classification CONFIDENTIAL. Then when used in a janusSEAL product the end-user could choose to select a marking of just CONFIDENTIAL, or they may choose to also indicate that it is CONFIDENTIAL information about the company and so mark it CONFIDENTIAL:COMPANY (by selecting CONFIDENTIAL + qualifier of COMPANY). The associations define which qualifiers are bound to which security classifications.

Whether this additional qualifier information is used by IT systems to enhance DLP rules is up to the organisation. We have seen some that would just adopt the simple rule 'do not let out any CONFIDENTIAL information via clear-text Internet email' whereas others might say 'let out CONFIDENTIAL information via Internet email unless it is CONFIDENTIAL:COMPANY information'.

Qualifiers are definitely needed in the gov.au security classification schema as they have the IN-CONFIDENCE security classification which can have any number of optional qualifiers such as COMMERCIAL-IN-CONFIDENCE, LEGAL-IN-CONFIDENCE, STAFF-IN-CONFIDENCE and so on. These all have the same broad sensitivity but the qualifier is used to convey more detail about the subject matter and could be used for fine adjustments in DLP-like rule-sets.

Caveats are related to concepts in military messaging and are another means to convey finer grain detail about the context or nature of certain information. Commercial organisations would have little need to use caveats. janusSEAL products have limited support for such.