# Event website security update and rollback record

Event / site: __________  Public hosts: __________  Change date and window: __________

| Component and version now | Target version | Vendor advisory / reason | Affected host or path | Exposure | Technical owner | Decision owner |
|---|---|---|---|---|---|---|
| | | | | | | |

## Before release
- [ ] The vendor advisory applies to this product and installed version.
- [ ] Any known exploitation and public exposure were considered in priority.
- [ ] Code, configuration, database, media and integration dependencies were inventoried.
- [ ] A recent backup is retrievable; restoration owner and location are recorded.
- [ ] Database migrations and other non-reversible steps are identified.
- [ ] Representative non-production review or documented alternative is complete.
- [ ] Public page, registration, confirmation and ticket handoff have a safe verification method.
- [ ] Stop/rollback symptom, decision maker and communication owner are named.

Backup evidence/location: __________  Restore owner: __________
Expected attendee impact: __________  Support contact: __________

## Release and decision
| Time | Component/version or action | Operator | Observation / attendee-path check | Decision and owner |
|---|---|---|---|---|
| | | | | |

Rollback trigger: __________  Code/config recovery steps and owner: __________
Database recovery decision and potential lost-data window: __________

## Closeout
- [ ] Canonical event URL and key details verified.
- [ ] Registration followed an approved safe test path.
- [ ] Ticket link reached the intended event/provider.
- [ ] Admin access and monitoring checked.
- [ ] Any issue, fix, attendee impact and communication recorded.

Outcome / follow-up owner / next review: __________

This worksheet is an operational record, not a universal platform command list. Follow the actual vendor and incident-response procedure.