---
id: TST-COM-CAT-011
title: Catalog Security Verification
kind: api-lifecycle
product_area: commerce
module: catalog
revision: 1
status: draft
product_intent: proposed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/catalog/tests/e2e/catalog-security.e2e.spec.js
implements:
  - ATS-COM-CAT-005-06
  - ATS-COM-CAT-008-06
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: 'Suite-owned workspace keys and database fixtures, removed by its cleanup hooks.'
binding_evidence:
  - scenario: ATS-COM-CAT-005-06
    source: >-
      services-commerce:modules/catalog/tests/e2e/catalog-security.e2e.spec.js#refuses a read-only
      principal every write, 403 permission_missing
  - scenario: ATS-COM-CAT-008-06
    source: >-
      services-commerce:modules/catalog/tests/e2e/catalog-security.e2e.spec.js#is served with no
      security context, acting in the path’s tenant alone
  - scenario: ATS-COM-CAT-008-06
    source: >-
      services-commerce:modules/catalog/tests/e2e/catalog-security.e2e.spec.js#is refused by the
      tenant access gate in a tenant Platform has no row for (403 TenantUnavailable)
  - scenario: ATS-COM-CAT-008-06
    source: >-
      services-commerce:modules/catalog/tests/e2e/catalog-security.e2e.spec.js#ignores a signed
      context it is handed: no diagnosis, the public prices
evidence:
  - 'services-commerce:modules/catalog/tests/e2e/catalog-security.e2e.spec.js'
  - >-
    services-commerce:modules/catalog/tests/e2e/catalog-security.e2e.spec.js#Real: the composed
    handler, the routes, PostgreSQL.
  - >-
    services-commerce:modules/catalog/tests/e2e/catalog-security.e2e.spec.js#Doubled: the signing
    key pair, the ports (fixtures).
execution_constraints:
  - No execution is performed in this documentation back-fill.
verification_boundary: >-
  Bindings identify the existing assertions contributing to each scenario; several suites can
  jointly cover a compound scenario.
---

# Catalog Security Verification

## Verification Boundary

The composed API handler runs locally with signed caller contexts and the integration database. Its route, mapping, permission and persistence assertions establish the local API boundary.

## What This Suite Proves

The catalog security assertions contribute to the scenarios listed in the register. Each binding retains its exact source test anchor so a reviewer can distinguish an individual contribution from the complete scenario.

## What It Does Not Prove

The register records source inspection only. It establishes no run result, delivery qualification or Product approval.

## Real Dependencies and Test Doubles

PostgreSQL and the services called by the suite are real. External service ports, file storage and queues may use the fixtures declared by the suite and its support helpers.

## Must Not Be Doubled

Keep the asserted database constraints, transactions, service functions and execution contexts real. For API suites, preserve the dispatcher and permission enforcement.