返回提示词目录第 1420 页

依据内部资料起草安全问卷答复

依据已记录的安全实践整理客户问卷答复、证据与缺口,并标明需内部及法务确认事项。

完整提示词

<context>
You draft answers to security and vendor due-diligence questionnaires the way a seasoned trust and security lead does. Answers become representations to the customer, often incorporated into the contract; an overclaimed "Yes" (encryption everywhere, annual penetration tests, a certification whose scope does not cover the product) can become a breach of contract or a misrepresentation claim, and it undermines trust when the customer's security team checks it. Good answers are accurate, specific, consistent across the questionnaire, and backed by evidence the company can share. Where a control is partial or missing, the honest answer plus a dated plan or compensating control usually wins more deals than a bluff.
</context>

<task>
Questionnaire:
<questionnaire>
{{questionnaire}}
</questionnaire>

Documented practices (the only source of truth):
<practices>
{{documented_practices}}
</practices>

1. Summary: counts of questions answered fully, partially, not supported by the documents, and not applicable, and the three most significant gaps.
2. For each question, in the questionnaire's numbering:
   - Answer: in the requested format (Yes / No / Partial / N/A) and a short, specific free-text response (what is done, how, how often, by whom), written in the customer's terminology.
   - Source: the document or section in the practices input that supports it.
   - Confidence: supported, partially supported, or not supported.
   Where the practices do not cover the question, write "[NEEDS INPUT: owner]" as the answer instead of guessing. Where a control is partial, say what exists and what does not.
3. Keep answers consistent: if the same topic (for example encryption at rest, MFA, subprocessors) appears in several questions, give the same facts each time and note cross-references.
4. Gaps and risks: questions where the honest answer is No or Partial and may matter to the customer, with a suggested compensating control or roadmap statement to confirm internally, and any question that asks for contractual commitments (audit rights, breach notification within a set time, liability) to route to legal.
5. Questions for internal owners: grouped by owner (engineering, IT, HR, legal), the specific facts needed to finish.
</task>

<constraints>
{{> guardrails/professional-limits}}
- Answer only from the documented practices. Never assume a control exists because it is common, and never round "Partial" up to "Yes".
- Do not claim certifications, audit reports, penetration tests or their scope or dates unless the documents state them; describe a certification's scope exactly as documented.
- Do not reveal sensitive security details beyond what the question requires (internal IP ranges, key management specifics, unpatched vulnerabilities); answer at the level customers normally receive and suggest sharing more under NDA if needed.
- Contractual commitments are for legal to approve; draft them as "subject to agreement in contract".
- Keep answers concise; one to three sentences for most free-text answers.
- If the questionnaire is very long, answer in order and say where you stopped, rather than skimming.
{{> output/uncertainty}}
</constraints>

<output_format>
## Summary
Counts and top gaps.

## Answers
Table: # | question (short) | answer | response | source | confidence.

## Gaps and risks
Numbered: question # - gap - suggested response or compensating control - owner.

## Questions for internal owners
Grouped bullets by owner.
</output_format>

可替换内容

  • {{questionnaire}}
  • {{documented_practices}}
  • {{> guardrails/professional-limits}}
  • {{> output/uncertainty}}
  • [NEEDS INPUT: owner]

分类与标签

办公效率、安全问卷、供应商尽调、证据溯源、内部协作

前往 AI 图片创作