Altitude operates the application, authentication systems and provider integrations, prepares payments, and maintains the account programs. Its operational controls govern employee and contractor access, production changes, monitoring and incident response. These controls complement the account's onchain rules.
Control | How it works |
Identity and access management | Employee and contractor access uses single sign-on and hardware security keys, with service-specific coverage. Identity workflows automate setting up access, role changes and deactivation for connected services. |
Device security | Policy requires device management and endpoint detection and response tools for employee and contractor devices with production access. These tools detect and respond to threats on devices. Managed devices receive centralized updates, vulnerability checks and targeted remediation. |
Production changes | Change policy requires human code review. Production deployments pass an approval gate in GitHub Actions. |
Monitoring | External 24/7 monitoring covers connected cloud, endpoint and identity systems. Cloud audit logs feed the workflow, which supports blocking confirmed threats, recording investigations and escalating incidents. |
Email protection | Filtering, link and attachment checks, and employee reporting address phishing and malicious email. Protected sensitive email content requires additional authentication. |
Web request filtering | Web application firewall rules block known probing patterns. |
Training and onboarding | Onboarding includes security policies, phishing guidance and device enrollment before access to work tools. |
Incident response | Documented procedures have 24/7 on-call ownership and after-hours escalation to external response specialists. |
These controls do not prevent every application flaw, compromised session or authorized malicious payment. Monitoring and on-call coverage do not guarantee detection before loss or a fixed response or recovery time.