<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/karim-said/</link>
    <description>Recent content on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/karim-said/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Launch to Landing: How NASA Took Control of Its HTTPS Mission</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2017/05/26/from-launch-to-landing-how-nasa-took-control-of-its-https-mission/</link>
      <pubDate>Fri, 26 May 2017 12:00:50 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2017/05/26/from-launch-to-landing-how-nasa-took-control-of-its-https-mission/</guid>
      <description>18F Editor’s note: This is a guest post by Karim Said of NASA. Karim was instrumental in NASA’s successful HTTPS and HSTS migration, and we’re happy to help Karim share the lessons NASA learned from that process. In 2015, the White House Office of Management and Budget released M-15-13, a “Policy to Require Secure Connections</description>
    </item>
  </channel>
</rss>
