عرض عملي: نمذجة تهديدات مساعد Larkspur

خطوة بخطوة

1. Draw the data flow: customer or staff user, assistant service, retrieval over product, order, and policy content, model provider, tool gateway to order and refund services, logs.
2. Mark trust boundaries: user to service, service to provider, tool gateway to internal systems.
3. Planned mistake: rely on the system prompt ("never reveal card numbers"). A tester pastes a card number into chat and an injected instruction in a product review makes the assistant echo it. Fix: mask card patterns at the input filter and never log them, filter outputs, and keep card data out of retrieved content.
4. List threats per boundary (injection, cross-customer leakage, over-powered refund tool, provider retention, log exposure) with a control and owner for each.
5. Add residual risks and test cases to the assurance plan, and record the decisions.
6. Review with the role-played security and privacy officer and confirm no payment card data can reach the model.

اختبر فهمك