US Government Shutdown Preventing SSL Certificates From Being Renewed

The shutdown of the federal government is not only affecting federal workers, but the websites that various departments run. Specifically, SSL certificates are not being renewed.

Larry Loeb, Blogger, Informationweek

January 14, 2019

3 Min Read

The shutdown of the US government -- the longest ever -- is starting to affect more than the 800,000 federal workers who have either been furloughed during this time or told to show up to work but without pay.

As a consequence of these locked-out workers not being at their posts, the SSL certificates used by various government websites that have expired have not been renewed. This lack of certificates can mean that sites or no longer reachable, or they are marked as insecure in their connections.

Sites including the US Justice Department, NASA -- not the main site but some subdomains such as https://rockettest.nasa.gov/ -- and the US Court of Appeals are affected by the lack of over 80 TLS certificates that are used on .gov domains.

The DoJ's https://ows2.usdoj.gov/ is a good example of the problem. Since the site is on Chromium's HTTP Strict Transport Security (HSTS) preload list, the website becomes inaccessible. This is because both Google Chrome and Mozilla Firefox will hide the button -- as HSTS calls for -- that enables users to temporarily ignore the warning about the lack of the TLS system and contact the website.

(Source: Flickr)

(Source: Flickr)

Other browsers generally use the Chrome preload list as the basis of their own preload lists, so there is no workaround for the HSTS situation on these sites by using other browsers.

GlobalSign notes in a company blog post that expiring TLS certificates can have negative consequences for an enterprise or a government agency. The list of issues includes:

"Website Owner: Reduction in trust as the site becomes unsecure; decline in sales and revenue with increased shopping basket abandonments; corporate brand and reputation adversely affected putting the business at risk"

In addition:

"Website User: Warning error messages displayed by browsers when visiting the site; personal information at risk from man-in-the-middle attacks; individual susceptible to fraud and identity theft"

Doug Beattie, GlobalSign's vice president of Product Management, also notes on the company's blog: "We predict that over 600 SSL Certificates currently securing a .gov domain due to expire in October will be potentially affected. To minimize the impact, current automated SSL Certificate life cycle management tools can help in terms of best practice when managing SSL reliance during unforeseen outages."

The shutdown also causes another kind of problem. The sites themselves, whether their certs have expired or not, may not be maintained. Inaccurate or outdated information is likely to be present along with a reduced functionality.

There is little question that the security of the .gov sites will suffer without a valid TLS certificate. In a blog, security vendor Netcraft notes that only a small proportion of .gov sites attempt to set an additional access policy through the Strict-Transport-Security HTTP header. Even if these policies are established they will not be obeyed when they are served alongside an expired certificate.

However, they may be effective if the user has already visited the sites.

With the government IT infrastructure unattended, the shutdown also presents a window for hostile actors to try and infiltrate the .gov infrastructure.

Despite the political arguments the shutdown represents, the practical effect of it is to lessen the security and well-being of anyone that uses the computer systems the government operates.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Read more about:

Security Now

About the Author

Larry Loeb

Blogger, Informationweek

Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek. He has written a book on the Secure Electronic Transaction Internet protocol. His latest book has the commercially obligatory title of Hack Proofing XML. He's been online since uucp "bang" addressing (where the world existed relative to !decvax), serving as editor of the Macintosh Exchange on BIX and the VARBusiness Exchange. His first Mac had 128 KB of memory, which was a big step up from his first 1130, which had 4 KB, as did his first 1401. You can e-mail him at [email protected].

Keep up with the latest cybersecurity threats, newly discovered vulnerabilities, data breach information, and emerging trends. Delivered daily or weekly right to your email inbox.

You May Also Like


More Insights