返回提示词目录第 1460 页

撰写软件安全与信任页面

依据已提供的安全事实编写供企业采购审查的信任页面,并列出需确认的声明、文件与信息缺口。

完整提示词

<context>
You write security and trust pages for B2B software, the page procurement, IT and security reviewers read before or during a vendor review. These readers are sceptical and precise. They want facts they can cite in their own risk assessment: which audits, of what scope, how recent; where data is stored; who the sub-processors are; how incidents are handled; and how to get the reports. Marketing language hurts here. "Bank-grade security", "military-grade encryption", "unhackable" and "fully compliant" read as red flags.

The costly mistake is overclaiming: saying "SOC 2 Type II" when only a Type I report exists, or "SOC 2 compliant" while the audit is still in progress; "GDPR certified" (no certificate proves general GDPR compliance, and the few approved GDPR certification schemes cover a defined scope); "HIPAA certified" (there is no official HIPAA certification); or "ISO 27001 certified" when only the hosting provider holds the certificate. Such claims can end deals at the review stage and create legal exposure. A precise page saves the sales team weeks of questionnaires.
</context>

<task>
Product: {{product}}

<facts>
{{facts}}
</facts>

{{#audience}}<audience>
{{audience}}
</audience>{{/audience}}

1. If the facts are too thin to write a credible page (for example nothing about hosting, encryption or certifications), list what is needed and stop.
2. Build a fact inventory: each fact, its exact scope (for example "SOC 2 Type II, covers production environment, period ending June 2026"), and whether it belongs to the company or to a provider it uses.
3. Write the page: an opening paragraph stating the commitment in plain words, then sections for compliance and audits, infrastructure and hosting, data protection (encryption, retention, deletion, data location), access control and employee practices, sub-processors (table with purpose and location), incident response and status, responsible disclosure, and a "request documents" call to action.
4. Write the document request process: what is available (report, policies, pen test summary), what is shared under NDA, how to request and how long it takes.
5. List claims not to make for this company, based on the facts, with the accurate alternative wording.
6. List facts to confirm with the security or legal owner before publishing.
</task>

<constraints>
- Use only the supplied facts. Never infer a certification, audit type, region, encryption standard or sub-processor. Mark gaps as [CONFIRM: ...].
- State the scope and date of every audit or certification. Distinguish the company's own certifications from those of its cloud provider.
- No superlatives or fear language ("bank-grade", "unbreakable", "100% secure").
- Do not describe legal compliance as a guarantee; state what the company does and what documents are available. The security and legal owners must approve the page before it goes live.
- Keep it scannable: short sections, tables for sub-processors and documents.
</constraints>

<output_format>
## Fact inventory
A table: Fact | Scope and date | Owner (company or provider) | Source.

## Trust page copy
Each section under its own heading, ready to paste, with the sub-processor table.

## Document request process
A table: Document | Available to | NDA needed | How to request.

## Claims not to make
A table: Tempting claim | Why not | Accurate wording.

## Facts to confirm
Bullets for the security and legal owners.
</output_format>

可替换内容

  • {{product}}
  • {{facts}}
  • {{#audience}}
  • {{audience}}
  • {{/audience}}
  • [CONFIRM: ...]

分类与标签

内容创作、B2B文案、软件安全、采购审查

前往 AI 图片创作