Skip to content

feat(security): improve document access controls - #515

Open
raphaelmansuy wants to merge 2 commits into
edgequake-mainfrom
codex/spec-180-document-access
Open

raphaelmansuy wants to merge 2 commits into
edgequake-mainfrom
codex/spec-180-document-access

Conversation

@raphaelmansuy

Copy link
Copy Markdown
Owner

Description

Adds governed sensitivity and security tags at upload, document edit, and bulk update. Enforces the resulting document scope across API, PDF, task, and MCP paths, with migration 225 and the SPEC-180 product/security documentation.

Type of change

  • New feature
  • Documentation update

Validation

  • 42 live Playwright E2E tests passed, including real RBAC/ABAC denial, revocation, RLS, rollback, replay, PDF, task, and MCP access checks.
  • 91 focused tests passed across Rust, Vitest, and live E2E.
  • Cargo build, cargo fmt check, strict targeted clippy, and release TypeScript typecheck passed.
  • 21 E2E screenshots are saved under specs/180-improve-sec-doc/e2e/screenshots/ and visually inspected.

Limits

Production load, object-store outage recovery, and a penetration test were not run; offline extraction validation does not claim model output quality.

Add governed sensitivity and security-tag workflows for uploads, document edits, and bulk updates. Enforce document scope across API, PDF, task, and MCP paths, with live security E2E coverage and SPEC-180 documentation.

Validation: 42 live Playwright E2E tests; 91 focused tests; cargo build, fmt, strict targeted clippy, and release TypeScript typecheck passed.
Pin the unreleased schema epoch for migration 225 and update compatible transitive TLS and constant-time crates to patched RustSec releases.

Validation: SPEC-150 epoch coverage passes; cargo check --workspace --locked --offline passes. Cargo audit still reports crypto-bigint 0.5.5 through OpenID Connect; its fixed major release is incompatible with elliptic-curve 0.13.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant