Skip to content

Commit db963af

Browse files
konklonemlazzeri
authored andcommitted
Clarify non-HTTP protocols and the use of port 80 (GSA#207)
* clarify that non-HTTP protocols are not covered * add FAQ item about cutitng off port 80 * fix links and ToC, tweak wording
1 parent 7528e01 commit db963af

1 file changed

Lines changed: 28 additions & 8 deletions

File tree

pages/guide.md

Lines changed: 28 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,13 +14,15 @@ This page provides implementation guidance for agencies by the White House Offic
1414
* [Compliance and best practice checklist](#compliance-and-best-practice-checklist)
1515
* [Options for HSTS compliance](#options-for-hsts-compliance)
1616
* [Compliance FAQ](#compliance-faq)
17-
* [What does "all Federal agency domains or subdomains" include?](#what-does-"all-federal-agency-domains-or-subdomains"-include?)
18-
* [What about domains that are only used to redirect visitors to other websites?](#what-about-domains-that-are-only-used-to-redirect-visitors-to-other-websites?)
19-
* [What about domains that are technically public, but in practice are only used internally?](#what-about-domains-that-are-technically-public,-but-in-practice-are-only-used-internally?)
20-
* [What happens to visitors using browsers that don’t support HSTS, like older versions of Internet Explorer?](#what-happens-to-visitors-using-browsers-that-don't-support-hsts,-like-older-versions-of-internet-explorer?)
21-
* [This site redirects users to HTTPS -- why is Pulse saying it doesn't enforce HTTPS?](#this-site-redirects-users-to-https----why-is-pulse-saying-it-doesn't-enforce-https?)
22-
* [Are federally operated certificate revocation services (CRL, OCSP) also required to move to HTTPS?](#are-federally-operated-certificate-revocation-services-(crl,-ocsp)-also-required-to-move-to-https?)
23-
* [What if I'm using a federally issued certificate -- such as from the Federal PKI or Department of Defense -- for my web service?](#what-if-i'm-using-a-federally-issued-certificate----such-as-from-the-federal-pki-or-department-of-defense----for-my-web-service?)
17+
* [What protocols are covered by M-15-13?](#what-protocols-are-covered-by-m-15-13%3f)
18+
* [Do I need to shut off port 80?](do-i-need-to-shut-off-port-80%3f)
19+
* [What does "all Federal agency domains or subdomains" include?](#what-does-"all-federal-agency-domains-or-subdomains"-include%3f)
20+
* [What about domains that are only used to redirect visitors to other websites?](#what-about-domains-that-are-only-used-to-redirect-visitors-to-other-websites%3f)
21+
* [What about domains that are technically public, but in practice are only used internally?](#what-about-domains-that-are-technically-public,-but-in-practice-are-only-used-internally%3f)
22+
* [What happens to visitors using browsers that don’t support HSTS, like older versions of Internet Explorer?](#what-happens-to-visitors-using-browsers-that-don't-support-hsts,-like-older-versions-of-internet-explorer%3f)
23+
* [This site redirects users to HTTPS -- why is Pulse saying it doesn't enforce HTTPS?](#this-site-redirects-users-to-https----why-is-pulse-saying-it-doesn't-enforce-https%3f)
24+
* [Are federally operated certificate revocation services (CRL, OCSP) also required to move to HTTPS?](#are-federally-operated-certificate-revocation-services-(crl,-ocsp)-also-required-to-move-to-https%3f)
25+
* [What if I'm using a federally issued certificate -- such as from the Federal PKI or Department of Defense -- for my web service?](#what-if-i'm-using-a-federally-issued-certificate----such-as-from-the-federal-pki-or-department-of-defense----for-my-web-service%3f)
2426

2527

2628
## Compliance and best practice checklist
@@ -74,6 +76,24 @@ This approach allows agencies the flexibility to focus only on publicly accessib
7476

7577
Answers to other common compliance questions appear below.
7678

79+
### What protocols are covered by M-15-13?
80+
81+
M-15-13 requires secure connections for **websites and web services**, which means **only HTTP-based protocols**. This includes all federal websites, as well as federally operated HTTP-based APIs.
82+
83+
M-15-13 does not address the use of DNS or DNSSEC, FTP or SFTP, or any other non-HTTP network protocol.
84+
85+
### Do I need to shut off port 80?
86+
87+
**No.** [M-15-13 states](https://https.cio.gov/#footnote-3):
88+
89+
> Allowing HTTP connections for the sole purpose of redirecting clients to HTTPS connections is acceptable and encouraged.
90+
91+
Agencies may employ port 80 for the sole purpose of redirecting clients to a secure connection.
92+
93+
Note that while connections to port 80 are insecure, even for redirects, the use of [HSTS](/hsts/]) will instruct supporting HTTP clients to automatically redirect themselves from port 80 to port 443, without attempting to connect to port 80 over the network.
94+
95+
HSTS mitigates the security impact of connections over port 80, while allowing agencies the flexibility to continue redirecting legacy clients or clients which have not yet received an HSTS policy for the target domain.
96+
7797
### What does "all Federal agency domains or subdomains" include?
7898

7999
Domains and subdomains, in the context of M-15-13, refer to hostnames that are publicly accessible via HTTP or HTTPS.
@@ -123,7 +143,7 @@ Agencies are encouraged to operate OCSP and CRL services via hostnames specifica
123143

124144
### What if I'm using a federally issued certificate -- such as from the Federal PKI or Department of Defense -- for my web service?
125145

126-
There are [no restrictions on acceptable certificate authorities](/certificates/#are-there-federal-restrictions-on-acceptable-certificate-authorities-to-use?) agencies might use to meet the requirements of M-15-13.
146+
There are [no restrictions on acceptable certificate authorities](/certificates/#are-there-federal-restrictions-on-acceptable-certificate-authorities-to-use%3f) agencies might use to meet the requirements of M-15-13.
127147

128148
However, M-15-13 requires agencies to do more than just redirect HTTP traffic to HTTPS. It also requires agencies to enable **[HTTP Strict Transport Security](/hsts/)** (HSTS), as [described above](#options-for-hsts-compliance). HSTS ensures that HTTPS is always used, and protects users from several common vulnerabilities.
129149

0 commit comments

Comments
 (0)