MIRA
Official Terms & PoliciesEffective date:

Security Policy & Vulnerability Disclosure

In short

At Motorsync Ltd, we prioritise system security, data privacy, and continuous threat monitoring across all MIRA products.

  • Strong Encryption: All data in transit is encrypted using TLS 1.2 or higher; sensitive data at rest is protected via AES-256 encryption.
  • Multi-Tenant Isolation: Strict tenant boundary enforcement prevents cross-dealership data leakage under company-scoped access tokens.
  • Responsible Disclosure: We welcome security reports from ethical researchers under our Safe Harbour guidelines.

This policy details technical security measures enforced by Motorsync Ltd ("we", "us", or "MIRA") and sets out guidelines for reporting vulnerability findings responsibly.

1. Technical Security Architecture

MIRA software systems are engineered following industry security frameworks (ISO 27001 / OWASP Top 10) and checked with regular code and dependency vulnerability scans:

  • Cloud Infrastructure: Hosted on Amazon Web Services in London, with hourly database backups stored separately from the servers.
  • Network Defence: Filtering of malicious traffic at the edge, rate limiting, bot protection, and our cloud provider's network-level protection against Distributed Denial-of-Service (DDoS) attacks.
  • Tenant Boundary Controls: Cryptographic token validation and company-level data isolation for dealership databases.

2. Data Encryption & Protection

Data protection is enforced at every layer of system architecture:

  • Encryption in Transit: Mandatory TLS 1.2 or higher transport encryption with HTTP Strict Transport Security (HSTS).
  • Encryption at Rest: AES-256 database field encryption for PII, document scans, and customer records.
  • Sanitised Logging: Automatic masking of sensitive authentication credentials, passwords, and PII from system audit logs.

3. Access Control & Authentication

Account security is protected via risk-based authentication, FIDO2/WebAuthn passkey support, mandatory password complexity rules, and multi-factor authentication options for dealership staff accounts.

4. Vulnerability Disclosure & Safe Harbour

Safe Harbour Commitment: Motorsync Ltd will not initiate legal action against security researchers who discover and report system vulnerabilities in good faith following these guidelines.

Researchers testing MIRA security must abide by the following rules:

  • Do not access, modify, or delete customer or dealership data belonging to real accounts.
  • Do not execute Denial-of-Service (DoS) attacks, automated spamming, or social engineering.
  • Report findings confidentially to admin@motorsync.co.uk and allow reasonable time for remediation before public disclosure.

5. Incident Response & SLAs

We acknowledge every security report within 2 business days, fix the most severe issues first, and keep the reporter updated until the issue is resolved. If an incident affects personal data, we follow the notification steps in our Data Processing Addendum and the law.

6. Reporting Security Enquiries

Motorsync Ltd Security Desk

Email: admin@motorsync.co.uk

Related Regulatory & Policy Documents