{"canonical_url":"https://engineer.company/security/","content_markdown":"# How we work securely\n\nSecurity is not a service we sell separately. It is how the work is done: the\nthreat model is part of the design, the hardening is part of the build, and the\nproof is part of the handover.\n\n## How we build\n\n- **Least privilege by default.** Services run as their own unprivileged users,\n  with the narrowest access that lets them work. Access boundaries are designed\n  to limit movement between components if one is compromised.\n- **Secrets never reach the repository.** Credentials live in a secret store or\n  in the deployment layer, never in source and never in a build artefact.\n  Automated scanning runs on every commit, and a hit stops the commit.\n- **Infrastructure described as code.** Servers are built from a description\n  that can be read, reviewed and rebuilt — so the configuration of a machine is\n  a document under version control rather than a memory in somebody's head.\n- **Dependencies pinned and audited.** What a system is made of is written down,\n  and the list is checked against published advisories rather than trusted\n  because it worked last month.\n- **Encryption in transit, everywhere.** Certificates are issued and renewed\n  automatically, and the renewal is monitored, because the common way TLS fails\n  is a certificate nobody was watching.\n- **Backup automation with separate restore tests.** A backup is a claim until\n  somebody restores from it. We implement backup and restore-test workflows\n  separately; verification rests on the data actually restored and checked.\n\n## How this site is built\n\nWe hold our own site to the same standard, and you can verify every line of this\nfrom your own browser.\n\n- **No backend, no database, no admin login.** Every page is a static file written\n  before it is requested. This avoids application sessions and database query\n  endpoints, reducing the site's application attack surface.\n- **Zero executable JavaScript.** Pages, menus and links use native HTML and\n  CSS; the structured data is inert JSON-LD. There is no browser script to make\n  a request or store a preference.\n- **A strict [Content Security Policy](/glossary/#csp)**, declared in the page\n  itself, with `form-action 'none'` — the site posts no forms anywhere.\n- **[Subresource Integrity](/glossary/#sri) on the stylesheet.** The bundle is\n  fingerprinted and hashed at build time, so your browser can verify it arrived\n  unmodified.\n- **No third-party requests.** No third-party analytics, font services or map\n  widgets, and no consent banner. Open your browser's network panel and count\n  the hosts: there is one, and it is ours.\n- **No cookies.** The whole of what is and is not stored is on the\n  [cookies](/cookies/) page.\n- **A machine-readable disclosure policy** at\n  [`/.well-known/security.txt`](/.well-known/security.txt), so a researcher who\n  finds something knows where to send it without asking.\n\n## How it is operated\n\nOne small server in Toronto, described in code, with the access log masked as it\nis written and kept about thirty days. The [credits page](/credits/) names every\npiece of software on it; the [privacy page](/privacy/) says exactly what it\nrecords while it answers.\n\n## Reporting a vulnerability\n\nIf you have found a weakness in this site or in anything we operate, write to\n[welcome@engineer.company](mailto:welcome@engineer.company) and say what you found and how to reproduce it. We will confirm\nreceipt, tell you what we are doing about it, and credit you if you would like\nto be credited. There is no bounty programme and no legal threat — just an\naddress that reaches an engineer.\n\nWant the same rigour applied to your own systems?\n[ask us to look](/contact/) *(we will tell you what we actually find)*.\n\n\u003chttps://engineer.company/security/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"How Engineer ApS builds and operates securely: the practices we hold to, how this site is hardened, and where to report a vulnerability.","formats":{"gemtext":"https://advisory.engineer.company/security/index.gmi","gopher":"https://advisory.engineer.company/security/gophermap","html":"https://advisory.engineer.company/security/","json":"https://advisory.engineer.company/security/index.json","markdown":"https://advisory.engineer.company/security/index.md","pdf":"https://advisory.engineer.company/security/index.pdf"},"kind":"page","language":"en","title":"How we work securely","url":"https://advisory.engineer.company/security/","version":1}