Security
Security whitepaper
How we secure our own systems, our development practice and our customers’ deployments.
Approach
RODMENA is a UK software company that builds fault-tolerant systems. Traffic to all our services is encrypted in transit, and people get only the access their work needs. We run and harden our own infrastructure. Our development practice is designed to contain failures and recover from them. Apart from business correspondence we hold little personal data, and this website uses no analytics, trackers or advertising cookies.
We are a small engineering company with a limited attack surface. The people who operate our systems are the people who built them. Where a control below depends on the engagement, its exact form is agreed in the contract documentation.
Identity and access control
- Multi-factor authentication
- Key accounts, including code hosting, infrastructure and email, are protected by MFA and strong, unique credentials in a password manager.
- Least privilege
- Production access, limited to those who need it, is by SSH key and has no password login. Root access is not used day to day.
- Customer systems (RBAC)
- Our software supports role-based access control and multi-tenant isolation, and the products that hold tenant data use PostgreSQL row-level security.
- SSO
- For customer deployments, integration with your identity provider is scoped per engagement.
Encryption
- In transit
- All public services use TLS, and HTTP traffic is redirected to HTTPS.
- At rest
- The managed database fleet runs on encrypted disks, and database backups are encrypted before they leave their host. Some application hosts do not yet encrypt their disks. For customer deployments we recommend and configure encrypted storage and encrypted PostgreSQL backups as standard.
Secure development
- Version control
- All code is held in Git with a reviewable history. Secrets are never committed to repositories.
- Dependencies
- We keep dependencies to a minimum. Highway needs only PostgreSQL and no Kafka, Redis or external queues. When security advisories are published, we update dependencies promptly.
- Testing
- We verify changes before release, and this website is checked by an automated suite whenever it changes.
Logging, backups and resilience
- Logging
- Server access and error logs are kept for security monitoring and rotated routinely. Logs record operational metadata only, without personal-data payloads.
- Backups
- Engagement systems have scheduled, encrypted and tested backups designed to the agreed recovery objectives. Highway is PostgreSQL-native, and standard PostgreSQL backup tooling works with it.
- Resilience
- Highway uses durable execution and commits application data and workflow state in one transaction. A crash therefore cannot leave a step half written.
Vulnerability management
Operating systems and dependencies are patched promptly, in order of severity. We publish a responsible-disclosure policy and a machine-readable security.txt.
Penetration testing: Planned A summary of scope and findings will be published on the Trust Centre after the first penetration test.
Incident response and notification
Suspected incidents are triaged immediately by the engineers who operate the affected system. Where an incident affects a customer, we notify that customer without undue delay, setting out what we know, what we are doing and what we recommend. Personal-data breaches are handled in line with UK GDPR, and where required we notify the ICO within 72 hours. The security contact is security@rodmena.co.uk.
Certifications
RODMENA LIMITED is certified under the UK Government-backed Cyber Essentials scheme for the whole organisation: certificate 00d24b59-7739-4d97-bb66-341ac50ef018, valid until 30 September 2027. The current status of Cyber Essentials Plus, ICO registration and ISO/IEC 27001 is kept up to date on the Trust Centre.