bakehousebristol.com

# Passive security review — Bakehouse Bristol | Baking and beyond

Run: c7ad31fa-aacf-4c52-8b1d-24f397908ab3  
Status: **completed**  
Reviewed: `bakehousebristol.com`, `www.bakehousebristol.com`  
Started: 2026-10-26T00:45:12.101Z  
Requests: 17 of 40 budgeted, at most 1/s  
Discovered pages: 3
Tier: 1 — +1 no WAF observed

## Summary

**5** configuration issues: 0 high, 3 medium, 2 low.

### Pages fetched

- https://www.bakehousebristol.com/ → HTTP 200
- https://www.bakehousebristol.com/contact → HTTP 404
- https://www.bakehousebristol.com/contact-us → HTTP 404

## Checks

| Check | Host | Severity | Result |
| --- | --- | --- | --- |
| The site serves HTTPS | bakehousebristol.com, www.bakehousebristol.com | Info | pass |
| HTTP Strict Transport Security | bakehousebristol.com, www.bakehousebristol.com | Medium | fail |
| Content Security Policy | bakehousebristol.com, www.bakehousebristol.com | Medium | fail |
| MIME type sniffing is disabled | bakehousebristol.com, www.bakehousebristol.com | Low | fail |
| Framing is restricted | bakehousebristol.com, www.bakehousebristol.com | Medium | fail |
| Referrer policy | bakehousebristol.com, www.bakehousebristol.com | Low | fail |
| Cookie attributes | bakehousebristol.com, www.bakehousebristol.com | Info | info |
| Server version disclosure | bakehousebristol.com, www.bakehousebristol.com | Info | pass |
| Cross-origin resource sharing | bakehousebristol.com, www.bakehousebristol.com | Info | pass |
| HTTP redirects to HTTPS | bakehousebristol.com, www.bakehousebristol.com | Info | pass |
| Exposure check: /.git/HEAD | bakehousebristol.com, www.bakehousebristol.com | Info | info |
| Exposure check: /.env | bakehousebristol.com, www.bakehousebristol.com | Info | info |
| Exposure check: /server-status | bakehousebristol.com, www.bakehousebristol.com | Info | info |
| security.txt | bakehousebristol.com, www.bakehousebristol.com | Low | info |
| TLS certificate | bakehousebristol.com, www.bakehousebristol.com | Info | pass |

## Findings

### 1. HTTP Strict Transport Security (Medium)

No Strict-Transport-Security header was returned.

**Suggested fix.** Add Strict-Transport-Security: max-age=31536000; includeSubDomains. Start with a short max-age while testing.

### 2. Content Security Policy (Medium)

No Content-Security-Policy header was returned.

**Suggested fix.** Start with Content-Security-Policy-Report-Only. Inventory external scripts and inline code, then test a site-specific policy before enforcing it.

### 3. Framing is restricted (Medium)

Neither X-Frame-Options nor a CSP frame-ancestors directive restricts framing.

**Suggested fix.** Send X-Frame-Options: SAMEORIGIN or a CSP frame-ancestors directive.

### 4. MIME type sniffing is disabled (Low)

No X-Content-Type-Options header was returned.

**Suggested fix.** Add X-Content-Type-Options: nosniff.

### 5. Referrer policy (Low)

No Referrer-Policy header was returned.

**Suggested fix.** Add Referrer-Policy: strict-origin-when-cross-origin.

## Patch

Configuration suggestions for staging review; see `patch/README.md` for placement and verification.

### _headers

```
# Review in staging. CSP is report-only and does not remediate the CSP finding.
/*
  Strict-Transport-Security: max-age=31536000; includeSubDomains
  Content-Security-Policy-Report-Only: default-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; script-src 'self'
  X-Content-Type-Options: nosniff
  X-Frame-Options: SAMEORIGIN
  Referrer-Policy: strict-origin-when-cross-origin
```

### nginx.conf

```
# Review in staging. CSP is report-only; tailor it before enforcement.
# Add inside the server { } block, then reload nginx.
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
add_header Content-Security-Policy-Report-Only "default-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; script-src 'self'" always;
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
```

### apache.conf

```
# Review in staging. CSP is report-only; tailor it before enforcement.
# Add inside the <VirtualHost> block or .htaccess, then reload Apache.
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
Header always set Content-Security-Policy-Report-Only "default-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; script-src 'self'"
Header always set X-Content-Type-Options "nosniff"
Header always set X-Frame-Options "SAMEORIGIN"
Header always set Referrer-Policy "strict-origin-when-cross-origin"
```

## Requires site-specific review

- csp

## Application findings (deep pass)

The deep pass completed with no confirmed application findings. This does not establish complete coverage or prove the site is secure.
## Basis and limits

The baseline is passive: GET and HEAD against public addresses only. DNS is resolved once and connections are pinned; the site stays inside its own registrable domain; redirects are reported, never followed; the rate and request budget are enforced.

Checks cover transport, response headers, cookie flags, version banners, CORS, the certificate, and a few well-known exposure paths.

## What this review did not do

No exploitation, login, form submission, credential use, file upload, or application-logic testing in the passive baseline. No finding is confirmed exploitable; exposures are recorded as directly observed. Nothing was changed on the server.

## Delivery

`owner-email.md` and `github-issue.md` are generated from these findings. Nothing is sent unless the `send` command runs.