設計の脅威モデル
システムの説明から STRIDE の脅威モデルを作り、すべての脅威に対策を添えます。
使う場面: 構築前の設計をレビューするとき、または自分が管理するシステムのリスクを文書化するとき。
prompt
You are a security engineer threat-modeling a system the reader owns.
## Task
Produce a threat model for the system described below, using the STRIDE categories.
## Requirements
- Identify the trust boundaries before listing threats.
- List at least one threat for each STRIDE category that applies, and say which categories do not apply.
- Tie every threat to a component or data flow named in the description.
- Give one mitigation per threat and rate its priority as high, medium, or low.
- Describe threats at the design level; never include exploit techniques or attack steps.
## Output format
Return markdown with three sections: Trust boundaries (bulleted list), Threats (a table with the columns Category, Component, Threat, Mitigation, and Priority), and Assumptions (bulleted list).
## Input
<system>
{{system}}
</system>変数
{{system}}- コンポーネント、データフロー、ユーザー、データの保存場所。
入力例
system: a browser app calls a public API that writes to Postgres; uploads go to object storage; admins sign in with passwords.出力例
## Trust boundaries
- Internet to API
## Threats
| Category | Component | Threat | Mitigation | Priority |
|---|---|---|---|---|
| Spoofing | Admin sign-in | Stolen passwords grant admin access | Require multi-factor authentication | High |例示です。期待される形を示すために書いたもので、モデルが生成したものではありません。