Implementing Windows Security

This section describes those considerations or tasks that are available within Windows when implementing mvBase security. This section assumes that the following prerequisites have been met.

Windows Prerequisites

Windows must be properly installed on each network system, and proper domains must be previously defined in order to define additional security measures from within Windows.
The administrator must already be familiar with the methods of defining user-based Windows security measures, such as passwords, permissions, rights, and varying access types (e.g., Read-Only or Full). This requires additional documentation or training.

This section covers the following topics:

Securing Virtual Memory Storage Files	Explains why virtual memory storage files should be protected, and describes the potential means of protecting such files using Windows tools.
Securing the mvBase Server System	Explains the relationship between the mvBase Server system and remote virtual memory storage files on one side and remote mvBase clients on the other, and describes the potential means of protecting the Server system.
Securing the mvBase Workstation System	Explains the relationship between the mvBase Workstation and remote Server systems, and describes the potential means of protecting the Workstation system.

The first element of system-level security is Windows. Assuming that proper user rights and permissions are already defined for all Windows users and objects on the network, subsequent installation of mvBase creates these considerations that may impact or modify the (intended) security scheme.

Virtual memory storage files must remain accessible to the mvBase Server system(s) and administrator(s), but possibly protected from certain or all other users.
The mvBase Server system(s) must be accessible to remote mvBase client systems (clients connecting to the Server via remote Workstation systems).
Remote tape drives mapped for use by mvBase Server(s) and/or client(s) must be shared with all intended mvBase clients. This may entail very specific sharing, or global sharing, depending on the degree of exclusivity you wish to grant to mvBase users.
Windows offers some additional tools, such as password-protected screen savers.

This section discusses security measures on the Windows side of mvBase that are applicable to these facets of mvBase security.

NOTE	This section is not comprehensive of Windows security, even for the topics discussed, and Rocket highly recommends reference to additional Windows documentation for appropriate implementation.