skip book previous and next navigation links
go up to top of book: HP OpenVMS Alpha Partitioning and Galaxy Guide HP OpenVMS Alpha Partitioning and Galaxy Guide
go to beginning of chapter: OpenVMS Galaxy Concepts OpenVMS Galaxy Concepts
go to previous page: Clustering with Galaxy Clustering with Galaxy
go to next page: Configuring OpenVMS Galaxy Instances in Time ZonesConfiguring OpenVMS Galaxy Instances in Time Zones
end of book navigation links

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 among all instances, automatically provide a consistent view of all Galaxy-related security profiles.

If you choose not to share all security database files throughout 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 unlikely that such a configuration would ever be covered by a US C2 evaluation or by similar evaluations from other authorities. Organizations that require operating systems to have security evaluations should ensure that all instances in a single OpenVMS Galaxy belong to the same cluster.


go to previous page: Clustering with Galaxy Clustering with Galaxy
go to next page: Configuring OpenVMS Galaxy Instances in Time ZonesConfiguring OpenVMS Galaxy Instances in Time Zones