The recovery process
Make the next decision from what can be verified.
The sequence depends on the incident. Changes should be authorized, recorded and coordinated with the people who control the affected systems.
Record and scope the incident
Identify the affected website, the visible symptoms, relevant dates and the owner who can approve work. State which systems are included and where host or specialist support is needed.
Preserve useful information
Keep the available site state, backups and relevant records in an appropriate private location. Agree how visitors and the business will be protected while the site is reviewed. Avoid replacing evidence with a series of guesses.
Investigate and propose recovery
Review the affected components and compare cleanup or restoration options. Explain what is known about the cause, what remains uncertain and what the recovery can reasonably include.
Carry out controlled changes
Use a separate copy where practical, keep a record of the work and coordinate necessary owner or provider actions. Test restoration before treating the existence of a backup as enough.
Check the recovered site
Repeat the important page, sign-in, form or commerce tasks using an agreed safe test method. Record checks, remaining questions and the follow-up owner. Any outstanding external warning or provider review should remain explicit.
Tell us what you have noticed.
Use Contact Us at the bottom right or email Faith Forge Labs. Include the public site address and a general description. Keep passwords, private logs and customer records out of the inquiry.
Prepare your first message