Security

Security is an operating habit.

We run infrastructure for other people, so we treat security as a daily process rather than an annual PDF. This page explains how to report a problem and what to expect.

Responsible disclosure

Report a vulnerability.

Email security@atlantika-company.uk. If you prefer encrypted email, ask for our PGP key in the first message and we will reply with it.

Include enough to reproduce the issue: the affected URL or IP, what you expected, what happened, and any logs or screenshots. Please do not test against another customer's account or data.

Safe harbour. We will not pursue legal action for good-faith research that respects privacy, avoids disruption and does not access customer data. If you are unsure whether something is in scope, ask first.

A machine-readable copy of this policy is available at /.well-known/security.txt.

Practices

The basics, done on a schedule.

None of this is exotic. The difference is that it is written down, reviewed and checked by someone who is not the person who implemented it.

Patch discipline

Weekly operating system patching. Critical CVEs triaged within 24 hours and patched within 72, including firmware.

Least privilege

Hardware keys for administrative access, short-lived tokens and no shared root accounts. Access is reviewed quarterly.

Segmentation

The management plane lives on a separate network. Customer workloads are isolated from each other and from our tooling.

Encryption

TLS 1.3 preferred, 1.2 minimum. Disks are encrypted, backups are encrypted, and customer-held keys are available for backups.

Backups

Immutable, geographically separate and restored in a quarterly drill. A backup that has never been restored is a rumour.

Visibility

Centralised logs, security alerts to the on-call engineer, and twelve-month retention for authentication events.

Scope

What is in scope.

We welcome reports affecting the following, provided you use your own account and do not access anyone else's data:

  • atlantika-company.uk and its subdomains
  • The customer portal and authentication flows
  • The public API and provisioning endpoints
  • Network services operated by Atlantika

Out of scope

What we will not chase.

  • Social engineering of staff or customers
  • Physical attacks on data centres or offices
  • Denial-of-service or volumetric testing
  • Automated scanner output without a credible finding
  • Third-party services we do not operate

No bug bounty, for now. We do not pay for reports, and we will not pretend a report is not valuable. With your permission, we credit researchers in release notes after the fix is live.

Found something odd?

Tell us before you tell the internet. We will confirm what we can, fix what needs fixing and keep you updated.