3.5  Security Considerations in an OpenVMS Galaxy
       Computing Environment

  OpenVMS Galaxy instances executing in a shared-
  everything cluster environment, in which all security
  database files are shared between all instances, automati-
  cally provide a consistent view of all Galaxy-related security
  profiles.

  If you choose not to share all security database files through-
  out all Galaxy instances, a consistent security profile can only
  be achieved manually.  Changes to an object's security profile
  must be followed by similar changes on all instances where
  this object can be accessed.

  Because of the need to propagate changes manually, it is un-
  likely that such a configuration would ever be covered by a
  US C2 evaluation or by similar evaluations from other au-
  thorities.  Organizations that require operating systems to
  have security evaluations should ensure that all instances in
  a single OpenVMS Galaxy belong to the same cluster.