Skip to content

fix(security): add response headers and opt-in HSTS #320

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jdotc1 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(security): add response headers and opt-in HSTS #320

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2e52bff
fix(security): add configurable response hardening headers
jdotc1 Nov 9, 2026
753e032
docs: explain frontend security headers and HSTS opt-in
jdotc1 Nov 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,22 @@ This runs Postgres, the indexer (`indexer/`), and the frontend together — see

The Postgres port is published only on `127.0.0.1`. Compose uses `prism` as a local-development-only default for `POSTGRES_PASSWORD`; set a strong value in your environment before starting the stack if you need a different password. Do not use the default for a production deployment.

### Security headers

The frontend sends a Content Security Policy, `X-Frame-Options: DENY`,
`Referrer-Policy: strict-origin-when-cross-origin`,
`X-Content-Type-Options: nosniff`, and a restrictive `Permissions-Policy` on
all paths. The permissions policy disables camera, microphone, geolocation,
payment, and USB browser features, which Prism does not use.

For an HTTPS-only production deployment, opt in to HTTP Strict Transport
Security by setting `PRISM_ENABLE_HSTS=true` **when building the frontend**
(for example, `PRISM_ENABLE_HSTS=true npm run build`). The production response
then includes `Strict-Transport-Security: max-age=31536000`. HSTS is absent in
development and when the variable is unset, so local HTTP remains usable.
Only enable HSTS after confirming that the public hostname is served over
HTTPS; browsers can remember the policy for up to a year.

### Rate limits and reverse proxies

Every `/api/*` route is rate-limited per client: 30 requests per minute, except `/api/contract/[id]/simulate` at 10 per minute. Each route keeps its own counter, so hitting the limit on one route doesn't block the others. Over the limit, the API returns `429` with a `Retry-After` header (in seconds).
Expand Down
6 changes: 6 additions & 0 deletions frontend/next.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
const isDev = process.env.NODE_ENV !== "production";
const hstsEnabled = !isDev && process.env.PRISM_ENABLE_HSTS === "true";

/** Origins of the configured Horizon and RPC endpoints, skipping any value that isn't a URL. */
function endpointOrigins() {
Expand Down Expand Up @@ -40,6 +41,11 @@ const nextConfig = {
{ key: "Content-Security-Policy", value: contentSecurityPolicy },
{ key: "X-Frame-Options", value: "DENY" },
{ key: "Referrer-Policy", value: "strict-origin-when-cross-origin" },
{ key: "X-Content-Type-Options", value: "nosniff" },
{ key: "Permissions-Policy", value: "camera=(), microphone=(), geolocation=(), payment=(), usb=()" },
...(hstsEnabled
? [{ key: "Strict-Transport-Security", value: "max-age=31536000" }]
: []),
],
},
];
Expand Down