Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft FAC Contingency Plan SOP #1677

Closed
Tracked by #725 ...
ChrisB-16 opened this issue Aug 2, 2023 · 6 comments
Closed
Tracked by #725 ...

Draft FAC Contingency Plan SOP #1677

ChrisB-16 opened this issue Aug 2, 2023 · 6 comments
Assignees
Labels
compliance Stuff which may relate to a specific requirement or timelines for resolution security SHOULD Things we should do for the tracking epic to be "satisfactory"

Comments

@ChrisB-16
Copy link
Contributor

In order to meet FAC ATO A&A security control requirements
as a FAC system owner I should document the workflow steps needed to recover or reconstitute the FAC system if any unforeseen circumstances occur, track all details within FAC Contingency Plan SOP .

@ChrisB-16 ChrisB-16 added compliance Stuff which may relate to a specific requirement or timelines for resolution security labels Aug 2, 2023
@ChrisB-16
Copy link
Contributor Author

  • GSA CP Plan template is being updated to track FAC CP details
  • Cloud.gov CP security controls are being reviewed & applicable statements will be tracked for FAC inheritance, since FAC is hosted within Cloud.gov
  • Additional details are being tracked by FAC operations team, when ready all technical implementation details necessary to help execute a effective CP action plan will be merged within final FAC CP Plan SOP

@mogul
Copy link
Contributor

mogul commented Aug 3, 2023

@ChrisB-16
Copy link
Contributor Author

Greetings Bret,

Thanks for details I will review and update the FAC CP accordingly.

https://docs.google.com/document/d/13iu4ZgumcWEemV68ocmcxoJiLMByc3mo/edit

@mogul mogul added MUST Things we gotta do for the tracking epic to be "minimal" SHOULD Things we should do for the tracking epic to be "satisfactory" and removed MUST Things we gotta do for the tracking epic to be "minimal" labels Aug 8, 2023
@mogul
Copy link
Contributor

mogul commented Aug 15, 2023

Changing this to a SHOULD since there was no SAR finding.

@jadudm jadudm added the REVISIT Triaged out of a 3-month window. label Sep 8, 2023
@jadudm jadudm added this to FAC Sep 14, 2023
@jadudm jadudm moved this from Triage to Backlog in FAC Sep 14, 2023
@github-project-automation github-project-automation bot moved this to Triage in FAC Sep 14, 2023
@jadudm jadudm removed the REVISIT Triaged out of a 3-month window. label Sep 14, 2023
@danswick danswick moved this from Backlog to In Progress in FAC Apr 1, 2024
@danswick danswick mentioned this issue May 17, 2024
@danswick
Copy link
Contributor

We're considering this blocked while backup and restore work is ongoing. We also need the system owner to review and sign-off.

@danswick danswick moved this from In Progress to Blocked in FAC May 21, 2024
@danswick
Copy link
Contributor

This is done. Latest document is on Drive here.

@github-project-automation github-project-automation bot moved this from Blocked to Done in FAC May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compliance Stuff which may relate to a specific requirement or timelines for resolution security SHOULD Things we should do for the tracking epic to be "satisfactory"
Projects
Status: Done
Development

No branches or pull requests

5 participants