If you need help getting started using the System Prompt feature, or to quickly try out the feature, use a preset scenario. The preset scenarios provide a system prompt.
- Be Specific in Answers: Provide detailed responses to AI questions for better results.
- Start Simple: Begin with three questions, increase if needed.
- Iterate: Run multiple evaluations as requirements evolve.
- Review Carefully: All suggestions do not have to be accepted.
- Use Presets to Learn: Try preset scenarios to understand common vulnerabilities.
In the Console, select Security Testing > System Prompt.
Click Need help getting started? to expand the section.
Click one of the preset scenarios. The Create System Prompt Evaluation slide-out displays.
- Optionally, you can change the evaluation name.
- Do not change the system prompt.
For Analysis Configuration, select the number of questions you will answer for this evaluation.
- The purpose of the evaluation questions is to try and tailor the new system prompt to the organization's concerns and context.
- The minimum is one and the maximum is five.
- Selecting fewer questions means less guidance to customization on your system prompt. Selecting more questions guides the simulation on more customization toward security best practices.
Click Next. The analysis is started. Questions are generated; this may take a moment.
- You can leave the slide-out and return later to answer the questions.
- Note: You must return to the evaluation within 60 minutes, otherwise the evaluation process will timeout and you must start over.
Answer the questions based on your organization's guidelines and goals.
Click Submit. The analysis may take a moment.
- An estimated processing time displays.
- More questions/answers in the evaluation will take more time to process.
- The elapsed time includes time spent away from the evaluation.
When the evaluation completes, click the green arrow to view the results. See System Prompt Evaluation Summary for more information.
| Preset Scenario | Description |
|---|---|
| Data Leakage Risk | Container hardcoded credentials vulnerable to extraction. |
| Prompt Injection Vulnerable | Missing input sanitization and role enforcement. |
| Agentic AI with Tools | No tool usage constraints or safety boundaries defined. |