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

Write collection of change requests for Tracker issues and submit to orgs #4980

Open
3 tasks
h701h opened this issue Nov 29, 2023 · 0 comments
Open
3 tasks
Assignees
Milestone

Comments

@h701h
Copy link
Collaborator

h701h commented Nov 29, 2023

In order:

  • TBS
  • SSC SSC Service Delivery Manager
  • TBD

Issue Type: Task
Summary: Upgrade Website to HTTPS

Description:
Upgrade [Insert Website URL] to use HTTPS for improved security and user trust. Currently, the website is accessible via HTTP, which poses potential security risks and may negatively affect our ..........

Details:

Website URL: [Insert Website URL]
Current Status: The website is currently accessible via HTTP.
Requested Action: Upgrade the website to use HTTPS as per the Web Sites and Services Management Configuration Requirements, section 1.1 which reads Ensure that all production websites and web services are configured to provide service only through a secure connection that is configured for HTTPS (and redirected from HTTP).
Additional Information:

HTTPS implementation should follow best practices, including:
1.1 Ensure that all production websites and web services are configured to provide service only through a secure connection that is configured for HTTPS (and redirected from HTTP).
1.2 Enable HTTP Strict Transport Security (HSTS).
1.3 Follow the guidance Recommendations for TLS Server Certificates for GC Public Facing Web Services for Transport Layer Security (TLS) server certificates.
1.4 Implement TLS 1.2, or subsequent versions, and use supported cryptographic algorithms and certificates, as outlined in:
1.4.1 Guidance on Securely Configuring Network Protocols ITSP.40.062, subsection 3.1 AES Cipher Suites; and
1.4.2 Cryptographic Algorithms for Unclassified, Protected A, and Protected B Information (ITSP.40.111)
1.4.3 Disable all other cryptographic algorithms.
1.5 Disable known weak protocols such as Secure Sockets Layer (SSL) v2 and v3 and TLS 1.0 and 1.1.
1.6 Disable known weak ciphers (RC4 and 3DES).

Acceptance Criteria:

The website must be accessible via HTTPS with a valid SSL certificate.
All internal and external links and resources on the website should use HTTPS.
HTTP requests should be automatically redirected to HTTPS.
The website should be tested for any mixed content issues or security vulnerabilities.

Due Date: [Insert Due Date]

@h701h h701h added this to the 3.x milestone May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants