security: add evidence_class to audit entries for tool response assurance#322
Merged
Conversation
…ance Introduce evidence_class field on AuditEntry (hash-only | tls-pinned). The proxy sets tls-pinned when the catalog entry carries a real TLS fingerprint (not the dev placeholder) and the upstream URL is HTTPS. Verifiers can use this field to distinguish responses received over a verified TLS channel from those received without cert pinning. Documents both classes and the non-repudiation limitation in LIMITATIONS.md. Signed-off-by: Imran Siddique <imran.siddique@opaque.co>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds `evidence_class: str` (`hash-only` | `tls-pinned`) to `AuditEntry`. The proxy sets `tls-pinned` when the upstream server URL is HTTPS and the catalog entry carries a real TLS certificate fingerprint (not the dev placeholder `SHA256:AAA...=`).
Verifiers can now distinguish audit entries where the response server identity was cryptographically verified via a pinned TLS certificate from those where it was not. Documents both evidence classes and the non-repudiation limitation in `LIMITATIONS.md`.
Changes
Test plan
🤖 Generated with Claude Code