You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create or update a policy based on strict alignment with SOC 2 standards and controls.
47
+
Task: Edit the provided TipTap JSON template to produce the final policy TipTap JSON. Apply ONLY the rules below.
36
48
37
-
Contextualise every section with company Secure-specific systems, regions, and roles.
38
-
Replace office-centric language with cloud and home-office equivalents.
39
-
Build control statements that directly mitigate the listed risks; remove irrelevant clauses.
40
-
Use mandatory language such as “must” or “shall”; specify measurable review cycles (quarterly, annually).
41
-
End with a bullet list of auditor evidence artefacts (logs, tickets, approvals, screenshots).
42
-
Limit to three-sentence executive summary and maximum 600-word main body.
43
-
Wrap any unresolved detail in <<TO REVIEW>>.
49
+
Required rules (keep this simple):
44
50
45
-
1.Remove Document Version Control section altogether(if present) and also adjust numbering accordingly
46
-
2. Make a table of contents (in tiptap format)
47
-
3. Give me executive summary on top of the document
48
-
4. Wrap any unresolved detail in <<TO REVIEW>>
49
-
5. Number 1 in Table of Contents will be Document Content Page
50
-
6. I want to document to be strictly aligned with SOC 2 standards and controls
51
+
1) Company details
52
+
- If the template contains placeholders like {{...}}, replace ANY placeholder with information you actually have (from the knowledge base, company name, company website, frameworks context).
53
+
- If a specific placeholder cannot be resolved, set it to "N/A" (do not invent values).
54
+
- Only fill placeholders where the template asks; do not add new fields beyond the placeholders.
55
+
- Placeholder legend (map values from the knowledge base Q&A where available):
56
+
- {{COMPANY}} ⇐ Company Name
57
+
- {{COMPANYINFO}} ⇐ Describe your company in a few sentences
58
+
- {{INDUSTRY}} ⇐ What Industry is your company in?
59
+
- {{EMPLOYEES}} ⇐ How many employees do you have
60
+
- {{DEVICES}} ⇐ What Devices do your team members use
61
+
- {{SOFTWARE}} ⇐ What software do you use
62
+
- {{LOCATION}} ⇐ How does your team work
63
+
- {{CRITICAL}} ⇐ Where do you host your application and data
64
+
- {{DATA}} ⇐ What type of data do you handle
65
+
- {{GEO}} ⇐ Where is your data located
66
+
- If multiple answers exist, choose the most specific/concise form. If no answer is found for a placeholder, set it to "N/A".
51
67
52
-
Policy Title: ${policy.name}
53
-
Policy: ${policy.description}
68
+
2) Structure & style
69
+
- Keep the same section order and general layout as the template (headings or bold titles as-is).
70
+
- Do NOT copy instruction cue lines (e.g., "Add a HIPAA checklist...", "State that...", "Clarify that..."). Convert such cues into real policy language, and then remove the cue line entirely. If a cue precedes bullet points, keep the bullets but delete the cue line.
54
71
72
+
3) Handlebars-style conditionals
73
+
- The template may contain conditional blocks using {{#if var}}...{{/if}} syntax (e.g., {{#if soc2}}, {{#if hipaa}}).
74
+
- Evaluate these using the selected frameworks:
75
+
- soc2 is ${hasSOC2 ? 'true' : 'false'}
76
+
- hipaa is ${hasHIPAA ? 'true' : 'false'}
77
+
- If the condition is true: keep only the inner content and remove the {{#if}}/{{/if}} markers.
78
+
- If the condition is false: remove the entire block including its content.
79
+
- For any other unknown {{#if X}} variables: assume false and remove the block.
55
80
56
-
Here is the initial template policy to edit:
81
+
Output: Return ONLY the final TipTap JSON document.
0 commit comments