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

Epic: Pages ATO/ATU website update and Compliance documentation #4430

Closed
17 tasks done
KKAtila opened this issue Mar 25, 2024 · 1 comment
Closed
17 tasks done

Epic: Pages ATO/ATU website update and Compliance documentation #4430

KKAtila opened this issue Mar 25, 2024 · 1 comment
Assignees

Comments

@KKAtila
Copy link

KKAtila commented Mar 25, 2024

The objective of this proposal is to outline a plan to update the Pages website and upload essential security and compliance documents, including ATO/ATU process documentation, CIS/CRM materials, and others, to facilitate seamless access for our customers.

Website Update:

  • Conduct a comprehensive review of the current Pages website to identify areas for improvement in terms of security and compliance documentation.
  • Collaborate with the Pages engineers/web development team to implement necessary updates and enhancements to the website.

Compliance Document Upload
Gather all relevant security and compliance documents, including ATO/ATU process documentation, CIS/CRM materials, and any other pertinent documents.

  • Revise and update the CIS/CRM documents in revision 5 templates to reflect the latest information and best practices (Rev5 CIS/CRM).
  • Review and update the ATO/ATU process documentation outlining the necessary procedures and requirements.
  • Create an updated ATU process flow slide for easy reference and understanding.

Website Integration:
Integrate a dedicated section on the Pages website specifically for security and compliance documents.

  • Organize the documents into categories for ease of navigation.
  • Provide clear instructions for customers on how to access and utilize the compliance documents effectively.

Communication and Publication:

  • Draft an announcement email to inform customers about the website update and the availability of compliance documents.
  • Draft the language to use toward updating the website, include direct links to the compliance documents and or section for easy access.
  • Publish the updated compliance section of the Pages website
  • If possible, monitor customer feedback and inquiries regarding the website update and compliance documents, and address any issues.

Implementation sketch

  • Rev5 CIS/CRM
  • ATO/ATU Process documentation
  • ATU Process flow slide
  • Draft the language to publish on the website
  • Website Integration
  • Communication and Update site Publication

Proposed Task List

  1. squad-pages
    KKAtila
  2. 2 of 2
    squad-pages
    KKAtila
  3. 3 of 3
    squad-pages
    KKAtila
  4. 3 of 3
    squad-pages
    KKAtila
  5. squad-pages
  6. 3 of 3
    squad-pages
    KKAtila
  7. 2 of 3
    squad-pages
    KKAtila
  8. 2 of 2
    squad-pages
    KKAtila
  9. 2 of 2
    squad-pages
    KKAtila
  10. 2 of 2
    squad-pages
    KKAtila
  11. squad-pages
    KKAtila
  12. 4 of 4
    squad-pages
    KKAtila
  13. squad-pages
    KKAtila
  14. squad-pages
    KKAtila
  15. squad-pages
    KKAtila
  16. squad-pages
    Ephraim-G KKAtila
  17. squad-pages
    KKAtila
@KKAtila KKAtila self-assigned this Mar 25, 2024
@sknep sknep changed the title Pages website update and Compliance documentation Proposed Epic: Pages ATO/ATU website update and Compliance documentation Mar 25, 2024
@sknep sknep mentioned this issue Mar 25, 2024
@apburnes apburnes changed the title Proposed Epic: Pages ATO/ATU website update and Compliance documentation Epic: Pages ATO/ATU website update and Compliance documentation Mar 25, 2024
@apburnes
Copy link
Contributor

apburnes commented Oct 2, 2024

Completed

@apburnes apburnes closed this as completed Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Later
Development

No branches or pull requests

3 participants