Security

Security is a first principle, not an afterthought.

Your emissions data is sensitive, your regulatory filings are consequential, and your auditors demand a full chain of evidence. Here is exactly how IORA protects the information you trust us with.

AES-256 encryption at rest
TLS 1.3 in transit
RBAC & SSO
SOC 2 Type II in progress
GDPR & CCPA certified
Annual pen test

Data Encryption

AES-256 · TLS 1.3

All customer data stored on IORA's infrastructure is encrypted at rest using AES-256. Data in transit between your browser, our APIs, and our data stores is protected by TLS 1.3 — the most current and secure version of the protocol. We enforce HSTS with a multi-year max-age and preload entry, ensuring no unencrypted connections are ever accepted.

  • AES-256-GCM encryption for all data at rest
  • TLS 1.3 enforced for all data in transit
  • HSTS preloaded — no cleartext HTTP ever accepted
  • Encryption keys managed via a hardware security module (HSM)
  • Separate encryption contexts for each customer tenant

Access Control

RBAC · SSO

IORA uses role-based access control (RBAC) to ensure every user sees only the data and actions appropriate for their role. Enterprise customers can enforce single sign-on via SAML 2.0 or OIDC, integrating with identity providers including Okta, Azure AD, and Google Workspace. Multi-factor authentication is available to all plans and required for administrative roles.

  • Granular RBAC with built-in roles: Viewer, Analyst, Editor, Admin
  • SAML 2.0 and OIDC SSO for enterprise plans
  • TOTP and hardware-key MFA enforced for admin roles
  • Session expiry and idle timeout controls
  • Audit log of every login, permission change, and data export

Compliance Certifications

SOC 2 · GDPR · CCPA

We hold ourselves to the same rigorous standards we help our customers meet. IORA's SOC 2 Type II audit is currently underway with an independent Big 4 auditor. Our GDPR and CCPA compliance programmes are certified and actively maintained. We publish a Data Processing Agreement (DPA) for all customers and a current sub-processor list.

  • SOC 2 Type II audit in progress (completion Q1 2027)
  • GDPR Article 28 Data Processing Agreement available
  • CCPA service provider addendum available on request
  • Sub-processor inventory published and updated quarterly
  • Annual third-party privacy audit

Incident Response

24 h SLA

In the event of a security incident, IORA's incident response team operates around the clock. We commit to acknowledging confirmed incidents within 4 hours, notifying affected customers within 24 hours, and providing a full post-incident report within 5 business days. Our incident response playbook is reviewed and rehearsed quarterly.

  • 24 / 7 security operations monitoring
  • 4-hour acknowledgement SLA for confirmed incidents
  • 24-hour customer notification for data-affecting events
  • 5-business-day post-incident report
  • Quarterly tabletop exercises and playbook reviews

Penetration Testing

Annual · Third-party

IORA commissions an independent penetration test from a CREST-certified security firm at least once per year, and additionally after any major infrastructure change. Internal security engineering runs automated vulnerability scans continuously. Findings are triaged, prioritised by CVSS score, and remediated within defined SLAs — critical findings within 24 hours.

  • Annual external penetration test by CREST-certified firm
  • Continuous automated vulnerability scanning
  • CVSS-based triage with defined remediation SLAs
  • Critical vulnerabilities patched within 24 hours
  • Test reports available to enterprise customers under NDA

Data Residency

EU · US

IORA offers customer-configurable data residency in the European Union (AWS eu-west-1, Frankfurt) or the United States (AWS us-east-1, Virginia). Choosing EU residency ensures all primary data storage, processing, and backups remain within the EEA — important for GDPR Article 44 cross-border transfer restrictions. Data residency is set at account creation and is immutable thereafter.

  • EU residency: AWS Frankfurt (eu-west-1) — GDPR Article 44 compliant
  • US residency: AWS N. Virginia (us-east-1)
  • Backups stored in the same jurisdiction as primary data
  • No cross-region replication without explicit customer consent
  • Residency documented in your DPA and architecture report

Have a specific security question?

Our security team is happy to answer detailed questions about our architecture, share penetration test executive summaries under NDA, and complete your vendor security questionnaire.