Current controls
- HTTPS-encrypted access. Browser traffic to DiamondHawk services is served over HTTPS.
- Authenticated accounts. Access to the application requires authenticated user accounts.
- Role-based permissions. User access is governed through role-based permissions.
- Project-scoped access. Users operate within authorized project boundaries.
- Operational audit history. Material operational actions are supported by historical attribution and operational records.
- Managed cloud infrastructure. DiamondHawk is operated as a hosted application on managed cloud infrastructure.
- Human approval before material schedule actions. Material schedule actions require human approval rather than silent automated plan changes.
- No silent P6 write-back. DiamondHawk does not silently mutate Primavera schedules. P6 changes flow through human-reviewed export and apply paths only.
- Data residency follows deployment region. Hosted application data resides in the cloud region selected for deployment. Customer-specific residency requirements are supported by arrangement.