Unverified50% confidenceConceptExact time
In SAML and JWT, the signature protects "the bytes that were selected," while the semantic correctness of the selection logic often goes unverified.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen validating a JWT, it is not sufficient to only verify the signature; standard claims such as exp, nbf, iss, and aud must also be strictly validated, and tokens that are expired or have mismatched audiences must be rejected.71% similarUnverifiedFor operations involving modifying funds, customer status or infrastructure configuration, the HITL approval gate is non-negotiable; the approver signs the cryptographically hashed payload parameters rather than the LLM's textual description.64% similarUnverifiedDevelopers should not implement SAML or XML signature verification themselves, but should use mature libraries that have been thoroughly audited.64% similarUnverifiedThe SAML specification requires the use of Exclusive Canonicalization (Exclusive C14N), which includes only the namespace declarations actually used, avoiding irrelevant declarations from ancestor nodes polluting the canonicalization result.60% similarUnverifiedThe verification conclusion of AgentLog-MCP is not derived by reading a status flag bit, but is recalculated in real time from hash values and signatures, so tampering with a flag bit cannot pass the check.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1069719API
curl https://kongchang.com/api/v1/knowledge/claims/1069719MCP
get_claim(id=1069719)