Cloud SQL: database location does not finish the security review
Regional administrative API endpoints raise an architecture question: where do the operations that manage your data travel?
Read article ↗Weekly edition · PT / EN / ES
Articles.
Cybersecurity news through an architecture lens.
Selected news and practical analysis on cloud, identity, DevSecOps and AI security.
Explore the 50-article collection ↓
Analysis and articles
AI agents: define the approval contract before granting autonomy
The agent security debate calls for a concrete architecture decision: which changes may an agent execute without approval?
Read article ↗Content produced with AI assistance for Thiago Silva’s website. Independent editorial analysis; it does not represent clients or employers.
50 · PT / EN / ES
Security architecture · 2026 collection
50 short articles on architecture decisions, identity, APIs, DevSecOps, cloud and AI security. A January–September editorial reading path to explore by topic.
Collection published on September 12, 2026. Months organize the reading path; they are not earlier publication dates.
January 2026
Access control: who decides and who executes?
Clear responsibilities prevent ownerless permissions.
Read article ↗Attack surface: include the forgotten paths
Reviewing only the main application misses integrations.
Read article ↗Authentication: design beyond login
Device changes and recovery also establish trust.
Read article ↗Authorization: turn business rules into testable decisions
A user role alone does not explain resource access.
Read article ↗CI/CD: every stage carries a trust boundary
Building code and authorizing production are different decisions.
Read article ↗CSP: treat adoption as a dependency migration
A sustainable policy needs script owners.
Read article ↗February 2026
CSRF: review state-changing operations
Risk depends on how the browser sends session authority.
Read article ↗Additional encryption: which threat does it address?
Application encryption changes exposure boundaries and operations.
Read article ↗Database roles: separate queries, maintenance and recovery
A shared credential hides distinct operational decisions.
Read article ↗Availability: budget expensive operations
Request counts can hide large differences in work.
Read article ↗SBOM: from component list to response decision
Inventory must connect to running software.
Read article ↗Containers: follow the review into runtime
An approved image still depends on deployment permissions.
Read article ↗March 2026
API errors: a contract for clients and operations
Public responses and internal diagnostics serve different audiences.
Read article ↗Uploads: receiving a file does not release it
Model states between ingestion, inspection and use.
Read article ↗Account recovery: support is part of the control
An exceptional procedure can redefine trust.
Read article ↗GitHub Actions: who can change the build tool?
Pipeline dependencies deserve code-level scrutiny.
Read article ↗Security headers: own the final response
CDN, proxy and application may produce different settings.
Read article ↗Infrastructure as code: return manual exceptions to the workflow
Repositories represent environments only when differences are reconciled.
Read article ↗April 2026
Input validation: valid format does not guarantee meaning
Rules must understand the operation's domain.
Read article ↗BOLA and IDOR: review the actual object
Knowing an identifier is not authorization evidence.
Read article ↗JWT: trust extends beyond signatures
Each consumer must know which tokens it may accept.
Read article ↗Key management: plan retirement before rotation
Changing the active key does not end historical dependencies.
Read article ↗Kubernetes: namespaces do not finish isolation analysis
Boundaries must account for shared resources.
Read article ↗Prompt injection: keep authority outside retrieved text
External documents may inform answers without granting permissions.
Read article ↗May 2026
Logs: start with the incident question
Event volume is not investigation capability.
Read article ↗MCP: tool changes are trust changes
An agent's tool catalog needs governance.
Read article ↗Microservices: preserve decision context when delegating
Technical identity alone does not explain the user's request.
Read article ↗Multitenancy: extend isolation into the cache
Correct database and API controls cannot fix ambiguous cache keys.
Read article ↗MFA: track exceptions as carefully as adoption
High coverage can conceal important alternative paths.
Read article ↗Segmentation: review permitted outbound traffic
Connection destinations are part of the exposure boundary.
Read article ↗June 2026
OAuth: distinguish clients before designing the flow
Mobile apps, browsers and backends have different boundaries.
Read article ↗Passwords: modernization needs a migration plan
Changing the standard does not update every account.
Read article ↗Dynamic queries: separate values from structure choices
Flexible filters need a bounded contract.
Read article ↗RAG: revocation must reach retrievable content
Removing source access may leave usable copies.
Read article ↗REST APIs: protect operation order
Individually correct endpoints can form an incorrect workflow.
Read article ↗SAML SSO: rehearse trust changes
Integrations must survive certificate changes.
Read article ↗July 2026
Secrets: emergency rotation must work under pressure
Central storage does not replace rehearsed revocation.
Read article ↗AI models: record what actually changed in a release
Behavior depends on more than the model file.
Read article ↗AWS and GCP: turn shared responsibility into tasks
Assign ownership for each control.
Read article ↗Code review: prioritize trust-changing modifications
Diff size does not measure security impact.
Read article ↗AI-generated code: acceptance remains an engineering decision
Generation speed does not replace behavioral understanding.
Read article ↗Secure design: defaults are product decisions
The easiest path often determines actual behavior.
Read article ↗August 2026
SSRF: fetching a URL grants network capability
The feature needs destination and behavior boundaries.
Read article ↗Sessions: interface logout must match access state
Logout becomes distributed across multiple consumers.
Read article ↗Supply chain: release the artifact that was assessed
Rebuilding at the last step can change the trust unit.
Read article ↗Threat modeling: end with testable decisions
Useful diagrams connect threats to actions and owners.
Read article ↗Transactions: confirmation must represent execution
Users should authorize the parameters producing the effect.
Read article ↗TLS: review the full path to the data consumer
The browser padlock describes only part of the architecture.
Read article ↗September 2026
Privacy by architecture: remove unnecessary data
Minimization starts before storage protection choices.
Read article ↗Vulnerabilities: prioritize the affected-system decision
Component severity is an input, not the whole context.
Read article ↗Subscribe via RSS
Get new articles in your RSS reader. Copy the feed address and add it to Feedly, Inoreader or another reader.