Module database security

Note: The following information only affects legacy RtReports installations that have chosen NOT to migrate their application data from the Module Database to Asset Framework. By default, new installations do not leverage the PI Module Database hosted on the PI Data Archive. For more information, see RtReports application data storage.

RtReports creates a number of modules in the Module Database. PI System administrators are responsible for enforcing security precautions, and assigning appropriate access levels to each module. By default RtReports creates two modules in these locations:   

• [ServerName]\Modules\%OSI\ClientApps\RtBaseline  

• [ServerName]\\Modules\%OSI\RtReports  

Ensure that the proper permissions have been set on the RtBaseline and RtReports root nodes so that all children modules inherit the desired permissions. Specifically, remove all access for the PI World identity from these modules to protect configuration data stored by RtReports and RtBaseline. Restrict access to these modules to only the following groups and accounts:  

• PI Administrators (PIAdmin, PIAdmins)  

• RtReports and RtBaseline Application Pool accounts  

• PI Identities/Groups that include RtReports Editors