How is administrative access to the infrastructure protected?
Access to the production infrastructure is strictly controlled:
Bastion host: Each environment has its own bastion host in a private subnet. Access is exclusively via AWS Systems Manager (SSM) — no SSH keys, no public IP address.
Role-based profiles: Read-only profiles for planning operations, administrator profiles for changes. Each profile is tied to a specific AWS account.
Database access: Granted through short-lived federated credentials via a documented administrative workflow. Manual production changes require approval from technical management following a four-eyes principle.
IMDSv2: Enforced on all instances — prevents SSRF-based credential theft attacks via instance metadata.
MFA: Enrolment is required for every account holder and verified during quarterly access reviews. Enforcing MFA as a technical condition on privileged role assumption is in progress.
Logging: All access is logged via CloudTrail. Alerts are triggered on root account access and security group changes.
Personnel location and vetting: amaise employees with access to production environments are subject to documented vetting and access controls. Access to the CH environment is restricted to authorized personnel under the same controls, and Swiss customer data is stored and processed exclusively in the Swiss environment. The same strict access controls apply to the EU and US environments — access is limited to authorized personnel and fully logged.