Prompt to Analyze Incident
Prompt to Analyze Incident is a verified PROMPT blueprint on Promptally in Personas, Teachers & Roleplay optimized for leading AI models. High-performance Prompt to Analyze Incident prompt blueprint. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Technical Specifications
| Specification | Value |
|---|---|
| Artifact type | PROMPT (Personas, Teachers & Roleplay) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 454 |
| Source file | prompt-prompt-to-analyze-incident.md |
| Access tier | Free public (MIT) |
Pre-Filled Template
Cybersecurity Hack Article Analysis: Efficient Data Extraction
Objective: To swiftly and effectively gather essential information from articles about cybersecurity breaches, prioritizing conciseness and order.
Instructions:
For each article, extract the specified information below, presenting it in an organized and succinct format. Ensure to directly utilize the article's content without making inferential conclusions.
- Attack Date: YYYY-MM-DD
- Summary: A concise overview in one sentence.
- Key Details:
- Attack Type: Main method used (e.g., "Ransomware").
- Vulnerable Component: The exploited element (e.g., "Email system").
- Attacker Information:
- Name/Organization: When available (e.g., "APT28").
- Country of Origin: If identified (e.g., "China").
- Target Information:
- Name: The targeted entity.
- Country: Location of impact (e.g., "USA").
- Size: Entity size (e.g., "Large enterprise").
- Industry: Affected sector (e.g., "Healthcare").
- Incident Details:
- CVE's: Identified CVEs (e.g., CVE-XXX, CVE-XXX).
- Accounts Compromised: Quantity (e.g., "5000").
- Business Impact: Brief description (e.g., "Operational disruption").
- Impact Explanation: In one sentence.
- Root Cause: Principal reason (e.g., "Unpatched software").
- Analysis & Recommendations:
- MITRE ATT&CK Analysis: Applicable tactics/techniques (e.g., "T1566, T1486").
- Atomic Red Team Atomics: Recommended tests (e.g., "T1566.001").
- Remediation:
- Recommendation: Summary of action (e.g., "Implement MFA").
- Action Plan: Stepwise approach (e.g., "1. Update software, 2. Train staff").
- Lessons Learned: Brief insights gained that could prevent future incidents.
# INPUT
INPUT:How to use this prompt
- Review the pre-filled example and source files above.
- Copy the template or download
prompt-prompt-to-analyze-incident.md, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use Prompt to Analyze Incident?
Open the prompt on Promptally, review the pre-filled example, then copy the template or download prompt-prompt-to-analyze-incident.md and paste it into your model, IDE or workflow tool. Prompt to Analyze Incident is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is Prompt to Analyze Incident free?
Yes. Prompt to Analyze Incident is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does Prompt to Analyze Incident need?
Prompt to Analyze Incident is a static blueprint with no dynamic variables. Copy it and use it as-is.