← All posts

Platform & Architecture

243 posts on platform & architecture.

Claude Connectors Security: Controlling Remote MCP Server Access

Claude connectors give an application a route to approved remote MCP servers. Secure deployments need a defined server inventory, authorization at the MCP server, narrow tool permissions, trusted connector configuration, and request-level policy for the LLM traffic that begins the flow. This article maps those controls to their actual boundaries.

ai-securityagentic-aillm-securityprompt-injectionidentity-and-authorizationpolicy-enforcement
Read post →

Security Architect AI Risk Checklist for Design Approval

This security architect AI risk checklist turns one proposed AI architecture into an approved, rejected, or conditional design decision before implementation. Seven checks bind the decision to a fixed trust boundary, identity flow, control allocation, failure model, evidence contract, external dependencies, and explicit assumptions. Release authorization and recurring risk reporting remain separate decisions.

ai-securityai-governancearchitecturezero-trustidentity-and-authorizationpolicy-enforcement
Read post →

ML Engineer AI Risk Checklist for Model Promotion

This ML engineer AI risk checklist turns model promotion into a signed engineering decision. It fixes the intended use, model and dataset lineage, evaluation conditions, artifact integrity, serving configuration, runtime policy contract, monitoring thresholds, rollback proof, and objective evidence required before a model release can receive production traffic.

ai-securityai-governancenist-ai-rmfdevsecopspolicy-enforcementarchitecture
Read post →

Vector Database Security Controls for Retrieval and Tenant Isolation

Vector database security controls start with identity-bound retrieval, tenant or namespace isolation, and provenance that survives chunking and re-indexing. They continue with negative tests, query evidence, deletion mapping, and inspection of the assembled prompt at the HTTP model boundary. Storage and request-path owners have separate enforcement jobs.

ai-securityllm-securityidentity-and-authorizationarchitecturezero-trustaudit
Read post →

Platform Engineer AI Risk Checklist for Material Changes

This platform engineer AI risk checklist turns a material AI service change into a signed go/no-go decision. Seven checks bind the decision to the exact route and identity contract, approved provider or model, policy version, tested failure behavior, rollback proof, latency result and emitted evidence. It is a change gate, separate from recurring platform reporting.

ai-securityai-governancezero-trustpolicy-enforcementarchitecturedevsecops
Read post →

AWS Bedrock Security: Guardrails, IAM, and Privacy Gaps

AWS Bedrock security uses Guardrails for content, PrivateLink for a private API path, and IAM for API access. This guide shows what each control covers, what Bedrock privacy settings govern, and where per-request authorization remains with the application or a separate policy layer.

ai-securitycloud-securityllm-securityidentity-and-authorizationarchitecturezero-trust
Read post →

Anthropic API Gateway: Identity, Policy, and Claude API Evidence

An Anthropic API gateway adds identity-aware policy and an audit record to Claude API requests. This guide maps the Messages API, batches, streaming responses, prompt caching, and computer-use response blocks to the evidence an enterprise needs for each routed request.

ai-securityllmpolicy-enforcementinline-enforcementarchitecture
Read post →

Perplexity Enterprise Security: SSO, SCIM, and Connector Controls

Perplexity Enterprise security covers SSO, SCIM, sharing, files, connectors, and retention. Review those workspace controls, then test each routed AI request for its authenticated principal, source context, selected model destination, policy version, and decision record.

ai-securitycloud-securityidentity-and-authorizationzero-trustpolicy-enforcementdata-loss-prevention
Read post →

Ghostjacking: Tenet Turned Blocked Requests Into Agent Instructions at DEF CON 34

Tenet Security presented Ghostjacking at DEF CON 34 on August 9, 2026. An attacker sends a request designed to be blocked, the firewall logs the payload verbatim, and an AI agent asked to review that log follows the attacker''s text as instruction. In the demonstrated chain the agent rewrote DNS records to point at attacker infrastructure. This piece walks the mechanism step by step and separates the observability fixes from the two controls that live on the AI request path.

llm-securityagentic-aiprompt-injectionai-securitypolicy-enforcementidentity-and-authorization
Read post →

Self-Replicating Prompt Injection Makes Agent Output a Containment Problem

OpenAI disclosed on September 25, 2026 that its GPT-Red red-teaming agent found prompt injections that copy themselves into the next email, file write or code comment. The payload has two goals at once: do the attacker bidding and get reproduced in the output. That shifts the control point from the inbound prompt to the outbound response, which is where an identity-aware HTTP enforcement layer can inspect what an agent is about to publish.

prompt-injectionai-securityagentic-aiai-gatewayincident-response
Read post →

AI Gateway vs LLM Router: The Architectural Distinction That Matters for Enforcement

An LLM router picks the cheapest or fastest model for a given prompt. An AI gateway evaluates whether the request is permitted before any model receives it. The router optimizes cost and latency. The gateway enforces identity-bound policy and produces a per-decision audit record. This piece walks through the architectural distinction, where the two functions overlap, and why an enterprise running regulated workloads needs the gateway capability regardless of whether routing is in scope.

ai-gatewayllm-routerengineeringarchitecturepolicy-enforcement
Read post →

AI Gateway vs API Gateway: What Changes When the Payload Is a Prompt

An API gateway enforces auth, rate limits, and routing on REST and gRPC calls. An AI gateway adds prompt classification, identity-bound policy at the request payload level, and per-decision audit records. The two answer different questions about the same network position. This piece walks through the architectural distinction, the auth model differences, what an API gateway cannot enforce at the prompt layer, and where the two should sit together in production.

ai-gatewayapi-gatewayengineeringarchitecturepolicy-enforcement
Read post →