Security at Quayline
Your artifacts are the last stop before production. This page describes how we protect them and how to report a problem.
Data protection
- All blobs, manifests and cache chunks are encrypted at rest with AES-256-GCM. Each organisation has its own data key, wrapped by a regional master key that is rotated every 90 days.
- All connections use TLS 1.3. TLS 1.2 is accepted only from clients that cannot negotiate 1.3, and will be switched off on June 30, 2027.
- Enterprise organisations can bring their own keys through an external KMS and can revoke access to all data with one key action.
- Storage nodes are in the European Union, the United States and Asia-Pacific. Data stays in the regions you choose.
Access control
Staff access to production is by short-lived certificates issued after hardware-key authentication and a recorded justification. Nobody at Quayline can read the content of your artifacts without a customer-approved support grant, which expires after 24 hours and appears in your audit log.
Software supply chain
The registry and the qln client are built from a reproducible pipeline, signed with cosign and published with an SBOM. You can verify a release before installing it:
$ cosign verify --certificate-identity-regexp "release@quayline" fi4.enotcloud.com/quayline/qln:2.14.3
Verification for fi4.enotcloud.com/quayline/qln:2.14.3 --
The cosign claims were validated
The code-signing certificate was verified using trusted certificate authority certificatesAssurance
| Programme | Status |
|---|---|
| SOC 2 Type II | Report covering January 1 to June 30, 2026, available under NDA |
| ISO/IEC 27001 | Certified, certificate issued March 2026, valid to March 2029 |
| Penetration testing | Independent external test every year; last completed September 2026, no critical findings |
| GDPR | Data processing agreement and EU standard contractual clauses available to every customer |
Responsible disclosure
If you believe you have found a vulnerability in Quayline, write to security@fi4.enotcloud.com. Our contact details, expiry and policy are also published in security.txt.
- We acknowledge reports within one business day and give a first assessment within five.
- Please give us a reasonable period, normally 90 days, to fix an issue before disclosing it.
- Do not access data that is not yours, degrade the service for others or run denial of service tests.
- Testing within these limits is authorised and we will not pursue legal action for it.
We do not run a paid bounty, but we credit reporters on request in the changelog and send a Quayline hardware keychain and a year of Team plan seats to people who report valid issues.