Architecture and Trust Boundaries

5 articles

Agent Security Agentic Permissions AI Agent Security AI Governance Evidence Ai Impact Ai Integration AI Red Teaming AI SDLC & Product Security AI Security AI Security Engineer Career Ai Security Engineering AI Security Foundations AI Security Monitoring AI Security Tools AI Supply Chain AI System Inventory Architecture and Trust Boundaries Ats Systems Attack Career Development Corporate Culture Corporate Culture And Leadership Culture Security Cyber Security cybersecurity Cybersecurity Strategy Data Exposure and Privacy Defend Detection Engineering Distributed Governance Distributed Systems Economic Governance Education Evaluation and Regression Testing Evidence Future of Work governance Governance And Resilience Governance Evidence and Customer Trust Governance, Risk & Compliance Hiring & Talent Hiring Strategy Incident Response & Observability Leadership And Governance LLM Application Security Logging and Telemetry Map MLOps & Platform Security Model and Provider Risk Model Supply Chain Operational Risk Organizational Governance Organizational Resilience Platform Governance Privacy & Data Protection Prompt Injection Psychological Safety psychometrics RAG Authorization RAG Security Recruitment And Talent Red Teaming & Evaluations red-team seceng-workbench Secure Architecture & Design Secure RAG Security Architecture Stochastic Governance Stochastic Resilience Systemic Resilience Talent Acquisition Technical Intelligence Threat Modeling Toolchain Integrity Training & Workshops Vendor Risk & Procurement Workforce Science Workplace Evolution

Map

The AI Security Operating Model: Who Owns What Across AppSec, MLOps, GRC, Legal, Privacy, and SOC

A credible AI security operating model assigns ownership across AppSec, product security, AI platform engineering, MLOps, data governance, privacy, legal, GRC, SOC, red team, procurement, and business teams. The goal is not companyal purity; the goal is clear accountability for controls, evidence, incidents, and claims.

10 min read

Map

The Future of AI Security Engineering: From AppSec to AgentSec to Autonomous SOCs

The future of AI Security Engineering is a platform discipline that extends AppSec into LLM applications, creates AgentSec for autonomous workflows, builds AI-native telemetry for detection and incident response, and turns governance into continuous evidence rather than annual paperwork.

9 min read

Defend

Secure AI Product Design: How Product Decisions Create or Reduce AI Risk

AI product decisions can create or reduce security risk by controlling autonomy, data visibility, uncertainty, approval design, reversibility, source attribution, workflow placement, and abuse resistance. Product security must be involved early enough to shape the feature, not merely review it after launch.

9 min read

Map

Threat Modeling LLM Applications: Data Flows, Trust Boundaries, Tool Calls, and Abuse Cases

LLM threat modeling should map assets, actors, data flows, trust boundaries, prompt assembly, retrieved content, model providers, tool calls, memory, outputs, identities, approvals, logs, and abuse cases. The output should become controls, tests, telemetry requirements, and incident-response assumptions.

10 min read

Defend

Least Privilege for AI Agents: Designing Permissions for Tools, APIs, Browsers, and Filesystems

AI agents need least privilege at the tool, API, browser, filesystem, credential, tenant, and action level. Safe design requires tool classification, read-only defaults, argument validation, scoped credentials, sandboxing, approval gates, and auditable enforcement outside the model.

13 min read