Hire an AI security architect

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A trust boundary table: where control passes between a user, a service or a third party, and what protects that crossing today.
• A ranked STRIDE threat table: each risk that applies, the component it hits, an attack scenario, and the proposed fix.
• An attack surface list, split into external, internal, data and infrastructure entry points.
• A control list in priority order, each sized small, medium or large.
• The assumptions it made and what you should confirm before you trust the result.

How it does the job well

• Build the model only from what the user gives you. Never invent a component, integration or control that wasn't named.
• Mark every control "confirmed by the user" or "assumed" and keep the two apart in the output.
• This is a design-stage review. It does not test a running system, scan code for bugs, or replace a penetration test or a compliance audit.
• Name the asset, the threat and the impact before recommending controls.
• Rank findings by real risk (likelihood and impact), with evidence for each.
• Prefer fixes that remove a problem over warnings that rely on people.
• Cite the exact law, standard or clause for compliance and legal points, and recommend qualified review.

Mistakes it avoids

• Reviewing a whole company or product line at once. Ask the user to name one system.
• Copying the profile's sample threat model as if it were the user's own data.
• Scoring a threat that doesn't apply to the described system just to fill out the table.
• Long lists of generic issues with no evidence they apply.
• Testing or scanning systems without permission.
• Presenting a legal opinion as final.

What a good result looks like

An example, not your task: You're designing a new service, API or feature and want the security gaps found before you build.

• Trust boundaries. Every place control passes between a user, a service or a third party, and what protects it today.
• STRIDE threats. Each risk that applies, the component it hits, an attack scenario and the proposed fix, ranked by severity.
• Attack surface. Every external, internal, data and infrastructure entry point found.
• Control proposals. A priority-ordered fix list, each sized small, medium or large.
• Assumptions and checks. What the agent assumed and which facts you still need to confirm.

How the work is checked

• Each finding has a location, evidence, severity and a specific fix.
• Likely false positives are checked and removed.
• Items that need a lawyer or auditor are clearly marked.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Map the system. It confirms the architecture, tech stack, data types and every way in, and asks once for anything missing.
• Find the trust boundaries. It marks each place where control passes between a user, a service or a third party, and what protects that crossing today.
• Run the STRIDE pass. For each boundary it checks all six threat types and keeps only the ones that fit, each with a real attack scenario.
• Rank by risk. It scores each threat by how easy it is to pull off and what it would cost, then orders the list by that score.
• Propose one control per threat. Each threat gets a concrete fix, such as a rate limit or a signature check, sized small, medium or large.
• Separate fact from assumption. It lists what you confirmed, what it assumed, and which checks (a scan, a pen test) you still need to run.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id security-architect only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/security-architect/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your system's architecture (monolith, microservices or serverless), and its languages, frameworks, databases and cloud provider.
• What data it handles and how sensitive it is, such as passwords, payment details or health records.
• Every way in: public APIs, admin panels, mobile apps, third-party integrations, internal service calls.
• Any controls you already have, such as login checks, encryption or a firewall (optional).
• An architecture diagram or design doc (optional).

Helpful context (optional)

• Any past security findings or audit reports.
• Your incident history, if you've had one.
• The compliance framework you're working toward, if any.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It can read your architecture diagram or design doc next to your description.

Functions and deliverables

• Security architect agent: Describe your system. Get trust boundaries, a ranked STRIDE threat table and the security controls to fix first, before you write a line of code.
  • A trust boundary table: where control passes between a user, a service or a third party, and what protects that crossing today.
  • A ranked STRIDE threat table: each risk that applies, the component it hits, an attack scenario, and the proposed fix.
  • An attack surface list, split into external, internal, data and infrastructure entry points.
  • A control list in priority order, each sized small, medium or large.
  • The assumptions it made and what you should confirm before you trust the result.
  Source: Michael Sitarzewski and Agency Agents contributors.
• App security threat planner: Describe your app, users and sensitive data. Get a first threat list, entry points, practical safeguards and assumptions to check.
  • A list of parts and entry points
  • The top threats, ranked, with likelihood and damage
  • One practical fix for each
  • What was assumed and what to confirm
• STRIDE system threat analyst: Run a STRIDE threat model on your code repository. Get diagrams, ranked findings and a report that shows new, fixed and open threats.
  • 0-assessment.md: a short summary of the main risks and what to fix first
  • 0.1-architecture.md: the system parts and how they connect
  • 1-threatmodel.md: the data flow diagram with trust boundaries
  • 2-stride-analysis.md: threats for each part, sorted by STRIDE type
  • 3-findings.md: ranked findings with severity, CWE and OWASP mappings and fixes
  • threat-inventory.json, and on update runs a comparison of new, fixed and open threats
  Source: GitHub Copilot community.
• Microsoft threat model file builder: Describe components, users, data paths and trust boundaries. Get a Microsoft Threat Modeling Tool file draft with mapped threats.
  • A .tm7 file built for the Microsoft Threat Modeling Tool v7.3 or newer, from a bundled example structure (not tested by us in every version)
  • A diagram with shapes laid out so they do not overlap
  • STRIDE threats attached to each data flow
  • A check of the file against known mistakes that corrupt .tm7 files
  Source: GitHub Copilot community.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• You're designing a new service, API or feature and want the security gaps found before you build.
• You inherited a system with no written threat model and need one for a review or a customer's security questionnaire.
• You added an integration, such as a payment processor or a login provider, and want to know what trust boundary it creates.
• A customer or investor asks how your system defends itself and you have nothing written down.

Limits to check before starting

• You have an active breach or suspicious activity right now. Use the Security incident responder and call your security lead first.
• You want your code scanned for bugs like SQL injection or broken access control. Use the Application security reviewer.
• You need a SOC 2, ISO 27001, HIPAA or PCI-DSS gap check. Use the Compliance Auditor agent.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill, or paste SKILL.md then references/source-agent.md into a new chat.
• Describe your system: architecture, tech stack, data types, and every way in, including internal and third-party ones.
• List any controls you already have, and attach a diagram if you have one.
• Say "Build the threat model. Score each threat and tell me what you assumed."
• Read the trust boundary table first. If a boundary is wrong, fix that before trusting the risks listed under it.
• Hand the ranked control list to whoever owns each fix, most urgent first.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/security-architect for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.