Protect sensitive data in Primavera Analytics and Primavera Data Warehouse, such as user names, passwords, and email addresses. Use the process below to help during your security planning:
- Determine which products and interacting applications display or transmit data that your organization considers sensitive. For example, costs and secure codes.
- Implement security measures in Primavera Analytics and Primavera Data Warehouse to carefully grant users access to sensitive data. For example, in P6 EPPM, use a combination of Global Profiles, Project Profiles, and OBS access to limit access to data. In Primavera Unifier, use Company level permissions to grant access to companywide data for all projects and Project level permissions to grant access to a project-specific data.
- Implement security measures for applications that interact with Primavera Analytics and Primavera Data Warehouse, as described in the documentation included with those applications.
- Implement consent notices in the source applications configured with Primavera Analytics and Primavera Data Warehouse to gather the consent of users to store, use, process, and transmit personal information (PI) and to alert users when there is a risk of PI being exposed.
- Implement a password policy by default. Password policies must be applied for:
- Application users
For source applications, it is their responsibility.
- Database-level password policy or Weblogic user password policies.
The DBA is responsible for their specific policies
- Oracle recommends users have a secure password policy for Oracle databases and for WebLogic.
- Application users