1. Security programme
The production platform should operate a risk-based information-security programme with accountable owners, documented controls, periodic review and vendor management. This document is a proposed policy, not a claim of ISO 27001 or SOC 2 certification.
2. Identity and access
Use unique accounts, role-based permissions, strong session controls, secure password management and multi-factor authentication for sensitive roles. Restrict administrative access by least privilege and remove dormant credentials.
3. Data safeguards
Use encryption in transit, secure secret storage, segregated tenant data and protected backups. Data retention and deletion must follow legal and contractual obligations.
4. Secure development
Apply dependency scanning, access-controlled source repositories, peer review for sensitive changes, environment separation, release procedures, vulnerability remediation and change logging.
5. Monitoring and recovery
Record security-relevant events, monitor misuse and maintain incident response, disaster recovery and restoration procedures with periodically tested plans. Customer website automations should have graceful failure and retry handling.
6. Vulnerability reporting
Provide a published security contact and responsible-disclosure process. Do not conduct intrusive testing of live systems without authorisation. Response and remediation service levels should be defined before production.
Questions about this policy?
Use the Ravensford contact page to submit an enquiry. Production legal, privacy and security contact addresses must be confirmed before launch.
