GSA-TTS / tts.gsa.gov

Making the website work for people who make websites work
https://federalist-a2423046-fe43-4e75-a2ef-2651e5e123ca.sites.pages.cloud.gov/preview/gsa-tts/tts.gsa.gov/staging/
Other
5 stars 3 forks source link

Add Continuity Plan (CP) #141

Open wesley-dean-gsa opened 1 month ago

wesley-dean-gsa commented 1 month ago

The Incident Response document mentions a Continuity Plan (they said "Contingency Plan"); however, no such document exists. The only documents that exist are IR.md (Incident Response) and CM.md (Configuration Management). While likely not required under our ATU, it would be good to either include one or remove the reference. (the only thing worse than no documentation is wrong documentation)

wesley-dean-gsa commented 1 month ago

https://gsa-tts.slack.com/archives/CG8SNAEQM/p1723583957069759

tl;dr: the TTS handbook references the Cloud.gov Contingency Plan which is no longer found under their public-facing Team Documentation section.

wesley-dean-gsa commented 3 weeks ago

per slack:

Paul/Wes, great timing on this question! We, here in Tech Ops, have been working on closing out an open POA&M/weakness relating to the GSA Pages COOP documentation and testing. As we speak, the docs are undergoing a final review by our ISSO. All GSA Pages websites will be able to leverage the updated BIA (Business Impact Analysis), ISCP (Info System Contingency Plan) and TTX artifacts (table top exercise plan and after action report), once they become official. Stay tuned.

wesley-dean-gsa commented 3 weeks ago

I added the Blocked label as we're waiting on Tech Ops to have their documentation reviewed by their ISSO. Upon approval, their documentation will be "official" and we'll be able to use them.

debjudy commented 3 weeks ago

Worked in sprint 3; however moved back to backlog since we have dependency on Cloud team. Keeping in backlog because we should have it, so we don't lose awareness of the need.