返回提示词目录第 1434 页

撰写安全策略例外申请

帮助整理安全控制例外的业务需求、风险、补偿措施、期限与责任人,形成可提交并便于审批的申请文案。

完整提示词

<context>
Security teams approve exceptions that are narrow, time-boxed and owned, and reject ones that read as "we are too busy". What reviewers look for: the exact control and scope (which systems, which accounts), the concrete risk in terms of what an attacker could do and to what data, compensating controls that actually reduce that risk (not ones that sound good), an expiry date tied to a remediation plan with milestones, and a named business owner with authority who accepts the residual risk. Requests fail when they understate data sensitivity, propose controls nobody will monitor, or ask for an open-ended exception.
</context>

<task>
Write the security exception request.

<policy>
{{policy}}
</policy>

<situation>
{{situation}}
</situation>
{{#process}}
<process>
{{process}}
</process>
{{/process}}

1. State the exact control, and the scope of the exception: systems, environments, accounts, data types. Keep it as narrow as the situation allows.
2. Explain the business need and why compliance is not possible now, with the cost or impact of complying immediately.
3. Describe the risk plainly: what could go wrong, how likely given exposure, what data or systems are at stake. Do not soften it.
4. List compensating controls, each with what risk it reduces and who monitors it. Mark weak ones as weak.
5. Propose an expiry date and a remediation plan with milestones and owners by role.
6. Name the risk acceptor by role and what they are accepting.
7. Add how the exception will be reviewed if circumstances change{{#process}}, and map everything to the organisation's form fields{{/process}}.
</task>

<constraints>
- Never invent controls the team has not agreed to, dates, or data classifications; leave placeholders and list them.
- Do not request an open-ended or permanent exception; if the situation implies one, say a policy change discussion is the right route instead.
- If the situation involves regulated data (payment cards, health, government ids), say the exception may need compliance or legal review too.
- One to two pages.
</constraints>

<output_format>
## Request
Control and scope, Business need, Risk, Compensating controls (table), Expiry and remediation plan, Risk owner, Review triggers.

## Gaps to fill
Placeholders and decisions still needed.
</output_format>

可替换内容

  • {{policy}}
  • {{situation}}
  • {{#process}}
  • {{process}}
  • {{/process}}

分类与标签

办公效率、安全合规、例外申请、风险审批、职场文档

前往 AI 图片创作