This section describes the main security principles applied by the platform.
It focuses on conceptual security mechanisms rather than operational procedures.
All API access requires authentication.
The platform supports:
- Machine to machine authentication using certificates and JWT
- User authentication using OAuth flows
Authentication tokens are required for all protected endpoints.
Authorization is enforced using:
- Organisation boundaries
- Sender identity permissions
- Role based access control
- API specific scopes
Access is evaluated for each request.
All external communication uses encrypted transport.
TLS is enforced for:
- API endpoints
- Authentication services
- File access services
Unencrypted connections are not supported.
The platform applies encryption at multiple levels:
- Transport encryption
- Storage encryption
- Recipient specific content encryption
When sender side encryption is used, files are decrypted for processing and re encrypted for recipients.
Encryption keys are managed within the platform.
Keys are:
- Generated per content item
- Isolated per recipient
- Protected from direct access
Senders do not receive recipient encryption keys.
The platform supports integrity verification through:
- Hash validation
- Authenticated encryption modes
- Schema validation
When hashes are provided, content integrity is verified before processing.
Security relevant events are logged, including:
- Authentication attempts
- Access operations
- Administrative changes
- Delivery failures
Audit data is available through the Log API.
The platform enforces isolation between:
- Organisation accounts
- Sender identities
- Receivers
Data and access are separated according to organisational boundaries.
Security incidents are handled according to governance procedures.
Operational processes are outside the scope of this documentation. Security incidents are handled according to platform governance procedures.
Details of operational processes are outside the scope of this documentation.