Security & Reliability
This page summarizes how EM-OS protects your data and the security features available to organization admins.
NOTE
If you need information not covered here, such as answers to a security checklist, where data is stored, or contract terms, please contact us through Support.
How EM-OS protects your data
| Area | Measures |
|---|---|
| Authentication | You sign in with a Google or GitHub account. EM-OS does not store passwords. Two-factor authentication can be enabled on those accounts. |
| Communication | All traffic is encrypted with TLS 1.2 or later, and HSTS is enabled. Cloudflare in front of EM-OS provides DDoS protection and a WAF. |
| Isolation between organizations | Data is separated by organization. Besides the application, the database enforces at the row level that no organization can read or write another's data. |
| Stored data | Stored data is encrypted at the disk level. |
| Activity records | Important operations are recorded in audit logs. The audit log screen masks personal information such as email addresses. |
| Vulnerability handling | Users can report bugs and vulnerabilities through Bug Hunter, and reports are accepted at any time. |
Security features for your organization
Access control (roles)
Access is controlled through three roles based on the principle of least privilege.
| Role | Key permissions |
|---|---|
| Org Admin | Organization-wide settings, inviting members, viewing and editing all data |
| Lead | Managing members of their teams, 1on1s, approving ADRs, evaluations, approving skill updates |
| Member | Updating their own profile, joining 1on1s, viewing data (except private items) |
Details: Administration > Permission Management
Audit logs
Records who did what and when, and lets you export filtered results as CSV (Pro plan).
- Authentication: sign-in, sign-out, failed sign-in
- Organization: creating and deleting teams, changing member roles, issuing invitations
- Administration: plan changes and settings changes
- Data: deleting ADRs and handling sensitive outputs
Details: Administration > Audit Logs
Visibility of monetary data
Admins decide which roles can see unit costs and other amounts on the Allocation screen. By default, only admins can see them.
Details: Administration > Financial Visibility Settings
Payment information
Payments are processed by Stripe. Card numbers are handled by Stripe and are not stored in EM-OS.
Details: Administration > Subscription Management
Scope of external integrations
| Service | What it is used for |
|---|---|
| GitHub | Measuring development metrics such as Four Keys. The GitHub App is given read-only permissions only |
| Jira | Importing and syncing projects and tickets |
| Slack | Notifications and analysis of communication between teams |
| Google Calendar | Scheduling 1on1s |
| AWS and GCP | Importing monitoring metrics and checking SLOs |
Details: Connect External Tools
Features for managing reliability
EM-OS includes features for managing the reliability of your own systems.
- SLO management: Define SLIs (what to measure) and SLOs (targets), and use the error budget to decide whether to invest in new features or reliability. → Service Level Objectives
- Post-mortems: Record incidents on a timeline and find root causes with 5 Whys. Prevention actions are registered as tech debt and tracked to completion. → Post-mortems
