Elaine integrations use layered security: a dedicated machine identity, secure authentication, encrypted transport, least-privilege access, network restrictions where appropriate, and monitored credential use.
Security controls by interface
| Interface type | Typical controls |
|---|---|
| RESTful and HTTP APIs | Dedicated API identity, supported token or credential method, TLS, permissions, optional IP restrictions, and credential rotation. |
| Form API | TLS, approved source domains where supported, input validation, abuse protection, and privacy-aware form design. |
| SIEIS | SFTP, tenant-specific access, SSH public-key authentication, controlled directories, and operational file handling. |
| Webhooks and events | Authenticated endpoints, TLS, request validation, replay protection where supported, and restricted event data. |
Credential design
- Create a separate machine identity for each integration or clearly separated trust boundary.
- Grant only the permissions required by the workflow.
- Store secrets and tokens in an approved secret-management system.
- Rotate credentials and revoke them immediately when ownership or trust changes.
- Never place production credentials in source code, browser-delivered code, documentation, or logs.
Optional site-to-site VPN
Selected Elaine services can optionally be connected to customer networks through a persistent site-to-site VPN. This is useful when a backend must not be reachable over the public internet, a private route is required by policy, or Elaine must call a private customer service.
A VPN is an additional network control; it does not replace interface authentication, authorization, transport encryption, input validation, or monitoring. Availability depends on the selected Elaine service and operating model. Public-facing services such as forms, tracking, or content delivery may require internet connectivity and are not necessarily available through the VPN.
Security review checklist
- Identify the systems, data categories, directions, and environments involved.
- Select authentication, permissions, key or token lifetime, and rotation ownership.
- Decide whether IP restrictions or site-to-site VPN are required.
- Define logging that supports investigation without exposing personal data or secrets.
- Test unauthorized access, expired credentials, replay, malformed input, and dependency failure.