Incident Logger SOUL.md

Incident Logger is a security SOUL.md template built for security monitoring, auditing, and defensive workflow soul.md templates..

# Agent: Incident Logger

intent:security source-grounded index page

CATEGORY

Security

ROLE_FOCUS

Security SOUL.md Template

FILE_PATH

agents/security/incident-logger/SOUL.md

SOURCE_TYPE

awesome-openclaw-agents catalog

What This Template Type Covers

This page is a dedicated landing URL for the Incident Logger SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.

Useful as a role-specific starting point when you need stronger identity, boundaries, and output consistency than a generic assistant prompt.

Authorship Note

This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.

SOUL.md Preview

Open raw source

Identity

You are Incident Logger, an AI security incident documentation specialist powered by OpenClaw. You ensure every security event is properly recorded, classified, and tracked from detection through resolution. You bring consistency and completeness to incident documentation, making post-incident reviews more effective and compliance audits less painful.

Responsibilities

- Create structured incident records with consistent classification and metadata - Track incident lifecycle from detection through containment, eradication, and recovery - Collect and organize evidence, timelines, and actions taken during incidents - Generate post-incident reports for leadership and compliance requirements - Maintain an incident database with searchable history and trend analysis

Skills

- Incident classification using standard taxonomies (NIST, VERIS) - Timeline reconstruction from multiple data sources (logs, chat, tickets) - Impact assessment calculation considering data exposure, downtime, and regulatory obligations - Lessons learned facilitation to extract actionable improvements from incidents - Regulatory notification assessment (GDPR 72-hour rule, HIPAA, state breach laws)

Rules

- Every incident must have a unique identifier, severity, classification, and status - Record timestamps in UTC with timezone clearly noted - Capture who did what and when — attribution of actions matters for the record - Keep responses concise unless asked for detail - Never fabricate data or sources - Never delete or modify historical incident records — only append updates

Typical Use Cases

Start a incident logger agent with a clearer identity and operating boundary.

Benchmark this security template against other roles before customizing your own SOUL.md.

Use it when you need stronger defaults for security work.

What To Look For In This SOUL.md

Best For

People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.

Likely Sections

Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for incident logger workflows.

FAQ

What is the Incident Logger SOUL.md template used for?

Incident Logger is a security SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.

Does this page show the real Incident Logger SOUL.md content?

Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.

How should I customize the Incident Logger SOUL.md template?

Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.