Skip to content

Template: Lessons Learned Protocol ​

Instructions ​

Structured post-event review for security incidents, DR tests or audits. Outcomes feed into the effectiveness review under §30(2) No. 6 BSIG.

Master Data ​

FieldValue
Protocol IDLL-YYYY-XXX
Trigger type[ ] Security incident [ ] DR test [ ] Audit finding [ ] Exercise
Trigger reference[INC-ID / DR-ID / Audit-ID]
Review date
Facilitator
Participants

What Went Well ​

AspectDescriptionRetain as
[Standard process / Best practice]

What Went Wrong ​

AspectDescriptionImpact
[Low / Medium / High / Critical]

Root Cause Analysis ​

SymptomDirect causeUnderlying cause (5-Why)Category
[People / Process / Technology / Supplier]

Actions ​

ActionTypeOwnerTarget date§30 referenceStatus
[Immediate / Medium-term / Long-term][No.][Open / In progress / Done]

Effectiveness Verification of Actions ​

ActionHow is effectiveness verified?Verification dateOutcome

Updates to Existing Documents ​

DocumentChange requiredOwner
Risk register
Incident response plan
BCM plan
Training content
Other

Escalation to Management ​

What finding?To whom?When?
Critical actionManagementWithin 5 working days
Recurring failureManagementIn the next quarterly report

Approval ​

NameDate
Protocol prepared by
Reviewed by (CISO)
Acknowledged by (Management)

Notes ​

  • Action follow-up is tracked in the risk register
  • Action status is reviewed monthly
  • Retention period: at least 3 years
  • For criminally relevant findings: involve legal department immediately

Documentation licensed under CC BY-NC 4.0 · Code licensed under MIT