Skip to main content

Operational & Security Incident Report Form

Report ID: INC-[YYYY]-[XXX]
Date of Report: [YYYY-MM-DD]
Incident Type: [Security Breach / Confidentiality Issue / Physical Safety / System Outage / Fraud]
Severity Level: P0 (Critical) | P1 (High) | P2 (Medium) | P3 (Low)

Interactive Printable & Downloadable Instrument​

The standardized operational instrument is embedded below. You can complete entries or check off items directly in the viewer, print to paper or PDF via the print trigger, or download the self-contained HTML asset for field distribution.

📄 Commercial Incident & Near-Miss Report Form (FORM-OPS-001)

🖨️ Print / Save PDF

📥 Download HTML

1. Incident Overview​

  • Date & Time of Occurrence: [YYYY-MM-DD @ HH:MM EST]
  • Date & Time Discovered: [YYYY-MM-DD @ HH:MM EST]
  • Reported By: [Name / Role]
  • Entities / Systems Impacted: [e.g., Alas 9 cloud, Alas Artistry client data, facilities]

2. Description of Incident​

Provide an objective, factual timeline of what happened, how it was discovered, and what systems or records were affected.

3. Data & Asset Impact Assessment​

  • Was Confidential Information or Trade Secrets Exposed? [ ] Yes [ ] No [ ] Under Investigation
  • Was Personal Identifiable Information (PII) Involved? [ ] Yes [ ] No
  • Estimated Financial / Operational Loss: $ [Amount / Scope]

4. Immediate Containment Actions Taken​

  1. [Step taken immediately to isolate system or prevent further harm]
  2. [Step taken to notify leadership / IT Security]

5. Corrective Actions & Resolution​

  • Root Cause Analysis: [Explanation of underlying defect or vulnerability]
  • Corrective Action Required: [Link to Corrective Action Record (CAR)]
  • Incident Closed Date: [YYYY-MM-DD]
  • Signed Off By: [Dante Lackland / Cody Rice-Velasquez / Ryan Schwegman]