Bind sender identities, add operator read surface, real serving layer
AUDIT-WP-0004 T03, T05, T06.
T03 - the receiver accepted whatever tenant and source a caller sent as long
as it held the one shared token, despite WP-0003 recording tenant isolation as
delivered. audit_core.senders binds each credential to the sources and tenants
it may assert, driven by AUDIT_CORE_SENDERS rather than literals. Identities
hold a list of tokens so rotation publishes the replacement alongside the
incumbent and needs no delivery gap. Read is a separate privilege from write,
so a sender credential cannot read the audit trail back.
T05 - lookup by event id, lookup by correlation id, and a dead-letter view.
Rejections are recorded rather than silently dropped. An event rejected for
carrying secret-shaped material has its payload withheld: storing it would
write that material into the audit store, which is what the rejection exists
to prevent. Reason and payload hash are kept so it stays traceable.
Replay is deliberately not built here. Idempotent replay is a property of the
durable store and building it against SQLite would produce a second
implementation to throw away; it lands with the Postgres backend in
AUDIT-WP-0005-T01.
T06 - serving moves to waitress with configurable threads and channel timeout,
installed in the image via the serve extra. Without it the entrypoint falls
back to a threaded wsgiref server with a socket timeout and graceful shutdown
on SIGTERM, and logs a warning so a deployment cannot quietly land on the
fallback. Metric counters deferred to WP-0005-T03 to be designed against the
real scrape path.
Tests 36 -> 46, covering cross-tenant and cross-source refusal, token
rotation, read/write privilege separation, correlation lookup, and payload
withholding on secret rejection.
Remaining in WP-0004: T04 redaction policy, which needs a decision on whether
a secret-shaped field is a rejection or a redaction.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 14:50:02 +02:00
|
|
|
"""Sender identities and what they are permitted to claim.
|
|
|
|
|
|
|
|
|
|
AUDIT-WP-0004-T03. WP-0003 recorded tenant isolation as delivered, but the
|
|
|
|
|
receiver accepted whatever ``tenant`` and ``source`` a caller sent as long as
|
|
|
|
|
it held the one shared token. This module binds a credential to the sources and
|
|
|
|
|
tenants it may write for, and drives that binding from configuration rather
|
|
|
|
|
than literals.
|
|
|
|
|
|
|
|
|
|
Each identity carries a *list* of tokens so a credential can be rotated without
|
|
|
|
|
a delivery gap: publish the replacement alongside the incumbent, move the
|
|
|
|
|
sender, then drop the old one.
|
|
|
|
|
"""
|
|
|
|
|
|
|
|
|
|
from __future__ import annotations
|
|
|
|
|
|
|
|
|
|
import hmac
|
|
|
|
|
import json
|
|
|
|
|
import os
|
|
|
|
|
from dataclasses import dataclass, field
|
|
|
|
|
from typing import Any, Iterable
|
|
|
|
|
|
Redact secret-shaped fields by default, countable per field path
AUDIT-WP-0004-T04, closing the workplan.
Decision (Bernd): default to redaction, allow rejection per sender. Losing an
audit record over one field is worse than storing it masked, but a
higher-assurance channel must be able to refuse rather than mask. secret_policy
is set per sender identity in AUDIT_CORE_SENDERS and defaults to redact.
Detection now covers the whole payload at any depth, including lists, rather
than only the top level of data. Under redaction the value is masked and the
key is preserved: dropping the key would hide that the sender transmitted the
field at all, which is exactly what an operator needs in order to stop it. The
stored record carries details.redaction with policy and affected paths, so a
reader never has to infer whether what they see is what was sent.
Idempotency is unaffected - the payload hash is taken over the original request
body, so redaction is deterministic and a resubmission still reconciles as a
duplicate.
Both outcomes are counted durably by sender, source, action and field path,
exposed at GET /v1/secret-findings. Per-path aggregation is the point: the
actionable unit is "stop emitting data.auth.token on membership.added", not
"there were 47 redactions". Counters survive restart because the fix they drive
lives in another service.
Contract doc updated to match. Tests 46 -> 50. WP-0004 is finished.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 16:02:22 +02:00
|
|
|
from audit_core.redaction import POLICIES, POLICY_REDACT
|
|
|
|
|
|
Bind sender identities, add operator read surface, real serving layer
AUDIT-WP-0004 T03, T05, T06.
T03 - the receiver accepted whatever tenant and source a caller sent as long
as it held the one shared token, despite WP-0003 recording tenant isolation as
delivered. audit_core.senders binds each credential to the sources and tenants
it may assert, driven by AUDIT_CORE_SENDERS rather than literals. Identities
hold a list of tokens so rotation publishes the replacement alongside the
incumbent and needs no delivery gap. Read is a separate privilege from write,
so a sender credential cannot read the audit trail back.
T05 - lookup by event id, lookup by correlation id, and a dead-letter view.
Rejections are recorded rather than silently dropped. An event rejected for
carrying secret-shaped material has its payload withheld: storing it would
write that material into the audit store, which is what the rejection exists
to prevent. Reason and payload hash are kept so it stays traceable.
Replay is deliberately not built here. Idempotent replay is a property of the
durable store and building it against SQLite would produce a second
implementation to throw away; it lands with the Postgres backend in
AUDIT-WP-0005-T01.
T06 - serving moves to waitress with configurable threads and channel timeout,
installed in the image via the serve extra. Without it the entrypoint falls
back to a threaded wsgiref server with a socket timeout and graceful shutdown
on SIGTERM, and logs a warning so a deployment cannot quietly land on the
fallback. Metric counters deferred to WP-0005-T03 to be designed against the
real scrape path.
Tests 36 -> 46, covering cross-tenant and cross-source refusal, token
rotation, read/write privilege separation, correlation lookup, and payload
withholding on secret rejection.
Remaining in WP-0004: T04 redaction policy, which needs a decision on whether
a secret-shaped field is a rejection or a redaction.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 14:50:02 +02:00
|
|
|
WILDCARD = "*"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@dataclass(frozen=True)
|
|
|
|
|
class SenderIdentity:
|
|
|
|
|
"""A credential holder and the claims it is allowed to make."""
|
|
|
|
|
|
|
|
|
|
name: str
|
|
|
|
|
tokens: tuple[str, ...]
|
|
|
|
|
sources: frozenset[str]
|
|
|
|
|
tenants: frozenset[str] = field(default_factory=lambda: frozenset({WILDCARD}))
|
|
|
|
|
may_write: bool = True
|
|
|
|
|
may_read: bool = False
|
Redact secret-shaped fields by default, countable per field path
AUDIT-WP-0004-T04, closing the workplan.
Decision (Bernd): default to redaction, allow rejection per sender. Losing an
audit record over one field is worse than storing it masked, but a
higher-assurance channel must be able to refuse rather than mask. secret_policy
is set per sender identity in AUDIT_CORE_SENDERS and defaults to redact.
Detection now covers the whole payload at any depth, including lists, rather
than only the top level of data. Under redaction the value is masked and the
key is preserved: dropping the key would hide that the sender transmitted the
field at all, which is exactly what an operator needs in order to stop it. The
stored record carries details.redaction with policy and affected paths, so a
reader never has to infer whether what they see is what was sent.
Idempotency is unaffected - the payload hash is taken over the original request
body, so redaction is deterministic and a resubmission still reconciles as a
duplicate.
Both outcomes are counted durably by sender, source, action and field path,
exposed at GET /v1/secret-findings. Per-path aggregation is the point: the
actionable unit is "stop emitting data.auth.token on membership.added", not
"there were 47 redactions". Counters survive restart because the fix they drive
lives in another service.
Contract doc updated to match. Tests 46 -> 50. WP-0004 is finished.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 16:02:22 +02:00
|
|
|
# Secret-shaped field handling. Defaults to redact-and-accept, so a
|
|
|
|
|
# legitimate event is not lost over one field; a higher-assurance channel
|
|
|
|
|
# can be set to reject instead (AUDIT-WP-0004-T04).
|
|
|
|
|
secret_policy: str = POLICY_REDACT
|
Bind sender identities, add operator read surface, real serving layer
AUDIT-WP-0004 T03, T05, T06.
T03 - the receiver accepted whatever tenant and source a caller sent as long
as it held the one shared token, despite WP-0003 recording tenant isolation as
delivered. audit_core.senders binds each credential to the sources and tenants
it may assert, driven by AUDIT_CORE_SENDERS rather than literals. Identities
hold a list of tokens so rotation publishes the replacement alongside the
incumbent and needs no delivery gap. Read is a separate privilege from write,
so a sender credential cannot read the audit trail back.
T05 - lookup by event id, lookup by correlation id, and a dead-letter view.
Rejections are recorded rather than silently dropped. An event rejected for
carrying secret-shaped material has its payload withheld: storing it would
write that material into the audit store, which is what the rejection exists
to prevent. Reason and payload hash are kept so it stays traceable.
Replay is deliberately not built here. Idempotent replay is a property of the
durable store and building it against SQLite would produce a second
implementation to throw away; it lands with the Postgres backend in
AUDIT-WP-0005-T01.
T06 - serving moves to waitress with configurable threads and channel timeout,
installed in the image via the serve extra. Without it the entrypoint falls
back to a threaded wsgiref server with a socket timeout and graceful shutdown
on SIGTERM, and logs a warning so a deployment cannot quietly land on the
fallback. Metric counters deferred to WP-0005-T03 to be designed against the
real scrape path.
Tests 36 -> 46, covering cross-tenant and cross-source refusal, token
rotation, read/write privilege separation, correlation lookup, and payload
withholding on secret rejection.
Remaining in WP-0004: T04 redaction policy, which needs a decision on whether
a secret-shaped field is a rejection or a redaction.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 14:50:02 +02:00
|
|
|
|
|
|
|
|
def __post_init__(self) -> None:
|
|
|
|
|
if not self.name:
|
|
|
|
|
raise ValueError("sender identity needs a name")
|
Redact secret-shaped fields by default, countable per field path
AUDIT-WP-0004-T04, closing the workplan.
Decision (Bernd): default to redaction, allow rejection per sender. Losing an
audit record over one field is worse than storing it masked, but a
higher-assurance channel must be able to refuse rather than mask. secret_policy
is set per sender identity in AUDIT_CORE_SENDERS and defaults to redact.
Detection now covers the whole payload at any depth, including lists, rather
than only the top level of data. Under redaction the value is masked and the
key is preserved: dropping the key would hide that the sender transmitted the
field at all, which is exactly what an operator needs in order to stop it. The
stored record carries details.redaction with policy and affected paths, so a
reader never has to infer whether what they see is what was sent.
Idempotency is unaffected - the payload hash is taken over the original request
body, so redaction is deterministic and a resubmission still reconciles as a
duplicate.
Both outcomes are counted durably by sender, source, action and field path,
exposed at GET /v1/secret-findings. Per-path aggregation is the point: the
actionable unit is "stop emitting data.auth.token on membership.added", not
"there were 47 redactions". Counters survive restart because the fix they drive
lives in another service.
Contract doc updated to match. Tests 46 -> 50. WP-0004 is finished.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 16:02:22 +02:00
|
|
|
if self.secret_policy not in POLICIES:
|
|
|
|
|
raise ValueError(
|
|
|
|
|
f"sender {self.name!r}: secret_policy must be one of {POLICIES}, "
|
|
|
|
|
f"got {self.secret_policy!r}"
|
|
|
|
|
)
|
Bind sender identities, add operator read surface, real serving layer
AUDIT-WP-0004 T03, T05, T06.
T03 - the receiver accepted whatever tenant and source a caller sent as long
as it held the one shared token, despite WP-0003 recording tenant isolation as
delivered. audit_core.senders binds each credential to the sources and tenants
it may assert, driven by AUDIT_CORE_SENDERS rather than literals. Identities
hold a list of tokens so rotation publishes the replacement alongside the
incumbent and needs no delivery gap. Read is a separate privilege from write,
so a sender credential cannot read the audit trail back.
T05 - lookup by event id, lookup by correlation id, and a dead-letter view.
Rejections are recorded rather than silently dropped. An event rejected for
carrying secret-shaped material has its payload withheld: storing it would
write that material into the audit store, which is what the rejection exists
to prevent. Reason and payload hash are kept so it stays traceable.
Replay is deliberately not built here. Idempotent replay is a property of the
durable store and building it against SQLite would produce a second
implementation to throw away; it lands with the Postgres backend in
AUDIT-WP-0005-T01.
T06 - serving moves to waitress with configurable threads and channel timeout,
installed in the image via the serve extra. Without it the entrypoint falls
back to a threaded wsgiref server with a socket timeout and graceful shutdown
on SIGTERM, and logs a warning so a deployment cannot quietly land on the
fallback. Metric counters deferred to WP-0005-T03 to be designed against the
real scrape path.
Tests 36 -> 46, covering cross-tenant and cross-source refusal, token
rotation, read/write privilege separation, correlation lookup, and payload
withholding on secret rejection.
Remaining in WP-0004: T04 redaction policy, which needs a decision on whether
a secret-shaped field is a rejection or a redaction.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 14:50:02 +02:00
|
|
|
if not self.tokens or any(not t for t in self.tokens):
|
|
|
|
|
raise ValueError(f"sender {self.name!r} needs at least one non-empty token")
|
|
|
|
|
if not self.sources:
|
|
|
|
|
raise ValueError(f"sender {self.name!r} needs at least one permitted source")
|
|
|
|
|
|
|
|
|
|
def permits_source(self, source: str) -> bool:
|
|
|
|
|
return WILDCARD in self.sources or source in self.sources
|
|
|
|
|
|
|
|
|
|
def permits_tenant(self, tenant: str) -> bool:
|
|
|
|
|
"""Whether this identity may write for ``tenant``.
|
|
|
|
|
|
|
|
|
|
Tenant identifiers are opaque here. Their shape
|
|
|
|
|
(``tenant:<grouping>:<name>``) is owned by the IAM Profile and
|
|
|
|
|
tenant-engine; matching is exact, never parsed or pattern-derived.
|
|
|
|
|
"""
|
|
|
|
|
return WILDCARD in self.tenants or tenant in self.tenants
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
class SenderRegistry:
|
|
|
|
|
"""Resolves a credential to the identity that holds it."""
|
|
|
|
|
|
|
|
|
|
def __init__(self, identities: Iterable[SenderIdentity]) -> None:
|
|
|
|
|
self.identities = tuple(identities)
|
|
|
|
|
if not self.identities:
|
|
|
|
|
raise ValueError("at least one sender identity is required")
|
|
|
|
|
|
|
|
|
|
def authenticate(self, authorization_header: str | None) -> SenderIdentity | None:
|
|
|
|
|
"""Return the matching identity, or None.
|
|
|
|
|
|
|
|
|
|
Every candidate token is compared even after a match is found, so the
|
|
|
|
|
work done does not depend on which credential was supplied or how many
|
|
|
|
|
identities precede it.
|
|
|
|
|
"""
|
|
|
|
|
supplied = str(authorization_header or "")
|
|
|
|
|
matched: SenderIdentity | None = None
|
|
|
|
|
for identity in self.identities:
|
|
|
|
|
for token in identity.tokens:
|
|
|
|
|
try:
|
|
|
|
|
hit = hmac.compare_digest(supplied, f"Bearer {token}")
|
|
|
|
|
except TypeError:
|
|
|
|
|
# compare_digest rejects non-ASCII str; such a header is
|
|
|
|
|
# simply not a valid credential.
|
|
|
|
|
hit = False
|
|
|
|
|
if hit and matched is None:
|
|
|
|
|
matched = identity
|
|
|
|
|
return matched
|
|
|
|
|
|
|
|
|
|
@classmethod
|
|
|
|
|
def from_env(cls, env: dict[str, str] | None = None) -> "SenderRegistry":
|
|
|
|
|
"""Build a registry from ``AUDIT_CORE_SENDERS`` (JSON).
|
|
|
|
|
|
|
|
|
|
Shape::
|
|
|
|
|
|
|
|
|
|
[{"name": "user-engine",
|
|
|
|
|
"tokens": ["current", "next"],
|
|
|
|
|
"sources": ["user-engine"],
|
|
|
|
|
"tenants": ["tenant:friendly:binky"],
|
|
|
|
|
"may_read": false}]
|
|
|
|
|
|
|
|
|
|
``tenants`` defaults to ``["*"]``. Omitting it is a deliberate choice to
|
|
|
|
|
accept any tenant from that sender and should be justified per sender,
|
|
|
|
|
not adopted by default.
|
|
|
|
|
"""
|
|
|
|
|
env = env if env is not None else dict(os.environ)
|
|
|
|
|
raw = env.get("AUDIT_CORE_SENDERS")
|
|
|
|
|
if raw:
|
|
|
|
|
return cls(_parse_identities(raw))
|
|
|
|
|
|
|
|
|
|
legacy = (env.get("AUDIT_CORE_INGEST_TOKEN") or "").strip()
|
|
|
|
|
if not legacy:
|
|
|
|
|
raise ValueError(
|
|
|
|
|
"no sender configuration: set AUDIT_CORE_SENDERS (preferred) "
|
|
|
|
|
"or AUDIT_CORE_INGEST_TOKEN"
|
|
|
|
|
)
|
|
|
|
|
# Legacy single-token form. Kept so an existing deployment keeps
|
|
|
|
|
# working, but it grants every tenant — which is what T03 exists to
|
|
|
|
|
# stop, so it is deliberately noisy about what it is.
|
|
|
|
|
return cls([
|
|
|
|
|
SenderIdentity(
|
|
|
|
|
name="legacy-ingest-token",
|
|
|
|
|
tokens=(legacy,),
|
|
|
|
|
sources=frozenset({"user-engine"}),
|
|
|
|
|
tenants=frozenset({WILDCARD}),
|
|
|
|
|
)
|
|
|
|
|
])
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
def _parse_identities(raw: str) -> list[SenderIdentity]:
|
|
|
|
|
try:
|
|
|
|
|
entries = json.loads(raw)
|
|
|
|
|
except json.JSONDecodeError as exc:
|
|
|
|
|
raise ValueError(f"AUDIT_CORE_SENDERS is not valid JSON: {exc}") from exc
|
|
|
|
|
if not isinstance(entries, list) or not entries:
|
|
|
|
|
raise ValueError("AUDIT_CORE_SENDERS must be a non-empty JSON list")
|
|
|
|
|
return [_identity_from(entry) for entry in entries]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
def _identity_from(entry: Any) -> SenderIdentity:
|
|
|
|
|
if not isinstance(entry, dict):
|
|
|
|
|
raise ValueError("each sender entry must be an object")
|
|
|
|
|
tokens = entry.get("tokens") or ([entry["token"]] if entry.get("token") else [])
|
|
|
|
|
return SenderIdentity(
|
|
|
|
|
name=str(entry.get("name") or ""),
|
|
|
|
|
tokens=tuple(str(t) for t in tokens),
|
|
|
|
|
sources=frozenset(str(s) for s in (entry.get("sources") or [])),
|
|
|
|
|
tenants=frozenset(str(t) for t in (entry.get("tenants") or [WILDCARD])),
|
|
|
|
|
may_write=bool(entry.get("may_write", True)),
|
|
|
|
|
may_read=bool(entry.get("may_read", False)),
|
Redact secret-shaped fields by default, countable per field path
AUDIT-WP-0004-T04, closing the workplan.
Decision (Bernd): default to redaction, allow rejection per sender. Losing an
audit record over one field is worse than storing it masked, but a
higher-assurance channel must be able to refuse rather than mask. secret_policy
is set per sender identity in AUDIT_CORE_SENDERS and defaults to redact.
Detection now covers the whole payload at any depth, including lists, rather
than only the top level of data. Under redaction the value is masked and the
key is preserved: dropping the key would hide that the sender transmitted the
field at all, which is exactly what an operator needs in order to stop it. The
stored record carries details.redaction with policy and affected paths, so a
reader never has to infer whether what they see is what was sent.
Idempotency is unaffected - the payload hash is taken over the original request
body, so redaction is deterministic and a resubmission still reconciles as a
duplicate.
Both outcomes are counted durably by sender, source, action and field path,
exposed at GET /v1/secret-findings. Per-path aggregation is the point: the
actionable unit is "stop emitting data.auth.token on membership.added", not
"there were 47 redactions". Counters survive restart because the fix they drive
lives in another service.
Contract doc updated to match. Tests 46 -> 50. WP-0004 is finished.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 16:02:22 +02:00
|
|
|
secret_policy=str(entry.get("secret_policy", POLICY_REDACT)),
|
Bind sender identities, add operator read surface, real serving layer
AUDIT-WP-0004 T03, T05, T06.
T03 - the receiver accepted whatever tenant and source a caller sent as long
as it held the one shared token, despite WP-0003 recording tenant isolation as
delivered. audit_core.senders binds each credential to the sources and tenants
it may assert, driven by AUDIT_CORE_SENDERS rather than literals. Identities
hold a list of tokens so rotation publishes the replacement alongside the
incumbent and needs no delivery gap. Read is a separate privilege from write,
so a sender credential cannot read the audit trail back.
T05 - lookup by event id, lookup by correlation id, and a dead-letter view.
Rejections are recorded rather than silently dropped. An event rejected for
carrying secret-shaped material has its payload withheld: storing it would
write that material into the audit store, which is what the rejection exists
to prevent. Reason and payload hash are kept so it stays traceable.
Replay is deliberately not built here. Idempotent replay is a property of the
durable store and building it against SQLite would produce a second
implementation to throw away; it lands with the Postgres backend in
AUDIT-WP-0005-T01.
T06 - serving moves to waitress with configurable threads and channel timeout,
installed in the image via the serve extra. Without it the entrypoint falls
back to a threaded wsgiref server with a socket timeout and graceful shutdown
on SIGTERM, and logs a warning so a deployment cannot quietly land on the
fallback. Metric counters deferred to WP-0005-T03 to be designed against the
real scrape path.
Tests 36 -> 46, covering cross-tenant and cross-source refusal, token
rotation, read/write privilege separation, correlation lookup, and payload
withholding on secret rejection.
Remaining in WP-0004: T04 redaction policy, which needs a decision on whether
a secret-shaped field is a rejection or a redaction.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-10 14:50:02 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
def development_registry(token: str) -> SenderRegistry:
|
|
|
|
|
"""A single permissive sender, for tests and local development.
|
|
|
|
|
|
|
|
|
|
Accepts any tenant. Not a production configuration — production binds each
|
|
|
|
|
sender to the tenants it may write for via ``AUDIT_CORE_SENDERS``.
|
|
|
|
|
"""
|
|
|
|
|
return SenderRegistry([
|
|
|
|
|
SenderIdentity(
|
|
|
|
|
name="development",
|
|
|
|
|
tokens=(token,),
|
|
|
|
|
sources=frozenset({"user-engine"}),
|
|
|
|
|
tenants=frozenset({WILDCARD}),
|
|
|
|
|
may_read=True,
|
|
|
|
|
)
|
|
|
|
|
])
|