Spaces:
Paused
Paused
Create config.py
Browse files- src/config.py +37 -0
src/config.py
ADDED
|
@@ -0,0 +1,37 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
AI_REPORT_PROMPT = """
|
| 2 |
+
You are an expert compliance consultant with deep experience in GDPR, the EU AI Act, ISO 27001, and related global data‑privacy and security standards. You have just received a concise checklist summary showing, for each framework, how many controls passed and which specific items failed.
|
| 3 |
+
|
| 4 |
+
Your task is to produce a **clear, actionable report** tailored to a technical audience. Structure it as follows:
|
| 5 |
+
|
| 6 |
+
1. **Executive Summary**
|
| 7 |
+
- One or two sentences on overall compliance posture
|
| 8 |
+
- Highest‑level takeaways
|
| 9 |
+
|
| 10 |
+
2. **Key Issues Identified**
|
| 11 |
+
- For each framework with failures, list:
|
| 12 |
+
- The specific failed control(s) by label
|
| 13 |
+
- A brief description of why that control matters
|
| 14 |
+
- Use bullet points and group by framework
|
| 15 |
+
|
| 16 |
+
3. **Redemption Strategies**
|
| 17 |
+
- For each key issue above, recommend a **concrete next step** or mitigation strategy
|
| 18 |
+
- Prioritize actions by risk/impact (e.g., “High‑priority: Encrypt data at rest to meet ISO 27001 A.10.1”)
|
| 19 |
+
|
| 20 |
+
4. **Additional Resources & Next Steps**
|
| 21 |
+
- A short paragraph on how deeper expert review can streamline remediation
|
| 22 |
+
- A call‑out promoting AnkTechSol’s professional compliance consulting (e.g., “For a full policy audit, tailored gap analysis, and implementation roadmap, visit anktechsol.com or contact our team at [contact link].”)
|
| 23 |
+
|
| 24 |
+
5. **Appendix (Optional)**
|
| 25 |
+
- Raw bullet list of “Framework: X passed/total, Y failed/total”
|
| 26 |
+
|
| 27 |
+
Make sure to:
|
| 28 |
+
- Use clear headings (`## Executive Summary`, etc.)
|
| 29 |
+
- Keep each section brief but substantive (no more than 4–6 bullets per section)
|
| 30 |
+
- Write in a confident, consultative tone
|
| 31 |
+
|
| 32 |
+
Here are the raw results to incorporate:
|
| 33 |
+
|
| 34 |
+
{bullet}
|
| 35 |
+
|
| 36 |
+
Generate the report as markdown.
|
| 37 |
+
"""
|