Transport and headers
The Content-Security-Policy, security headers and cookie settings of the Baseera platform.
This page covers the platform web app (the console). The runtime API is called with headers and tokens, not cookies. See Authentication.
Content-Security-Policy
The policy is built for each request in the platform's middleware. Scripts need that request's nonce, plus strict-dynamic, so injected markup cannot run script.
| Directive | Value |
|---|---|
default-src | 'self' |
script-src | 'self', the request's nonce and 'strict-dynamic' |
style-src | 'self' and 'unsafe-inline' |
img-src | 'self', data:, blob: and the Supabase project |
connect-src | 'self', the Supabase project (and websocket), and the runtime for the in-product guide when it is on |
font-src | 'self' |
object-src | 'none' |
frame-ancestors | 'none' |
base-uri, form-action | 'self' |
upgrade-insecure-requests | Only on requests that arrived over HTTPS |
style-src keeps 'unsafe-inline' because React and the motion library set style attributes, which cannot carry a nonce. Scripts never get 'unsafe-inline'. A library that injects an inline script has to take the nonce, which a server component reads from the x-nonce header.
Fonts are self-hosted, so no third-party origin is in the policy.
Security headers
Sent on every response:
| Header | Value |
|---|---|
Strict-Transport-Security | max-age=63072000; includeSubDomains; preload |
X-Content-Type-Options | nosniff |
X-Frame-Options | DENY |
Referrer-Policy | strict-origin-when-cross-origin |
Permissions-Policy | camera, microphone, geolocation, payment, usb and interest-cohort all denied |
Cross-Origin-Opener-Policy | same-origin |
Cross-Origin-Resource-Policy | same-origin |
X-Permitted-Cross-Domain-Policies | none |
Cookies
Session cookies are SameSite and Secure in production.
If you embed the SDK
Your own site sets its own CSP. If you use an agent logo, your policy needs img-src blob:, because the SDK shows the logo from a blob: URL. Allow connect-src to your runtime URL. The SDK sends the publishable key and user token as headers, never as cookies.
Sign-in settings
Passwords need 12 or more characters with lower and upper case letters and a digit. Email confirmation is on. Access tokens and email links last 15 minutes, secure password change is on, and TOTP is available. See Two-factor and sessions.