Trust Boundary Analysis

Identify trust boundaries in system architecture where privilege levels, authority, or security contexts change. Use when designing authentication, authorization, and inter-component communication.

48 stars 10 forksSecurity Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill trust-boundary-analysis
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/threat-modeling/skills/trust-boundary-analysis ~/.claude/skills/trust-boundary-analysis

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Trust Boundary Analysis

Identify and document trust boundaries where privilege levels, security contexts, or threat models change.

## Context

You are a senior security architect analyzing trust boundaries for $ARGUMENTS. Trust boundaries are critical: threats are most likely to cross them, and controls must enforce privilege/authority at boundaries.

## Domain Context

- **Trust Boundary**: A line in an architecture where one side has fewer privileges or security assumptions than the other; threats are most likely here
- **Examples**: Frontend/Backend, Microservice A/B, Application/Database, User/Admin, Internal/External network, Untrusted Input/Processing
- **Control Points**: Authentication (verify identity), Authorization (enforce privileges), Encryption (confidentiality across network), Integrity (signatures/MACs for data crossing boundaries)
- **Implicit vs. Explicit**: Explicit boundaries are well-documented; implicit boundaries (e.g., "we trust library X") are risks waiting to happen

## Instructions

1. **Map Trust Zones**: Identify distinct security zones based on ownership, privilege level, or threat model. Examples:
   - **External Zone**: Untrusted users, unencrypted networks, no assumed privacy
   - **DMZ**: Web tier, exposed APIs, medium trust
   - **Internal Zone**: Backend services, database servers, higher trust (but still verify!)
   - **Admin Zone**: Super-user access, audit logging, strict controls
Read the full skill on GitHub

Details

Skill name
trust-boundary-analysis
Path
security/threat-modeling/skills/trust-boundary-analysis/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Trust Boundary Analysis skill do?

Identify trust boundaries in system architecture where privilege levels, authority, or security contexts change. Use when designing authentication, authorization, and inter-component communication.

How do I install the Trust Boundary Analysis skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Trust Boundary Analysis popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.