EterShieldDocs
etershield.com
PTLog in
Trust and security/Security

Security & Trust

Version 2.5 · 2026-11-15
Classification: Public

EterShield preserves the security knowledge of organisations, so the security of the platform itself is non-negotiable. This page summarises how we protect our customers' data and knowledge.

Data in Europe

Primary locationDedicated infrastructure managed by Eter Growth, in the European Union
CDN / DNSBunny.net (CDN and DNS of the domain)
BackupsEncrypted, with copies off the production server
Transfers outside the EEAPersonal data does not leave the European Economic Area under normal operation. The exception is AI requests (see below)

For transfers to sub-processors in the USA (for example the AI API), we apply Standard Contractual Clauses (SCCs) and select only providers with zero retention for API data.

International transfers: posture and documentation

Eter Growth bases every transfer of personal data to countries outside the EEA on Standard Contractual Clauses (SCCs), under Implementing Decision (EU) 2021/914. For each transfer we document a Transfer Impact Assessment (TIA), required by Schrems II case law and EDPB guidance, which analyses the legal framework of the destination country, surveillance risks and the supplementary measures applied.

We also continuously monitor exposure to the EU-US Data Privacy Framework (DPF): any transfer that depends on it is flagged for reassessment, so that no transfer is left without documented legal cover.

Data isolation

  • Isolation per organisation: each organisation has a unique identifier and each request is validated against the active organisation of the session.
  • Layered protection: additional controls reinforce the isolation of each organisation's data.
  • Least privilege: the application accesses data only with the permissions it needs.
  • Soft delete: in several modules deleted records are marked as deleted rather than destroyed at once, for traceability and recovery in case of error.

Access control

  • Granular role permissions (Admin, Manager, Viewer, Auditor) and custom roles; each module has independent permissions.
  • Multi-organisation membership: a consultant or partner can belong to several organisations by invitation; disabling access in one does not affect the others. The customer can refuse external members.
  • Multi-factor authentication: authenticator app (TOTP). MFA policy per organisation (off, administrators or everyone). MFA is mandatory for external members.
  • Sessions with server-side expiry and inactivity and maximum-duration limits configurable per organisation.
  • SAML 2.0 SSO per organisation, with mandatory domain validation; integration with Azure AD, Okta and other enterprise IdPs.
  • SCIM 2.0 provisioning: users and groups synchronised from the customer's IdP.
  • Sign-in with Google and GitHub, with email verification.
  • Email confirmation: email and password sign-in only works with a confirmed email; the confirmation link is single-use, expires after 24 hours and confirms with one click.
  • Layered sign-in limits: per address, per email and address, and a ceiling per email, to stop password guessing.
  • SSO domain proof: a domain only enables SSO, automatic account creation and SCIM after it is proved by a DNS record, revalidated every day.
  • Proven identity-provider MFA: people signing in through SSO skip the EterShield second factor only if the provider proves MFA was done in that session.
  • MFA recovery codes: 12 single-use codes, which can be regenerated.
  • Segregation of duties in approvals: whoever submits, creates or owns a record cannot approve it. Configurable per organisation: it can only record the situation or block the approval.
  • Session log: all sessions (start and end, authentication failures, expiry) are recorded, with automatic highlighting of new devices and addresses for Admin and Auditor.

Application protection

  • Dynamic Content Security Policy (CSP) that mitigates script injection attacks (XSS).
  • No third-party resources: fonts are served by EterShield itself, so users' IP addresses are not sent to third parties for that reason.
  • Public data subject request form (GDPR): off by default in each organisation, with email confirmation and abuse protection.
  • Request rate limiting on all sensitive points (authentication, SSO, API), with a 429 response and the waiting time.
  • HTTPS/TLS 1.3 across all communication.
  • Application firewall (WAF) in front of the application, which detects exploitation attempts.
  • Signed inbound webhooks, rejected when the signature is missing or invalid.
  • Protected automatic tasks with rotating credentials.

API keys

  • Named keys per organisation, one per integration or server, with mandatory expiry date, revocation and last-use log.
  • Stored only as a hash: the full value is shown only at creation.
  • Scopes per route: each key is accepted only on the routes it was issued for. A key without scopes has full access to the organisation's API, so good practice is to always define scopes.

Continuous monitoring

SystemWhat it monitors
SIEMInfrastructure security events and EterShield audit events
Network intrusion detection (NIDS)Network traffic on production servers, with real-time alerts
AntivirusFull daily scan and real-time protection
CDN / WAFTraffic, denial-of-service attacks and exploitation attempts
Audit logAll changes (create, update, delete, approve, reject, export), with user and date. Hash chain with a timestamp from an external authority; administrators and auditors can export an integrity proof verifiable offline. The log is immutable: changes and deletions are refused
Session logAll user sessions, with address, device and authentication failures
Health checksDaily, with email alerts on failure

Backups and availability

Backup frequencyDaily, encrypted with AES-256
StorageTwo encrypted external copies, off the production server
Retention7 days on the server and 60 days in an external copy
Estimated RTOUnder 4 hours for full recovery
RPOUnder 24 hours

Secure development

  • Mandatory code review before any change reaches production.
  • Static security analysis of the code and dependency checks on every change.
  • Automated tests, including end-to-end tests, on every change.
  • Operating system security updates applied automatically and daily.
  • Remote access to production servers is restricted.

Vulnerability management and coordinated disclosure

  • Vulnerability feed: automatic ingestion from public sources (EUVD/ENISA, NVD/NIST), enriched with exploitation probability (EPSS) and the catalogue of exploited vulnerabilities (CISA KEV), to prioritise risk.
  • Software bill of materials (SBOM): reading of SBOMs in CycloneDX and SPDX formats to relate components to assets and known vulnerabilities.
  • Coordinated disclosure: public /security page with scope, deadlines and legal protection for good-faith reporters, and a /.well-known/security.txt file (RFC 9116).

AI: transparency and control

The full detail is in Artificial intelligence in EterShield. In short:

Model providerClaude (Anthropic), listed as a sub-processor in the DPA
Data retention by the providerZero, under the contract
Training on customer dataNo
Transparency of each answerEach result shows confidence, sources and limits
Customer controlAI is optional: an administrator can switch it off for the organization and defines by role who can use it; quota and usage are visible
Form suggestions: the person decidesOn forms, a suggestion is saved only when the person accepts and submits it; every decision is logged
Data sent to the modelOnly what is needed and within what the person can already see, with a size limit; personal fields on forms are not sent
RetentionThe content of suggestions is deleted after 12 months; metadata and the decision remain

Compliance of the platform itself

EterShield is developed and operated following the practices it recommends to its customers:

PracticeStatus
GDPR, documented processingDPA available
International transfersSCCs in force, TIA documented per transfer and DPF monitoring
Data hosted in the EUYes
Immutable audit log with independent timestampYes, with an integrity proof verifiable offline
Encryption of sensitive personal dataAES-256-GCM
Public privacy policy and terms of serviceYes
Network intrusion detection and antivirusActive on production servers
Backups with an encrypted external copyYes
Request rate limiting on public pointsYes
Signed inbound webhooksYes
Multi-factor authentication, SSO and SCIMAvailable, with policy per organisation
Segregation of duties in approvalsAvailable, configurable per organisation
AI assistance with human review and defined retentionYes
AI agent governanceRegister, card and periodic review, with human confirmation
GDPR modules (RoPA, LIA, retention periods, consents, data subject requests)In production; LIA approval is always human
Technical vulnerability managementCode and dependency analysis on every change
Coordinated vulnerability disclosurePublic page and security.txt (RFC 9116)
Public institutional Trust CenterYes
Data Act compliance (Reg. (EU) 2023/2854)Declaration published in the Trust Center

Reporting vulnerabilities

Found a security vulnerability? We appreciate responsible reporting:

  • Email: security@etershield.com (subject: [SECURITY])
  • Response: acknowledgement within 2 working days (24 hours for critical vulnerabilities)
  • Commitment: we will not take legal action against good-faith researchers

Public Trust Center

The EterShield website gathers, at www.etershield.com/en/trust-center, what you can read without asking the team: service status, the sub-processor list, AI transparency, security, responsible disclosure and news.

  • Sub-processors: the public list is the same as clause 6 of the DPA. On the page you can subscribe to notice of changes by email: you receive an email with a link to confirm and you are only subscribed after clicking it; every notice includes a link to cancel. Changes to the list are notified 30 days in advance.
  • AI transparency: a short page with the model provider, where data stays, what people review and the commitment not to train on customer data. The detail is in the AI guide.
  • Responsible disclosure: the acknowledgements page gathers the rules for reporting a vulnerability, the deadlines by severity and the names of those who have helped (with their permission). The site's security.txt file points to it.
  • News: what changed in EterShield, explained by the benefit, with an RSS feed for your reader.
  • Documents on request: the DPA for signing and the security summary are requested through a form. The request reaches the team, which reviews it and replies by email; nothing is downloaded automatically.

Contact

Security Officer (CTO), Eter Growth
geral@etergrowth.com · https://etershield.etergrowth.com

EterShield, an Eter Growth platform