Skip to content

Security: README security model + deployment hardening + epClientSecret audit (#279 LOW-4 + INFO-1) #288

@field123

Description

@field123

Parent PRD

#279

What to build

Closing slice for PRD #279. Three small jobs bundled because none of them merit a standalone issue:

  1. Security model README section — describe the package's security guarantees after Security: verify EP account token in /ep/account/login (#279 HIGH-1) #280Security: apply Origin-allowlist gate to cart routes (#279 MEDIUM-2) #287 land: HttpOnly JWE session, server-side cart routes, opt-in browser token surface, Origin-allowlist gates on proxy + cart, host allowlist on bundle config, account-login token verification.

  2. Deployment hardening section (LOW-4) — recommended edge/WAF rules for /api/ep/ep/anonymous (per-IP rate limit, short-cache anonymous responses). No code change.

  3. epClientSecret audit (INFO-1) — grep usage; if unused in the package, delete the field from the public config interface. If reserved for future use, document the contract (server-only, never in providerProps()) with an inline comment.

Acceptance criteria

  • README has a "Security model" section enumerating the post-fixes guarantees
  • README has a "Deployment hardening" section with recommended edge/WAF rules
  • epClientSecret is either removed or comment-documented as server-only
  • CHANGELOG entry summarizes the breaking changes (tokenSurface default, allowedOrigins requirement) so consumers upgrading aren't surprised

Blocked by

User stories addressed

  • User story 10
  • User story 11
  • User story 12

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions