Secure defaults and clear boundaries.

Start with less exposure

The public website has no database, advertising trackers or infrastructure credentials. Its contact workflow validates input and sends through a separate mail boundary without exposing the private recipient.

Controls that follow the risk

Commercial and customer systems will require server-side authorisation, administrative MFA, secure sessions, least privilege and useful audit records before they are trusted with accounts or service changes.

• Input validation and contextual output escaping
• CSRF protection for state changes
• Credential isolation
• Dependency maintenance
• Production-safe error handling

Customer identity

A customer login cannot be treated as a visual form alone. Identity verification, password handling, recovery, session security, rate limiting and account migration must be designed as one controlled capability.

Responsible reporting

Potential vulnerabilities should be reported privately through a confirmed and monitored route. Reports must not be placed in public issues or ordinary forms when they contain exploit detail or sensitive data.