Incident obligation reconciliation

What does the incident obligation reconciliation produce?

Reconcile incident reporting obligations, staged submissions and contradictory duty versions.

Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.

What do you need before you start?

• Define the authorized source population and your review rules.
• Keep the unchanged original files and record the snapshot and exclusions.
• Review missing and invalid inputs before preparing the finalized pack.

What information do you enter?

Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.

• Reference. Stable internal reference for this incident preparation version.
• Working pack version. Exact current customer document version.
• Organization. Actual organization owning this incident or exercise.
• Your jurisdiction. Exact jurisdiction and entity scope approved for this incident. No legal applicability is inferred.
• Incident ID. Exact incident or exercise identifier shared by the task rows.
• Responsible reviewer. Customer-authorized incident reviewer and decision owner.
• Review timestamp. Exact timestamp with seconds and a confirmed UTC offset.
• Approved incident scope. Included events, populations, systems, products, exclusions and uncertainty.
• Scope approval reference. Customer approval for the selected incident boundary.
• Approved preparation method. Your exact procedure or assessment method version.
• Method source reference. Actual local file containing the approved method.
• Approved method source locator. Exact location supporting the selected method.
• Method approver. Customer-authorized approver for this procedure version.
• Method approval timestamp. Exact approved instant no later than the review timestamp.
• Incident population. Selected records or a declared complete supplied population.
• Declared event count. Required for your declared complete event population.
• Declared duty count. Required for your declared complete supplied duty population.
• Incident obligation and submission reconciliation event inputs. Readable typed task rows. Exact IDs link incidents, original sources, operative rules, approvals and outputs.
• Duties. Readable typed task rows. Exact IDs link incidents, original sources, operative rules, approvals and outputs.
• Submissions. Readable typed task rows. Exact IDs link incidents, original sources, operative rules, approvals and outputs.
• Report Fields. Readable typed task rows. Exact IDs link incidents, original sources, operative rules, approvals and outputs.
• Evidence. Readable typed task rows. Exact IDs link incidents, original sources, operative rules, approvals and outputs.
• Actions. Readable typed task rows. Exact IDs link incidents, original sources, operative rules, approvals and outputs.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the incident obligation reconciliation work?

1. 1
   Select the actual sources

   Reference. Stable internal reference for this incident preparation version.

2. 2
   Freeze the review rules

   Bind each approved duty to its exact instrument or contract version, incident trigger and recipient. Flag conflicting supersessions, duplicate stage receipts, missing predecessor submissions and incomplete dispatch proof. Calculate only explicit approved clocks and preserve all competing duty records rather than choose a legal interpretation.

3. 3
   Inspect complete findings

   Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.

4. 4
   Keep recoverable work

   Exact draft strings and source bytes save locally. Strict restore checks tool identity, typed row structure, source hashes and retained history before replacing browser work. Earlier generic work and the prior checkpoint remain downloadable.

5. 5
   Prepare the finalized pack

   Prepare eight core files, including the private ICS calendar, and exact selected attachments, then download them free. Review the fictional sample below.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• Incident Response Recommendations and Considerations for Cybersecurity Risk Management. A CSF 2.0 Community ProfileSupports this named evidence-preparation structure. Actual operative criteria, policy terms, incident facts and approvals remain exact customer inputs. NIST SP 800-61 Revision 3, April 2025. Incident analysis, communication, recovery and evidence handling within CSF 2.0. Voluntary risk-management guidance does not determine notification applicability, legal deadlines, policy coverage or an organization's actual incident facts.National Institute of Standards and Technology. Reviewed 2026-10-09.

Common questions

What still needs review?

This working pack organizes your supplied incident facts, original evidence, approved rule versions and recorded decisions. It does not decide legal applicability, notification duties, statutory deadlines, insurance coverage, AI seriousness, product exploitation, authenticity or sanctions clearance. No report, message, authority filing or payment is sent. Original files remain unchanged and browser-local. Original files are not saved to the cloud.

At most 500 rows and 200000 characters per table, 20 files, 10 MB each and 25 MB total. Complete input metadata is bounded to 900 KB. Exact JSON source comparison supports source files of at most 1 MB.

Calendar calculations require explicit approved units, counting rules, dates, weekday exclusions and confirmed offsets. No daylight-saving rule or operative legal clock is inferred.

Formal previews are bounded. Complete accepted task rows, decision drafts, original timestamps, source lineage and results remain in Excel and JSON.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all cybersecurity tools.

• Incident contact treeMaintain contacts, alternates and dependencies. Try a free example, then review your inputs and the result. No account or payment required.
• Exercise observation recorderCapture actual actions and decisions. Try the free example, then enter your own inputs and review the result before exporting.
• Incident timeline normalizerReconcile timestamps, time zones and conflicting sources. Try a free example. Review your inputs and result. No account or payment required.
• Incident evidence manifestIndex collected material and its source. Try the free example, then enter your own inputs and review the result before exporting.
• Incident action trackerRecord containment, recovery and follow-up work. Try a free example, then review your inputs and the result. No account or payment required.