Policy gap check against a framework checklist
Compare your written security policies with a control checklist, such as a SOC 2-style list, and get a draft gap list for your security lead.
The use case
Small companies preparing for customer reviews or a first audit usually have some policies written, but nobody knows which controls they actually cover. Reading every policy against a long checklist is tedious and easy to rush. This agent reads your policy documents and a control checklist you supply, then drafts a mapping showing which controls appear addressed, partly addressed, or not mentioned, with the policy passage it relied on. It also drafts plain-language notes on what each gap might need. The security lead reviews every mapping, corrects misreads, and decides which gaps to prioritize. The output is a working document, not a compliance statement.
Example workflow
- The security lead uploads current policy documents and a control checklist into a restricted project folder.
- The agent splits the checklist into individual controls and reads each policy for passages that relate to them.
- For each control it drafts a status of addressed, partial, or not found, quoting the supporting policy passage.
- It adds a short note on what a partial or missing control might need, such as a procedure, owner, or evidence source.
- The security lead reviews each mapping, corrects errors, and assigns owners and target dates to gaps worth closing.
- The reviewed gap list is saved with the policy versions used, so the next check can compare progress.
Tools
- Claude
- Google Drive
- Google Sheets
- Notion
- Jira or Asana
- Slack
Risks and guardrails
- A policy that mentions a control is not proof the control operates — guardrail: the output says policy coverage only and the lead tracks operating evidence separately.
- The agent may stretch vague wording into full coverage — guardrail: every addressed status must quote a passage, and the lead downgrades weak matches.
- A checklist copied from an unofficial source could be incomplete — guardrail: the lead confirms the checklist source and version before the run.
- The gap list might be shared as if it were an attestation — guardrail: the document is labeled an internal draft and only a responsible person makes any external statements.
Related recipe
Security Questionnaire First-Draft Agent with Cited Sources: An agent drafts security questionnaire answers from your own trust documents and approved answer library, cites every source, and marks gaps NEEDS OWNER for a responsible person to sign.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Claude (official page): claude.ai (checked 2026-11-09)
- Google Drive (official page): developers.google.com/workspace/drive (checked 2026-11-19)
- Notion MCP server (official page): developers.notion.com/guides/mcp/overview (checked 2026-11-09)
- Asana MCP server (official page): developers.asana.com/docs/using-asanas-mcp-server (checked 2026-11-09)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)