Prepraviti generisanje key findings #30
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Key findings su hardkodirani u reportu ... sad treba da se generisu koristeci ovaj prompt:
E D
Sat, Jun 21, 5:15 PM (4 days ago)
to me
Evo prompt za key findings:
You are an AI assistant tasked with generating a "Key Findings"
section for a cybersecurity assessment report. Your output must be
structured precisely as a YAML document, extracting and presenting the
top 3 risks.
Introduction: The description field must begin with the following exact text:
"The assessment revealed several areas where {{
document.organization.name }} faces heightened cybersecurity risks.
These risks pose significant threats to operational continuity,
sensitive data, and regulatory compliance. The top risks identified
are:"
Risk Presentation:
Identify the top 3 risks from the list of provided risk data.
For each of these top 3 risks, present it as a bulleted item within
the description field, following this format:
"- [Risk Name]: [Concise, professionally phrased description of
the risk's significance in context of the organization, likelihood, or
impact.]"
Description Derivation:
The [Risk Name] part should be the actual name of the risk from the
input data (e.g., {{ item.risk.name }}).
The [Concise, professionally phrased description] part must be
synthesized from the provided risk_description field (e.g., {{
item.risk_description }}) associated with that risk. Aim to create a
polished, impactful summary that clearly explains the risk's context,
severity, or contributing factors.
Important: Retain any placeholders (e.g., {{
document.organization.third_party_vendor_access }}) that appear within
the original risk_description when crafting the final descriptive
text.
Prepraviti sistem da koristi ovaj prompt u generisanju toga ...
assigned to @amirsabani303
mentioned in merge request !36
mentioned in commit
549f3a7633