Access Control
Infrastructure access
Credential management
All sensitive keys and credentials are stored in AWS Secrets Manager and accessed at runtime by authorized service instances only. No credentials exist in source code, configuration files, or environment files committed to version control.
IAM role separation
Access to AWS infrastructure is governed by IAM roles with strict separation of duties:
Production data and services
Company CTO only, plus service-to-service IAM roles
Staging and development
Development team (for testing and debugging)
Production monitoring and logs
Development team (read-only — no access to production data stores)
Application-level access control
Authentication
All users authenticate via Microsoft Entra ID (Azure AD) or Google Identity using industry-standard OAuth 2.0. Rockhopper does not maintain its own authentication system — credentials are never stored or managed by the platform.
Authorization
Every API request is authorized against the user's team membership and role before any data is returned or modified:
Team-scoped — Users can only access files and data belonging to teams they are members of. There is no cross-team data visibility.
Role-based — Admin, Manager, and Contributor roles determine what actions a user can perform (e.g., inviting members, dismissing reviews).
File-scoped — Individual file access is verified on every request through dedicated access guards.
No API endpoint is accessible without authentication and authorization checks.
Audit logging
All data mutations — creating, updating, and deleting records — are logged with:
The acting user's identity
The resource type and ID affected
A timestamp
This audit trail is maintained for SOC 2 compliance and is available for forensic review.
Last updated