• AI-Agent
  • Ready to Run

Draft Security Incident Reports

Draft reports from confirmed incidents for analyst review

Use this Agent instantly or customize it - no programming needed

Draft a security incident report for analyst review
Reads
  • Confirmed status change
    Confirmed status change

    Your ticket's move to Confirmed starts the draft and identifies the incident.

  • Incident details
    Incident details

    Your ticket supplies the alert, investigation notes, and asset IDs for this draft.

  • Affected asset details
    Affected asset details

    Your inventory supplies each named asset's service, owner, and recorded criticality.

  • Report guidance
    Report guidance

    Your report outline guides uncertain findings and separates completed actions from proposals.

Incident ticket system
Incident ticket system

Your incident ticket system supplies confirmed tickets and keeps the draft link for analyst review.

Incident ticket system
Asset inventory tool
Asset inventory tool

Your asset inventory tool shows the service and owner of each asset named on the ticket.

Is the ticket no longer Confirmed?YesNo
Stop drafting and leave reporting with the incident owner.
Does the ticket already link a first draft?YesNo
Use the existing draft link for analyst review.
Does creating the report document fail?YesNo
Comment on the ticket with the document problem.
Writes
  • Draft failure comment
    Draft failure comment

    Your ticket names the document problem so your analyst can follow up.

Create the provisional report and link it on the ticket.
Writes
  • Security incident report draft
    Security incident report draft

    Your analyst gets an editable report with a provisional cause, supported impact estimate, and open questions.

  • Report review link
Document editor
Document editor

Your document editor holds the editable report that your analyst reviews.

Document editor

This Agent starts when your security incident ticket enters Confirmed. It checks the investigation notes and named assets, then drafts a provisional report. Your analyst gets an editable document linked on the ticket.

Modify Agent

Customize this Agent to fit your needs using natural language.

Start Agent for Free

Enter your email address and we will send you a secure link to continue.

Google Drive
Used as:
Show all Agents working with Google Drive
monday.com
Used as:
Show all Agents working with monday.com
Google Contacts
Used as:
Show all Agents working with Google Contacts
Podio
Used as:
Show all Agents working with Podio
Superhuman Docs
Used as:
Show all Agents working with Superhuman Docs

Made for your industry

Draft Security Incident Reports is made for businesses in these industries.

Made for your role

Draft Security Incident Reports is made for people in these roles.

Made for your department

Draft Security Incident Reports is made for people in these departments.

How Draft Security Incident Reports works

4 steps, in order, on every run.

  1. Check the incident ticketRead the ticket's alert and notes. Stop if it is no longer Confirmed; reuse any existing first-draft link.
  2. Check affected assetsMatch ticket asset IDs to inventory entries for service, owner, and criticality. Flag unmatched IDs as limits on the impact estimate.
  3. Draft the reportCreate an editable report with a provisional cause and supported impact estimate. Separate completed containment from proposed actions and list open questions.
  4. Link the draft for reviewComment on the ticket with the draft link and unresolved findings. Ask the analyst to verify any missing facts.

How to Get Started

Connect your tools

Connect the tools you already use, such as Google Drive, monday.com or Google Contacts.

5 tools
Set your rules
  • Choose the security incident project, issue type, and Confirmed status that starts a report.
  • Map the ticket fields for the alert, severity, incident times, and asset IDs, and use its description and comments for investigation notes.
  • Choose the asset inventory table and map its asset ID, service, owner, and business criticality fields.
  • Provide the report outline and response guidance for wording provisional causes, impact estimates, containment, and follow-up.
  • Connect a document account accessible to the reviewing analyst and grant the Agent permission to read and comment on incident tickets.
Launch the Agent

Use safe mode to approve every result before it goes out, or let the Agent run automatically.

FAQs

Frequently asked questions about the Draft Security Incident Reports:

What triggers the report draft?

You choose the security incident project, issue type, and Confirmed status. A ticket entering that status starts a draft.

How does it handle missing information?

The report marks missing times or asset details as unknown and labels the cause provisional. Your analyst gets the gaps in the ticket comment.

Does it create another report for the same ticket?

If the ticket already links a first draft, the Agent uses that link and does not create another.

What happens if it cannot create the document?

The Agent comments on the ticket with the problem so your analyst can follow up.

What happens when the Agent is unsure?

It stops and asks you. The Agent does not guess when it reaches a decision you have not approved.

Can I review its work?

Yes. Every run creates a plain-language log that you can review and export. Logs are kept for twelve months.

What happens if I cancel?

The Agent stops at the end of the billing month and its tool connections are removed. Your run logs remain available for twelve months.

Related Agents

Agents related to Draft Security Incident Reports

More ready-to-run Agents for connected work.