← All posts

Platform & Architecture

338 posts on platform & architecture.

Confidential Computing for AI: Protect Data During Processing

Confidential computing protects AI data and code while a CPU or GPU processes them inside a hardware-based, attested trusted execution environment. It complements encryption at rest and in transit. For enterprise AI, attestation, key release, workload identity, model routing, and request policy remain separate controls with separate evidence.

ai-securitycloud-securityarchitecturezero-trustidentity-and-authorization
Read post →

AI Threat Modeling: Boundaries and Evidence for Abuse Cases

AI threat modeling starts with assets and trust boundaries, then traces attacker paths across data, model, retrieval, agent, tool, identity, and application components. This guide combines NIST adversarial-machine-learning terminology with MITRE ATLAS techniques and turns the result into testable abuse cases with control owners and evidence requirements.

ai-securityllm-securityagentic-aiarchitecturezero-trustidentity-and-authorization
Read post →

Attribute-Based Access Control for AI at the Request Boundary

Attribute-based access control can turn an AI usage policy into a per-request decision. The useful design binds a verified subject, model route, requested operation, prompt classification, and current environment to a versioned rule. This guide defines the attribute contract, deny behavior, test cases, decision record, and the boundary between model authorization and downstream tool authorization.

ai-securityidentity-and-authorizationzero-trustpolicy-enforcementarchitecturellm-security
Read post →

AI Agent Kill Switch: A Shutdown Sequence That Actually Stops Work

An AI agent kill switch needs a defined shutdown sequence across intake, model routes, delegated credentials, tools, workers, and queued work. This guide turns that sequence into an engineering control with named owners, activation thresholds, preserved evidence, and a restart gate.

agentic-aiai-securityidentity-and-authorizationincident-responsepolicy-enforcementarchitecture
Read post →

Human-in-the-Loop AI Agents: The Approval State That Survives Pause and Resume

Human-in-the-loop agent control requires more than an approval button. A defensible implementation pauses the exact tool call, persists its identity and arguments, records the reviewer decision, and revalidates policy before execution resumes. This article maps that state machine, including nested-agent approvals, stale decisions, duplicate resumes, and the boundary between an HTTP policy decision and the orchestrator that performs the approved action.

agentic-aiai-securityidentity-and-authorizationpolicy-enforcementauditarchitecture
Read post →

SOC Analyst AI Risk Checklist for Incident Triage

This SOC analyst AI risk checklist turns an AI alert into a triage and incident decision. It fixes the incident threshold, telemetry join, scope estimate, evidence handling, containment test, recovery proof, and handoff record for governed model traffic while preserving the boundary around endpoint, vendor, and local execution paths.

ai-securityincident-responseforensic-auditauditpolicy-enforcementsoc-operations
Read post →

Salesforce Einstein Security: Map the Trust Layer Boundaries

Salesforce documents Trust Layer controls for data access, TLS, zero data retention with third-party LLM providers, masking, toxicity scoring, grounding, and audit. Each control answers a different security question. A defensible review maps those functions to Salesforce-managed traffic, CRM permissions, external model routes, application actions, and independent HTTP policy enforcement.

ai-securityllm-securityzero-trustpolicy-enforcementidentity-and-authorization
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 →

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 →