Microsoft Windows security issues

File level security issues

Helix ALM can only restrict security access through the application. This does not replace the need for file and directory security at the operating system level.

Use Windows NT/2000 with NTFS to provide increased security. You can restrict access to the Helix ALM directory through NTFS security settings. You can also restrict access for most users to read-only permission. Users do not need write access because the server application does the actual writing to the project files.

The following example illustrates what could happen if users have full access:

A drive is accessible through the network and there is no file-level security on the drive. Any user can open and look at data/files using a program such as Notepad. Data is stored in both binary format and plain text. Usernames and passwords are encrypted so the user cannot access that information. In addition to viewing the data/files, it is possible for a user to vandalize your system by deleting files or even deleting an entire project.

Windows 2000 with FAT provides some security restrictions. However, Windows NT/2000 with NTFS is recommended if security is a concern.

Directory sharing issues

  • The Helix ALM ODBC driver requires projects to be accessible via a shared network drive. You only need to share the Helix ALM directory if you are planning to use the ODBC driver.
  • If you grant ODBC access to a project, users can view all Helix ALM data with the exception of encrypted usernames and passwords.
  • The need for file-level security is increased if you place the Helix ALM project on a shared network drive.
Windows XP does not provide file-level security because it uses the FAT file system. Windows NT security is only available if you are using the NTFS file system; it is not available with the FAT file system. You can convert to NTFS. Refer to the Microsoft Windows documentation for additional information.