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

Figure out how to gain access to a service for managing and sending out system alerts and notices #1422

Open
5 tasks
ccostino opened this issue Nov 18, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation epic

Comments

@ccostino
Copy link
Contributor

As Notify.gov continues to grow with more partners and we look toward improving our operational excellence, we'd like to start exploring how we can communicate more effectively with our partners when we have planned maintenance and/or active incidents.

Both Login.gov and cloud.gov use StatusPage.io for this purpose and it may be possible to tap into existing contracting support. If not, then we should look into it setting up our own or finding a similar service that is available to use (by checking GSA's approved software/services list).

Implementation Sketch and Acceptance Criteria

  • Look into existing service offerings in use by TTS and reach out to folks in Login.gov and cloud.gov for more details
  • Speak about this with our ISSO/ISSM
  • Get in touch with purchasing/contracting folks to figure out what's required from us, licenses needed, budget amounts, etc.
  • Get the necessary approvals to make the purchase for access to the tool
  • Set up accounts and permissions for team access

Security Considerations

  • Whatever service we go with must be approved by GSA IT.
  • We'll need to add tracking of account access to our account and permissions tracker 🔒.
  • We may have to make some documentation updates to our SSPP based on what our ISSO/ISSM say.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation epic
Projects
Status: Epics (Less than 3 Months)
Development

No branches or pull requests

1 participant