Security

How EternalEngine is secured

How data is separated, how access is controlled, how inputs are validated and how the code is checked, and what we do not claim.

Security areas

Encryption in transit and for stored secrets

Connections are encrypted in transit with TLS; TLS 1.3 is supported. Secrets are kept in an encrypted vault.

  • Secrets are kept in an encrypted vault.
  • Encrypted in transit with TLS; TLS 1.3 is supported.

Tenant separation details

Tenant tables are separated in the database using PostgreSQL row-level security.

  • Row-level security (RLS) in the database

Access controls

Role-based permissions control what each user can see and do. Authentication events are recorded in an audit log.

  • Role-based access control (RBAC)
  • JWT authentication tokens
  • Audit log of sign-in and account events

Infrastructure

Services run in containers. Backups are taken on request, not on an automated schedule.

  • Docker containerization
  • Backups taken on request (no automated schedule)

Checked code

Changes land through a merge queue that runs the full CI matrix before they reach the main branch, and CodeQL static analysis is configured in the repository.

  • Merge queue with the full CI matrix
  • CodeQL static analysis configured

Validated inputs

External inputs are schema-validated and database queries are parameterized.

  • Schema validation (Zod) on external inputs
  • Parameterized SQL only, no string interpolation
Response

Vulnerability response targets.

When a vulnerability is confirmed, these are the internal remediation targets from our findings process. They are targets, not a guarantee to any customer.

Internal remediation targets by severity
SeverityRemediation target
Critical24 hours
High72 hours
Medium7 days
Low30 days

Vulnerability response

What we do not claim

Honesty over badges. Nothing here is a certification.

  • EternalEngine holds no security certification. It does not hold SOC 2 Type II or ISO 27001.
  • We use OWASP ASVS and NIST SP 800-218 as reference frameworks. That is a way of working, not a certification or an outside attestation.
  • We do not claim GDPR compliance. What we commit to in writing is in the Data Processing Agreement and the Privacy Policy.
  • No uptime figure is promised. System status says what is monitored publicly.
  • Backups are taken on request. There is no automated backup schedule and no recovery-time or recovery-point target.
Do you hold SOC 2 or ISO 27001?

No. EternalEngine holds neither certification and does not claim one. The security page says what we do and what we do not claim.

What is your GDPR status?

We do not claim GDPR compliance. The Data Processing Agreement and the Privacy Policy say what is in writing today.

How is my data separated from other customers?

Tenant tables are separated in the database using PostgreSQL row-level security.

How do I report a vulnerability?

Email info@eternalengineos.io with reproduction steps. We welcome coordinated disclosure, and good-faith reports made through that channel are not a violation of the acceptable-use section of the Terms.

Questions about security?

Ask about how data is separated, how access works, or what is in writing. The commitments in writing: the Data Processing Agreement, the Privacy Policy, and every request you can make on Your Data & Requests.