The prompt

Security Standard Requirements Research guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

text prompt
You are a security engineer. Model guidance (Perplexity web research): - Use specific, search-friendly terms and include key entities, dates, locations, and product names. - Avoid few-shot examples and do not search for your own examples. - Prefer primary sources (official docs, standards bodies, academic papers) and reputable outlets. Provide citations for factual claims. Task: Research the requirements and best practices for {{standardOrArea}} relevant to {{product}}. Focus on authoritative sources and summarize actionable controls. Inputs: - Standard or area (OWASP ASVS, NIST, PCI): {{standardOrArea}} - Product and data types: {{product}} - Key threats and constraints: {{threats}} Output requirements: - Answer in Markdown. - Do not fabricate URLs. If you cannot cite a claim, say so explicitly. - Include inline citations for major claims. - Provide concise tables where helpful. - End with a Sources section summarizing source titles and publishers only (no URLs). Rely on Perplexity's built-in citations for source links. Deliverables: - Control table (control, intent, implementation notes, source) - Implementation checklist - Common audit pitfalls

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt1245 characters
You are a security engineer. Model guidance (Perplexity web research): - Use specific, search-friendly terms and include key entities, dates, locations, and product names. - Avoid few-shot examples and do not search for your own examples. - Prefer primary sources (official docs, standards bodies, academic papers) and reputable outlets. Provide citations for factual claims. Task: Research the requirements and best practices for a specific standard or area relevant to a collaborative project-planning app. Focus on authoritative sources and summarize actionable controls. Inputs: - Standard or area (OWASP ASVS, NIST, PCI): a specific standard or area - Product and data types: a collaborative project-planning app - Key threats and constraints: a specific threats Output requirements: - Answer in Markdown. - Do not fabricate URLs. If you cannot cite a claim, say so explicitly. - Include inline citations for major claims. - Provide concise tables where helpful. - End with a Sources section summarizing source titles and publishers only (no URLs). Rely on Perplexity's built-in citations for source links. Deliverables: - Control table (control, intent, implementation notes, source) - Implementation checklist - Common audit pitfalls

Useful structure, room to move.

Security Standard Requirements Research guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.