Identity and API
Identity follows the query through document retrieval.
Risk
Cross-user or cross-organization access.
Architecture controls
Validate sessions and tokens server-side, enforce limits and derive the tenant from a trusted identity.
Thiago Lima Soneti da Silva (Thiago Silva) — Cyber Architect and technical lead at Lima e Silva Tecnologia.
In focus · November 2026
Starting a task does not prove completion. Design agents with idempotent actions, recoverable checkpoints and delivery confirmation, while preserving access boundaries for tools and data.
Explore my profile ↗From question to answer, with controlled access.
Select a component to explore.
Query → identity → retrieval → model → response
Ingestion → index • Auditing spans the entire flow
Identity follows the query through document retrieval.
Cross-user or cross-organization access.
Validate sessions and tokens server-side, enforce limits and derive the tenant from a trusted identity.
Semantic search only within content allowed for this identity.
A relevant document may still be unauthorized.
Apply ACL and tenant restrictions before sending context to the model; propagate permission changes and revocations to the index.
Combines the question with retrieved passages to generate an answer.
Malicious instructions embedded in documents.
Treat documents as untrusted data, separate instructions, limit context and do not grant privileged tools to the model.
Returns an answer with verifiable references to the content used.
Data leakage or claims unsupported by sources.
Check data exposure, escape output, link authorized sources and acknowledge missing evidence.
Approved documents are classified, split and indexed.
Poisoned content or stale permissions.
Validate origin and format, scan files, record ownership and ACLs, encrypt and remove copies after revocation or deletion.
Correlates access, retrieval and generation decisions.
Missing evidence or sensitive data in logs.
Record decisions and correlation IDs with data minimization, defined retention, restricted access and alerts.
Illustrative reference architecture. This interaction explains security decisions; it does not run queries or send data to models.
Assign ownership for each control.
Device changes and recovery also establish trust.
Building code and authorizing production are different decisions.
Removing source access may leave usable copies.
Knowing an identifier is not authorization evidence.
Application encryption changes exposure boundaries and operations.
Separate execution, durable results and delivery; recover individual steps and test retries without duplicating business effects.
A query can reveal business intent without exposing its results. Classify and test query text as a separate asset.
Failure logs can cross the boundary between code and credentials. Test diagnostics, access and response without losing evidence.
Get new articles in your RSS reader. Copy the feed address and add it to Feedly, Inoreader or another reader.
AI-assisted curation · Sources: Amazon Builders’ Library — Making retries safe with idempotent APIs · AWS Lambda — Asynchronous errors and retries
Meet Privacy Guardian · Code Provenance Guardian · CVE Hunter · Agentes de Segurança
Cloud Guardrail Assurance · MCP Authorization Security Lab · Security Architecture Decision Lab · Security Resilience Lab
Explore projects ↗