Security hardening: key-only access and encrypted conversations
By Weslley Harakawa
Customer conversations are the most sensitive thing ORYKSA keeps. Over the last weeks we did a security pass on the servers and we want to tell you what changed.
Access to the servers
SSH access is now key-only. Password login is switched off, and every key belongs to an identified person or system. Application secrets (service keys, tokens) left the code and live in a separate configuration, outside the repository.
Encrypted conversations
Conversation history is encrypted at rest in the database. Only the application, with the service key, can read the content. Backups inherit the same encryption.
The website chat only answers your website
Every chat installed on a website has its own identifier and only answers requests coming from the domains authorised in the account. The spoken voice has a request limit per visitor and can only say sentences that belong to that conversation, never arbitrary text.
What is not served
The web servers no longer serve backup files, configuration, scripts or hidden files, even when they exist in the public directory. The links between internal services are not exposed to the internet.
What comes next
Security does not end with a list. We keep reviewing permissions, reducing what each service can see and recording what changes. When there is news relevant to customers, we will tell it here.
