<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Defense Digital Service on Medium]]></title>
        <description><![CDATA[Stories by Defense Digital Service on Medium]]></description>
        <link>https://medium.com/@DefenseDigitalService?source=rss-1aa4e8205e68------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KYCrre6RoAL-igNsU99Xdw.png</url>
            <title>Stories by Defense Digital Service on Medium</title>
            <link>https://medium.com/@DefenseDigitalService?source=rss-1aa4e8205e68------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:05:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DefenseDigitalService/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Hack the Marine Corps results are in!]]></title>
            <link>https://medium.com/@DefenseDigitalService/hack-the-marine-corps-results-are-in-3d6f95bf534b?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d6f95bf534b</guid>
            <category><![CDATA[technology-news]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[department-of-defense]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 15:26:28 GMT</pubDate>
            <atom:updated>2018-10-03T15:46:12.720Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Hackers work alongside Marines to discover and disclose nearly 150 vulnerabilities</em></h4><p>We know that adversaries are continually working to exploit our networks and cripple critical operations. They don’t hold back — and in order to fight and win in all domains, neither can we. That’s why last month we launched Hack the Marine Corps, the Defense Department’s sixth public bug bounty challenge. We partnered with private-sector security firm HackerOne and the U.S. Marine Corps Cyberspace Command (MARFORCYBER) to deploy over one-hundred of the world’s top ethical hackers on the U.S. Marine Corps public-facing websites and services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T5-G5tFOjXlWykWxMbYJLQ.jpeg" /><figcaption>Ethical hackers collaborate with Marines to spotlight findings during the challenge. Photo credit: HackerOne.</figcaption></figure><p>The challenge kicked off last month in Las Vegas — coinciding with the world’s largest hacker and security conferences, Black Hat USA, DEF CON and BSides — as leading security researchers and Marines convened for ten hours of live-hacking. The hackers and Marines had one shared goal: better securing U.S. Marine Corps digital assets. Once the launch event concluded, participants were able to continue to hack away over the next twenty days while U.S. Marine personnel worked diligently to rapidly respond to and remediate bugs.</p><p>And, the results are in!</p><h4><strong>Hack the Marine Corps by the Numbers</strong></h4><ul><li>Hack the Marine Corps engaged <strong>105</strong> registered and vetted hackers from across the globe.</li><li>The challenge focused on roughly <strong>200</strong> public-facing websites.</li><li>Over <strong>150 </strong>valid vulnerabilities were discovered and reported.</li><li>Hackers who submitted valid vulnerabilities received a total of <strong>$151,542</strong> for these findings.</li><li>During the launch event, hackers filed <strong>75</strong> unique valid security vulnerability reports and were initially awarded over <strong>$80,000</strong>.</li><li>The top performing researcher took home a collective <strong>$26,900</strong> for identifying multiple vulnerabilities.</li><li>While contracts for security assessments can cost millions of dollars and take many months to run, the total cost for the Hack the Marine Corps challenge was <strong>$350,000</strong>.</li><li>This is the Department of Defense’s <strong>eleventh </strong>bug bounty program and its <strong>sixth</strong> bug bounty focused on public-facing assets.</li><li>Since the launch of Hack the Pentagon in 2016, nearly <strong>1,000</strong> valid vulnerabilities have been reported through our bug bounty challenges.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wxsb0sB7IOiajtyrwrF5Q.jpeg" /><figcaption>Photo credit: HackerOne.</figcaption></figure><blockquote>“It was an honor to work on the Marine Corps program. This opportunity to help improve the security of the armed forces was not only fun, but it made me feel proud to give back. Working alongside the Marine Corps in-person felt like we were all on the same team.” — Nathanial Lattimer, ethical hacker participant &amp; security engineer at Dropbox</blockquote><p>Like other Defense Department bug bounties, the range of reported vulnerabilities identified through Hack the Marine Corps have varying degrees of potential impact. For instance, they can include inadvertent system-related information disclosure, improper access to personally identifiable information, the ability to access or edit public-facing sites without proper permissions, or security gaps that could allow malicious attacks.</p><p>One of the most interesting findings during the Hack the Marine Corps challenge was when a group of three hackers were able to access certain records related to Marine Corps personnel. The three hackers split one of the single largest payouts of the event: $10,000.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K5tvX5TzKocq88BamADOAA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GEFcaK0hPsAM1gsNOGIo8A.jpeg" /><figcaption>Photo credit: HackerOne</figcaption></figure><blockquote>“During Hack the Marine Force, security researchers from all around the world effectively worked together to help secure the U.S. Department of Defense. — Inti de Ceukelaire, ethical hacker participant &amp; creative developer, Belgium</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*jEubexo5GcrF8VjoiuBzJg.jpeg" /><figcaption>DDS Chief Information Security Officer Alex Romero and Major General Matthew Glavy review hacker reports.</figcaption></figure><blockquote><strong>“Hack the Marine Corps was an incredibly valuable experience. When you bring together this level of talent from the ethical hacker community and our Marines we can accomplish a great deal. What we learn from this program assists the Marine Corps in improving our warfighting platform. Our cyber team of Marines demonstrated tremendous efficiency and discipline, and the hacker community provided critical, diverse perspectives. The tremendous effort from all of the talented men and women who participated in the program makes us more combat ready and minimizes future vulnerabilities,”</strong></blockquote><blockquote><strong>— Major General Matthew Glavy, Commander, U.S. Marine Corps Forces Cyberspace Command.</strong></blockquote><p>At the Defense Department, people are our greatest asset. It is our responsibility to ensure they are continually safeguarded and supported. Challenges like Hack the Marine Corps help the Department to identify and fix bugs before they can be exploited, and to minimize future vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-NJKP56_ncSD5FUQh1hQPw.jpeg" /><figcaption>Hack the Pentagon Program Manager Reina Staley and DDS team member Jack Cable monitor results.</figcaption></figure><h4><strong>Hack the Pentagon</strong></h4><p>Hack the Marine Corps is part of our Hack the Pentagon crowd-sourced security initiative. Recognizing many of the nation’s biggest companies use bug bounties to improve the security and delivery of digital services, the Defense Digital Service launched the federal government’s first bug bounty challenge in 2016, proving hackers and hoodies have an important role to play in supporting national defense.</p><p>Since the launch of Hack the Pentagon, we’ve led bug bounties to hack the Army, the Air Force — twice, the Defense Travel System, and other internal DoD systems. Other public bug bounty challenges include:</p><ul><li><a href="http://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fwww.usds.gov%2Freport-to-congress%2F2017%2F07%2Fhack-the-pentagon%2F&amp;esheet=51851706&amp;newsitemid=20180813005420&amp;lan=en-US&amp;anchor=Hack+the+Pentagon&amp;index=3&amp;md5=9caa2f9d76be786ddc60a83c93f36bcb"><strong>Hack the Pentagon</strong></a> launched in May 2016 and resulted in over 130 valid vulnerabilities resolved and tens of thousands of dollars paid to ethical hackers.</li><li><a href="http://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fwww.hackerone.com%2Fblog%2FHack-The-Army-Results-Are-In&amp;esheet=51851706&amp;newsitemid=20180813005420&amp;lan=en-US&amp;anchor=Hack+the+Army&amp;index=4&amp;md5=341798c6d3b67205ddac92eae443fb59"><strong>Hack the Army</strong></a> launched in December 2016 and surfaced over 115 valid vulnerabilities resolved and paid $100,000 to hackers.</li><li><a href="http://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fwww.businesswire.com%2Fnews%2Fhome%2F20170810005301%2Fen%2FU.S.-Air-Force-Awards-130000-Hackers-HackerOne&amp;esheet=51851706&amp;newsitemid=20180813005420&amp;lan=en-US&amp;anchor=Hack+the+Air+Force&amp;index=5&amp;md5=21b7ef49f239d86f536f46c0f29319c4"><strong>Hack the Air Force</strong></a> launched in April 2017 and resulted in over 200 valid vulnerabilities resolved and more than $130,000 paid to hackers.</li><li><a href="http://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fwww.businesswire.com%2Fnews%2Fhome%2F20180215005220%2Fen%2FU.S.-Air-Force-Boosts-Security-Bug-Bounty&amp;esheet=51851706&amp;newsitemid=20180813005420&amp;lan=en-US&amp;anchor=Hack+the+Air+Force+2.0&amp;index=6&amp;md5=7dfbbf5180f4b32f12b5e159ebc5d7de"><strong>Hack the Air Force 2.0</strong></a> launched in December 2017 and resulted in over 100 valid vulnerabilities resolved and $103,883 paid to hackers.</li><li><a href="http://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fwww.businesswire.com%2Fnews%2Fhome%2F20180402005247%2Fen%2FU.S.-Department-Defense-Kicks-Bug-Bounty-Challenge&amp;esheet=51851706&amp;newsitemid=20180813005420&amp;lan=en-US&amp;anchor=%0AHack+the+Defense+Travel+System&amp;index=7&amp;md5=6a3ca2088cf0a4c8b4df2c545aa8af1f"><strong>Hack the Defense Travel System</strong></a> launched in April 2018 and focused on testing a DoD enterprise system and resulted in 100 security vulnerabilities reported and $80,000 paid to hackers.</li></ul><p>As part of Hack the Pentagon, the Defense Department launched its Vulnerability Disclosure Policy in 2016 to provide a legal avenue for security researchers to find and disclose vulnerabilities in any DoD public-facing systems. After the close of bug bounty challenges, hackers who become aware of vulnerabilities can<a href="http://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fhackerone.com%2Fdeptofdefense&amp;esheet=51851706&amp;newsitemid=20180813005420&amp;lan=en-US&amp;anchor=disclose+them+to+the+DoD&amp;index=8&amp;md5=f29afbe550fe726bc6ec58e2f32c2cc7"> disclose them to the DoD</a> through its ongoing vulnerability disclosure program. Thousands of valid vulnerabilities have since been reported through our Hack the Pentagon crowdsourced security initiative.</p><p>Turning to the global ethical hacker community allows us to tap into new perspectives and ways of thinking to boost national security and hunt for vulnerabilities. We’re excited to see Hack the Pentagon continue to build momentum and bring together ethical hackers who want to make a difference and help protect our nation. Thank you to the U.S. Marine Corps and the hackers who joined us from all over the globe!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qvbdhmFZLdCvdp4MnCgqrg.jpeg" /></figure><p>Stay tuned as we continue working to bring in the best talent, technology, and approaches from the private sector to help transform government IT and better protect our country.</p><blockquote>“It was great having the opportunity to work side by side with the Marines to help secure their assets. These are my favorite types of programs to be a part of, because they allow me to have a massive impact on systems critical to national security.” — Tanner Emek, ethical hacker participant &amp; full time bug bounty hunter</blockquote><h4><strong><em>Join Us!</em></strong></h4><p>Interested in proving hoodies, hackers, and nerds have an important role to play in furthering national defense missions? We’ve built a team at the Pentagon of top technical talent to transform how the Defense Department builds and delivers digital services and products for the three million civilian and military employees in the U.S. and around the world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TYX6QNsbon__liqliv8gKQ.jpeg" /><figcaption>After winning the Hack the Air Force challenge, renowned ethical hacker Jack Cable was recruited by and<br>joined DDS for a tour of duty this summer. 18-year old Cable helped to support the Hack the Marine Corps<br>Challenge, lending his unique, hacker security skills and perspective towards the planning of the challenge. Jack provides an overview to Hackers at the launch event of the challenge scope. Photo credit: HackerOne.</figcaption></figure><p><a href="https://www.usds.gov/join.html">Learn about opportunities to work with us to improve government technology.</a> <a href="http://www.dds.mil/">DDS</a> is an agency branch of the <a href="http://www.usds.gov/">U.S. Digital Service</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d6f95bf534b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Iterating on Code.mil]]></title>
            <link>https://medium.com/defense-digital-service/iterating-on-code-mil-1b5f70cb6c0b?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b5f70cb6c0b</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[department-of-defense]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[free-software]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 17:43:21 GMT</pubDate>
            <atom:updated>2018-02-13T17:43:21.411Z</atom:updated>
            <content:encoded><![CDATA[<p>No one ever said open sourcing code at the Department of Defense (DoD) would be easy. [citation needed]</p><p>In February 2017, the Defense Digital Service (DDS) decided it was time to take a more involved approach within the Department of Defense in the government-wide movement to open source code. This was spurred by the release of the new Federal Source Code Policy by the Office of Management and Budget in August, 2016 and <a href="https://www.code.gov/">Code.gov</a> in November, 2016. We spent a lot of time talking with people in the DoD, across the federal government, and leaders in the Free / Open Source Software (F/OSS) community. Thus we formed <a href="https://medium.com/@DefenseDigitalService/code-mil-an-open-source-initiative-at-the-pentagon-5ae4986b79bc">a new project called Code.mil</a> and created a <a href="https://github.com/deptofdefense/code.mil">GitHub repository</a> providing guidance on how to open source code at the DoD.</p><p>It’s been a long time coming, but that guidance — and its organization and presentation — has received a well-needed refresh with today’s (re)launch of <a href="http://www.code.mil/">Code.mil</a>, an experiment in open source at the Department of Defense. Our guidance has been reorganized into an easy to digest website and we’re investing in further improvements.</p><h3>Unique Challenges</h3><p>The DoD faces many challenges in open sourcing code. Unlike most software projects, code written by U.S. Federal government employees typically does not have copyright protections under U.S. and some international laws. Often times this makes people think that our code can’t use an OSS license, but this is far from true! It does, however, require a little more effort to define our intent. The complexity of national security policy adds another point of difficulty when individual program offices look to open source their work. Even with approval to release code publicly, government employees can be hindered by lack of access to modern source control and developer operations processes.</p><p>Those barriers are precisely what DDS is good at tackling. The guidance we’re providing at Code.mil will help many projects across the Department by giving developers and product owners a template to start from and the necessary background information to share with people in their organization who may not be familiar with open source software. The site also highlights the policy and laws that affect custom-developed code written by U.S. government employees — or contractors working with us — so that people are informed about the requirements placed on them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vT_M86FkRmD5q_oMIFtQjg.png" /></figure><h3>Working with Our Friends at Code.gov</h3><p>Many challenges DoD faces in open sourcing software are not unique. The U.S. Federal Government has been mandated to open source 20% of new, custom-developed code for a three year pilot program that began in August 2016. This is the “<a href="https://www.code.gov/#/policy-guide/docs/open-source/introduction">Open Source Pilot Program</a>” that was authorized by OMB policy M-16–21 to ascertain the appropriate amount of code to open source and how to best measure that amount. The policy also set up the team at <a href="https://www.code.gov/">Code.gov</a> to facilitate government-wide implementation of the policy . We launched Code.mil to further the mission of Code.gov within DOD.</p><p>The Code.gov team is doing awesome work! The DDS crew (and DoD CIO) have been working closely with their folks to determine what next steps the DoD needs to take and how we can begin to comply with the policy. A big part of that is beginning to expand our <a href="https://code.gov/#/explore-code/agencies/">agency project listing</a>. Projects listed on Code.mil will also be accessible through Code.gov as it continues to grow the inventory of government open source code.</p><h3>What’s Next? What can you do?</h3><p>Providing guidance and creating an inventory of code is great, but we want more. The Defense Digital Service strives for the big wins, doing the most good for the most people in the most need. We feel strongly about Free / Open Source Software (F/OSS) and want to help make its use the normal path in the Department, not an exception.</p><p>To that end we are working closely with the DoD Chief Information Officer’s people to revise the <a href="http://dodcio.defense.gov/Portals/0/Documents/FOSS/2009OSS.pdf">2009 memo</a> clarifying the Department’s position on the use of Free and Open Source Software. We’re engaging organizations throughout the DoD to help them kickstart their open source initiatives. We’re working with thought leaders both inside the Department and in the F/OSS community to make our guidance more in tune with the needs of the Department and the American people.</p><p>And we’re engaging with you. Right now. This blog post is one of many avenues we are using to engage directly. Read our documentation on the <a href="https://github.com/deptofdefense/code.mil">Code.mil website</a> and let us know what we can improve by <a href="https://github.com/deptofdefense/code.mil/issues">submitting an issue</a> or a Pull Request. If you are a DoD project owner contact us at <a href="/service/mailto:code@dds.mil">code@dds.mil</a> so that we can hear your story or help get you started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b5f70cb6c0b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-digital-service/iterating-on-code-mil-1b5f70cb6c0b">Iterating on Code.mil</a> was originally published in <a href="https://medium.com/defense-digital-service">Defense Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code.mil: An Open Source Initiative at the Pentagon]]></title>
            <link>https://medium.com/hackernoon/code-mil-an-open-source-initiative-at-the-pentagon-5ae4986b79bc?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ae4986b79bc</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[department-of-defense]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[free-software]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Mon, 13 Mar 2017 04:02:01 GMT</pubDate>
            <atom:updated>2017-03-22T02:04:25.162Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building bridges between the Department of Defense and the software development community, one pull request at a time</h4><p>The Department of Defense (DoD) is a behemoth Federal agency built upon closed proprietary software and legacy systems that have been continually outpaced by modern technology and development standards. While the DoD has made strides towards modernization, one arena that has yet to be fully embraced and implemented is the practice of free and open source software.</p><p>Our team at the <a href="https://www.dds.mil/">Defense Digital Service </a>(DDS) was formed by Secretary of Defense to bring in private sector best talent, practices and technology into the DoD. Most of us hail from companies such as Google and Amazon, and from environments where open source is commonplace. We at DDS deeply believe that code developed by Federal employees should be available for reuse and collaboration not only across the rest of government, but the public too.</p><p>As a result, we created <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a>, an initiative that allows developers around the world to reuse and contribute to unclassified code written by Federal employees in support of DoD programs, which in turn support services for millions of people around the globe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/229/1*QIbaP7IznI7MvwBV3ZsegQ.jpeg" /></figure><h3>Open source in the Federal space</h3><p>The concept of open source in government is not a brand new one: in fact, the White House launched <a href="https://code.gov/">Code.gov</a> last November, which is the Federal government’s primary platform for code sharing and reuse. <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a> is our direct implementation of this mission to “improve access to the Federal government’s custom developed software.” We want to promote the concept of open source across the vast DoD landscape, and demonstrate its utility by hosting projects developed by our own engineering talent. The many projects hosted on <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a> will also be available on <a href="https://code.gov/">Code.gov</a>.</p><h3>How <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code. mil</a> is different</h3><p>The DoD is a policy driven organization, where many technology efforts and ideas spend years incubating in numerous meetings and briefings before resulting in any tangible output. By this point, the output (typically a policy) has since become outdated or too static and prescriptive, and arrests our capability to quickly adapt to the ever-changing technology landscape.</p><p><strong>Rather than going the traditional route, the </strong><a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense"><strong>Code.mil</strong></a><strong> team decided to take an unconventional approach — at least by Pentagon standards.</strong></p><p>DDS General Counsel, Sharon Woods, and DDS engineers, Brandon Bouier and Tom Bereknyei, partnered together to create a developer-centric strategy that empowers individual contributors and creatively navigates the legal framework. DDS worked in consultation with organizations like the <a href="https://opensource.org/">Open Source Initiative</a> and <a href="http://www.fsf.org/">Free Software Foundation</a> for this first iteration.</p><p>We also decided to share a <a href="https://github.com/deptofdefense/code.mil/blob/master/Proposal/CONTRIBUTING.md">draft strategy on GitHub</a> to actively engage in public discourse and crowdsource community input to codify a licensing pathway that makes the most sense for our unique situation. Through combining both legal and developer expertise, our metric for <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a>’s success is defined by the level of active collaboration with the free and open source communities on DoD projects rather than written guidance or policy.</p><h3><strong>Our new licensing strategy</strong></h3><p>At the start of <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a>, our team wanted to experiment with using a legal avenue in contract law to create an arrangement similar to what is commonplace in the open source community. After soliciting feedback from the developer and legal communities across the Federal government and private sector, DDS settled on a simpler solution to reuse existing free and open source software licensing practices.</p><p>While all of the work done by Federal employees remains in the public domain with no restrictions, public contributors enjoy the protections of widely adopted free and open source licenses. As projects mature, the aggregate work — with all the patches, bug fixes, and additional features — will fall under the license associated with the project. To simplify the contribution process even further, DDS is releasing a <a href="https://github.com/deptofdefense/dco-bot">GitHub webhook</a> that will facilitate the verification of commits having followed the <a href="https://developercertificate.org/">Developer Certificate of Origin</a> process.</p><p>All of these elements collectively allow the DoD to tap into a vast pool of talent and creativity otherwise excluded from contributing to DoD efforts.</p><h3><strong>What drives </strong><a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense"><strong>Code.mil</strong></a></h3><p>There is a huge resource of developer talent within the DoD that would love to leverage some of the modern tools used in the tech industry to share code and ideas. Likewise, there are many skilled developers in private sector who would love to contribute to strengthening software developed within the government.</p><blockquote>As Eric Raymond famously wrote, “given enough eyeballs, all bugs are shallow.”</blockquote><p>Opening up DoD codebases for the world to see allows code vulnerabilities to be identified and remediated more quickly than current internal methods. This crowdsourced concept is similar to how public bug bounties like <a href="https://medium.com/the-u-s-digital-service/hacking-the-pentagon-69486aa9f226#.yxkd6w9qn">Hack the Pentagon</a> were successful in allowing the public to aid the DoD in identifying and fixing bugs faster and at a lower cost than the DoD could on its own.</p><p>Giving everyone the freedom to run, copy, distribute, study, change and improve software developed by DoD is a public good from which everyone should benefit. This is especially true considering that much of the code developed by the Federal government is funded by taxpayer dollars. This is one of the reasons why we are releasing our own custom-developed code on Code.mil.</p><h3>Our first release, <a href="https://github.com/deptofdefense/eMCM">eMCM</a></h3><p>Code.mil just released its first open source project, <a href="https://github.com/deptofdefense/eMCM">eMCM</a>: it’s a web-based viewer of the Manual for Courts-Martial (MCM). The MCM is the official guide to the conduct of Courts-martial in the U.S. military. The current process of updating the MCM is very manual and tedious, involving multiple trips across different military organizations and hours of looking for typos and inconsistencies. The MCM is republished only every several years, resulting in many out-of-date manuals in circulation.</p><p>Our team developed the <a href="https://github.com/deptofdefense/eMCM">eMCM</a> to modernize this process by enabling the military to maintain a canonical “live” edition of the manual that is easily accessible, while also maintaining prior versions of the manual for legal purposes.</p><p>We chose to use the Affero General Public License (AGPL) for the <a href="https://github.com/deptofdefense/eMCM">eMCM </a>because every military member has the right to know how the raw legal code (<em>i.e</em>., MCM) will be transformed or manipulated by the <a href="https://github.com/deptofdefense/eMCM">eMCM</a>. Applying the AGPL is a small but important way to help ensure the public has that freedom and transparency to the process. The <a href="https://github.com/deptofdefense/eMCM">eMCM</a> is still in beta so we welcome any suggestions for the viewer.</p><h3><strong>What’s next on </strong><a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense"><strong>Code.mil</strong></a></h3><p><a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a> will continue to iterate and expand as we gather more feedback from contributors and host more projects from across DoD on our platform. Future phases may include making <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a> a full fledged website rather than just a redirect to the GitHub repository, expanding the repository to include projects from other DoD offices, tackling procured source code, and addressing how this strategy might facilitate technology transfer.</p><p>Our hope is that <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a> will encourage conversation around these topics and allow anyone around the world to contribute knowledge and code for DoD projects. We invite everyone to open an issue or submit a pull request with your ideas on future directions for <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a>.</p><h3><strong>Host your project on </strong><a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense"><strong>Code.mil</strong></a></h3><p><a href="https://mcm.mil/">eMCM</a> is just the first of many projects we would love to host on <a href="https://github.com/deptofdefense/code.mil#welcome-to-codemil---an-experiment-in-open-source-at-the-department-of-defense">Code.mil</a>. We hope that this effort will continue to encourage other components and offices within the DoD and Military Departments to benefit from releasing their code as open source too.</p><p><strong>If you are a Federal employee and have a program or project you would like to share, start the conversation by connecting with us directly at code@dds.mil.</strong></p><h3>Happy coding!</h3><p><em>Learn more about the Defense Digital Service team </em><a href="https://www.dds.mil/">here</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ae4986b79bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/code-mil-an-open-source-initiative-at-the-pentagon-5ae4986b79bc">Code.mil: An Open Source Initiative at the Pentagon</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data.mil: An Experiment in Defense Open Data]]></title>
            <link>https://medium.com/defense-digital-service/data-mil-an-experiment-in-defense-open-data-259f58bcaafb?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/259f58bcaafb</guid>
            <category><![CDATA[department-of-defense]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[open-data]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Thu, 15 Dec 2016 17:31:01 GMT</pubDate>
            <atom:updated>2016-12-15T19:07:44.272Z</atom:updated>
            <content:encoded><![CDATA[<h4>Major Aaron Capizzi and Mary Lazzeri on open data in the Department of Defense, experimentation, and inviting public collaboration</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*vSZYPC6bLoWIDwIf8T4J_w.png" /><figcaption>Landing page for data.mil.</figcaption></figure><p><strong>Can you tell us the story of how </strong><a href="https://www.data.mil/"><strong>Data.mil</strong></a><strong> got started?</strong></p><p><strong>Aaron:</strong> I was fortunate to attend a panel discussion at the Harvard Kennedy School sponsored by former Deputy CTO, Nick Sinai. Listening to Marina Martin and Tim O’Reilly talk about the ideals and power behind open data, I realized many of the barriers to innovation I had encountered within the Department of Defense revolved around limited access to information. Finding and unlocking defense data became a valuable quest. Open data can empower DOD employees to research, understand, and solve their own problems. This became the motivation behind <a href="https://www.data.mil/">Data.mil</a>. Around that same time, I landed a job just upstairs from the newly created Defense Digital Service (DDS) in the Pentagon.</p><p><strong>Mary: </strong>I was introduced to Aaron and immediately realized he had a great idea on his hands. The DoD’s open data program needed a jump start. DDS had the expertise and resources to build <a href="https://www.data.mil/">Data.mil</a>, but I wanted to do it lean. The goal was to get something out there, gather feedback, iterate, improve and ultimately expand. Too many good ideas get bogged down by bureaucratic constraints, real and imagined. With a narrow, targeted scope, I knew we could release a beta MVP within a three months, tops.</p><p><strong>What differentiates this project from other open data efforts?</strong></p><p><strong>Aaron: </strong>From the start, we knew we needed to build more than just another data portal, which typically provide repositories and download links but incite no interest in the data. So the first step was to find military datasets with rich stories that could invite attention — not just post a link. We then needed to provide a place where data scientists, researchers, and visualization experts could start exploring and discussing the data, driving the kind of unexpected but powerful insights and new directions we’ve seen on other successful data initiatives.</p><p><strong>How did you build </strong><a href="https://www.data.mil/"><strong>data.mil</strong></a><strong> and how did you invite collaboration?</strong></p><p><strong>Mary:</strong> DDS and the larger Department of Defense has done a great deal of outreach within the startup and venture capital community. We are always on the look-out for great new software and applications to pilot within the Department. We were lucky enough to partner with two awesome startups in the open data space. <a href="https://www.data.mil/">Data.mil</a> is built using <a href="https://www.livestories.com/">LiveStories</a>, a versatile and easy-to-use storytelling platform that enabled us to craft an engaging narrative and provide context for our data. The second is <a href="https://data.world/datamil">Data.World</a>, a collaboration platform for data scientists. With <a href="https://data.world/datamil">Data.World</a>, we were able to entice researchers and data scientists to put our data to use. We launched our site less than a week ago and already have seen some great <a href="https://data.world/datamil/world-war-ii-thor-data/discuss/world-war-ii-thor-data/5708">collaboration</a> and <a href="https://deptofdefense.github.io/data-mil-THOR-example/">examples</a> of <a href="https://vimeo.com/195152105">visualizations</a> developed by the larger open data community.</p><p><strong>Aaron:</strong> And to help capture interest, we started with a unique dataset from the Air Force, THOR.<strong> </strong>We selected the Theater History of Operations (THOR) database, a compilation of historical bombing data assembled by a small team over years of tedious work, to feature with the launch of <a href="https://www.data.mil/">Data.mil</a>. THOR contains digitized logbooks and punch card data from WWI through Vietnam. We are close to locating the results of a Gulf War bombing survey and hope to feature it soon after approving for public release.</p><p><strong>Mary: </strong>Yes, I think it’s fair to say that open data is not top-of-mind at DoD. In order to get much-needed traction, we needed to launch with interesting datasets that would resonate with both the Defense audience and the general public. “Bombs dropped” data is bound to raise a few eyebrows. We are very interested to see where public discourse takes this data.</p><p>It’s also worth noting, for some of our budget examiners out there, we built this product on a shoestring, for less than ten-thousand dollars. It will be extraordinarily inexpensive to maintain.</p><p><strong>What’s next for </strong><a href="https://www.data.mil/"><strong>Data.mil</strong></a><strong>?</strong></p><p><strong>Mary: </strong><a href="https://www.data.mil/">Data.mil</a> is true to its tagline. It genuinely is “an Experiment in Defense Open Data.” We put the MVP out there and are eager to iterate and partner with DoD data owners to help them open their data and share their stories.</p><p><strong>Aaron:</strong> Like any experiment, we don’t yet know where this could go. Beyond THOR, we’re talking to groups throughout the military on sharing anything from manufacturing and logistics numbers to personnel statistics and research data. If it has potential to help solve military problems through open access and competition, we’d like to put it up on <a href="https://www.data.mil/">Data.mil</a>. And with the help of platforms like <a href="https://data.world/datamil">Data.World</a>, we’ll be able to track the discussion and see how people are using our data. We’ll use this knowledge to guide our next steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/252/1*NsEXx3ZlwMD1TCbHMBpBOQ.png" /></figure><p><em>Mary Lazzeri is a Tech Policy Advisor and Digital Services Expert with the U.S. Digital Service at the White House and the Defense Digital Service.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/252/1*rQhXnGR9602XFIWMn94e-g.png" /></figure><p><em>Major Aaron Capizzi is an acquisitions officer and digital government advocate in the US Air Force.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=259f58bcaafb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-digital-service/data-mil-an-experiment-in-defense-open-data-259f58bcaafb">Data.mil: An Experiment in Defense Open Data</a> was originally published in <a href="https://medium.com/defense-digital-service">Defense Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shifting the Tide: DoD’s new Vulnerability Disclosure Policy]]></title>
            <link>https://medium.com/defense-digital-service/shifting-the-tide-dods-new-vulnerability-disclosure-policy-715ece33fbb7?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/715ece33fbb7</guid>
            <category><![CDATA[security-vulnerabilities]]></category>
            <category><![CDATA[department-of-defense]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[crowdsourcing]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Mon, 28 Nov 2016 22:08:13 GMT</pubDate>
            <atom:updated>2016-11-28T22:08:13.942Z</atom:updated>
            <content:encoded><![CDATA[<h4>How “Hack the Pentagon” follow-up efforts are strengthening and changing the DoD’s security landscape.</h4><p><em>By Lisa Wiswell, Defense Digital Service and Charley Snyder, OSD Policy</em></p><p>Every day at the Department of Defense (DoD), a perpetual conflict takes place between hackers seeking to gain access to our networks and our defenders seeking to keep them out. About a year ago, we began to brainstorm ways to fundamentally shift this dynamic in favor of DoD. Increasingly, major corporations supplement their in-house security talent by engaging with the far larger talent pool of security researchers across the globe — so why couldn’t we?</p><p>We embarked on an effort to engage this community to help spot vulnerabilities in DoD networks before malicious hackers could. Earlier this year, we successfully completed that pilot, called <a href="https://hackerone.com/resources/hack-the-pentagon">Hack the Pentagon</a>, and followed it up with initiatives to make engagement with the security researcher community a permanent part of DoD’s approach to security. Who says government can’t move quickly?</p><p>Hack the Pentagon proved to many in the government that the hacker community could make positive contributions to our security — and that caricatures about dangerous, childish lawbreakers weren’t accurate. The pilot was a huge success — 138 real vulnerabilities were discovered and disclosed to us in three weeks. Hack the Pentagon vividly illustrated that hackers and the government can and <em>should </em>work together. Both sides were conscientious, collaborative, and totally dedicated to ensuring the pilot was a success.</p><p>This spirit of cooperation gave us the proof we needed to make a broader pitch to institutionalize crowdsourced solutions for our security within the Department of Defense and the wider government. In the past few weeks, these pieces have come together for DoD.</p><h3>New Vulnerability Disclosure Policy</h3><p>On November 21, the Secretary of Defense announced a <a href="https://hackerone.com/deptofdefense">Vulnerability Disclosure Policy</a> covering all Department of Defense websites. For the first time, someone who uncovers a security issue on a DoD website will have clear guidance on how to disclose that vulnerability. Even better, the vulnerability disclosure policy will reduce the legal uncertainty that can serve as a chilling effect on Internet security research. That’s one reason why <a href="http://www.defense.gov/News/News-Releases/News-Release-View/Article/1009956/dod-announces-digital-vulnerability-disclosure-policy-and-hack-the-army-kick-off">the Department of Justice</a> is also a fan of this initiative. As the owner of a large percentage of the Internet’s address space, we want to do our part to encourage research into the health of the Internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6eGPbYqAkc5ISFQn." /><figcaption>Submit your vulns at <a href="https://hackerone.com/deptofdefense">https://hackerone.com/deptofdefense</a></figcaption></figure><p>We hope that this policy will yield a steady stream of disclosures, allowing us to find and fix issues faster. The net effect is that the Department of Defense, our Service members, and the public will be safer and more secure. So far, the reception has been fantastic — the same collaborative spirit that made Hack the Pentagon such a success has carried over into this effort.</p><h3><strong>Hack the Army &amp; Future Bug Bounties</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*eZLK2IUMWIC47XstotteGQ.png" /></figure><p>Although the new vulnerability disclosure policy covers all DoD websites, we also want to sponsor focused challenges on specific networks and systems, so we are also bringing bug bounties back! When we announced the vulnerability disclosure policy, we also opened registration for the Hack the Pentagon follow-on, called <a href="https://www.army.mil/article/178473/army_secretary_issues_challenge_with_hack_the_Army_program">Hack the Army</a> announced by Secretary of the Army, Eric Fanning on Veterans Day. This challenge is focused on Army websites that support recruiting, and it is the first of many more bounties to come.</p><p>We contracted with <a href="https://hackerone.com/">HackerOne</a> for large, open challenges like Hack the Army, and we’ve partnered with <a href="https://www.synack.com/">Synack</a> to conduct private challenges against more sensitive assets like internal systems, embedded devices, and source code. This way, we can reap the benefits of crowdsourced vulnerability discovery and disclosure across the full range of DoD technologies, and all DoD Components have the ability to leverage these contracts to host their own bounties.</p><h3><strong>Commitment</strong></h3><p>All of these parts fit together to create a healthier ecosystem for security. We hope to create a feedback loop where hackers are encouraged to point out flaws and receive recognition for their contributions — enhancing the government’s security and cementing the reputation of security researchers as a critical element of Internet security. We believe that these efforts represent a positive example of government adopting best practices from industry and moving an idea from concept to execution fairly rapidly.</p><p>We hope that efforts like this can lead to deeper civic engagement where everyone has the opportunity to directly serve their country to solve shared challenges. Not everyone wants to put on a uniform, fill out a security clearance form, or move to Washington, DC, but Hack the Pentagon showed that people will help their government if they are treated with respect and given an avenue to do so.</p><p>As we move forward with these initiatives, we are committed to making our government more open, innovative, and engaged with private citizens. We’ll continue to listen to feedback as we work to improve, so please let us know how we’re doing and what we can do better!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=715ece33fbb7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-digital-service/shifting-the-tide-dods-new-vulnerability-disclosure-policy-715ece33fbb7">Shifting the Tide: DoD’s new Vulnerability Disclosure Policy</a> was originally published in <a href="https://medium.com/defense-digital-service">Defense Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Team: Brandon • Lori • Nick]]></title>
            <link>https://medium.com/defense-digital-service/meet-the-team-brandon-lori-nick-b9551b9c562f?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9551b9c562f</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[department-of-defense]]></category>
            <category><![CDATA[team-and-culture]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Thu, 18 Aug 2016 12:43:14 GMT</pubDate>
            <atom:updated>2016-08-18T15:50:41.272Z</atom:updated>
            <content:encoded><![CDATA[<p>Get to know some of the amazing faces that work at the Defense Digital Service.</p><p><strong>Brandon Bouier, Software Engineer</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*MqcfPtmVGqBQZDAQr4wLhg.jpeg" /><figcaption>Hanging out in Belize.</figcaption></figure><p>I came to DDS by way of Seattle, driving all the way across the country to work with this awesome group of extremely smart &amp; motivated people. I’ve long worked in government at the local level as The Lead GIS Analyst at the Seattle Police Department, so the opportunity to work on projects that impact the country as a whole was a no-brainer for me. Working at DDS has allowed me to see what happens when passion, execution, &amp; impact converge.</p><p><em>Who is your current role model? </em>Matt Cutts.</p><p><em>Best piece of advice you’ve received? </em>“Great things never came from comfort zones.” — Barry Sanders</p><p><em>It’s a zombie apocalypse: what 3 things do you take?</em></p><ul><li>a sword (to remove heads)</li><li>a shovel (to dispose of heads once removed)</li><li>a buddy with more/better equipment who’s got my back</li></ul><p><strong>Lori Thomas, Software Engineer</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*jXm9pB62rjnUXptfFeiIgg.jpeg" /><figcaption>Rock climbing with friends in The Gunks.</figcaption></figure><p>I’m a software engineer with a background in big data, system archeology and testing. Before joining the US Digital Service, I worked on Flights, Maps and Image Search at Google. My first project at USDS was HealthCare.gov, helping keep the site up through 2016 Open Enrollment. I’ve done several discovery sprints, and am now at the Defense Digital Service, embedded with the contractors building the next generation of GPS.</p><p>It’s been an incredible opportunity to work with brilliant people on things that really matter. I sometimes say that the news my friends post about on Facebook are the projects my coworkers are working on.</p><p><em>Who is your fictional hero? </em>Let’s go with Bujold’s Miles Vorkosigan. He doesn’t let impossible stop him, and makes the people around him excel.</p><p><em>What is your most treasured possession? </em>My cats. Curling up with them and a book is the perfect end to a day.</p><p><em>When are you the happiest? </em>Thanksgiving with friends. It’s a very midwestern display of love in the form of far too much food.</p><p><strong>Nicholas Small, Software Engineer</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*AoJVamhNMwoLjGdFCmS-2w.jpeg" /><figcaption>Staring into the desert heat in Kabul, Afghanistan.</figcaption></figure><p>Before USDS, I led the front end engineering team at Shopify, an e-commerce software company. On the side, I did a lot of extracurricular projects with Open Data and various government organizations, and came to believe that governments have a responsibility to improve the lives of their citizens through technology. Our world is changing and advancing so quickly, there’s no reason that governments and citizen-facing services shouldn’t keep up. So when I heard about US Digital Service for the first time, I said “well, I guess I gotta go do that.” So I blindly moved to Washington DC and joined USDS, not having any idea what I would be working on, but I can confidently say that I am doing the most impactful and important work of my life here.</p><p><em>What is your greatest weakness? </em>Pizza.</p><p><em>It’s Saturday night in DC — where can we find you? </em>Room 11 — the best cocktail bar in DC.</p><p><em>Who is your favorite historical figure? </em>Astronaut Albert II, first monkey in space</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9551b9c562f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-digital-service/meet-the-team-brandon-lori-nick-b9551b9c562f">Meet the Team: Brandon • Lori • Nick</a> was originally published in <a href="https://medium.com/defense-digital-service">Defense Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why did Matt Cutts leave Google for USDS?]]></title>
            <link>https://medium.com/defense-digital-service/why-did-matt-cutts-leave-google-for-usds-d9a0408ef627?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9a0408ef627</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[pentagon]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Wed, 10 Aug 2016 16:05:31 GMT</pubDate>
            <atom:updated>2016-08-10T16:05:31.742Z</atom:updated>
            <content:encoded><![CDATA[<h4>Matt Cutts recently left his 15-year stint at Google as head of the webspam team to join the Defense Digital Service, a USDS agency team at the Pentagon.</h4><p>On August 9, Matt appeared on <a href="https://www.quora.com/session/Matt-Cutts/1?srid=vli&amp;share=66f57c03#!n=40">Quora Sessions</a> to answer questions about his new role. Below is his answer to, “Why did Matt Cutts leave Google for USDS?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*PhMmh2US2ceHGkdnH8rlFA.jpeg" /><figcaption>Answering all your burning questions.</figcaption></figure><p>Matt writes, that “the idea of helping government work better has been on my mind for a while. After Mikey Dickerson and several other folks helped rescue the healthcare website, I heard Mikey talk about how much of an impact just a few people could make. Meanwhile, I saw how Jen Pahlka and others tried to improve government with a group called Code for America (and later Jen served as Deputy Chief Technology Officer with the US government).</p><p>I’ve seen a bunch of smart people like Ed Felten, Amac, DJ Patil, and Megan Smith go help how they can. At a conference in Chicago called ORD Camp earlier this year, I got to meet Paul Smith, who helped with the healthcare rescue and then formed a small company called Ad Hoc that tries to improve things on the contracting side. At conferences, I’d see a lot of people that I respect (hi, Erie Meyer!) who were tackling all kinds of projects.</p><p>So: I’m fundamentally an idealist, and the idea of trying to help appealed to me. A bunch of people that I respect and like were also doing it. My former team at Google was doing well. And I was at a place in my life where I could spend several months in DC. The final nudge came at a conference earlier this year when I had dinner with Haley Van Dyck, an early member of the USDS. After talking to her, the question became: why wouldn’t you do this?</p><p>By the way, I feel like I should add: if it sounds interesting to work with a bunch of smart, get-things-done idealists, the USDS is hiring: <a href="https://www.usds.gov/">https://www.usds.gov/join</a>”</p><p><em>This post originally appeared on a </em><a href="https://www.quora.com/session/Matt-Cutts/1"><em>Quora Session</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9a0408ef627" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-digital-service/why-did-matt-cutts-leave-google-for-usds-d9a0408ef627">Why did Matt Cutts leave Google for USDS?</a> was originally published in <a href="https://medium.com/defense-digital-service">Defense Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking the Pentagon]]></title>
            <link>https://medium.com/the-u-s-digital-service/hacking-the-pentagon-69486aa9f226?source=rss-1aa4e8205e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/69486aa9f226</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[defense]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Defense Digital Service]]></dc:creator>
            <pubDate>Mon, 20 Jun 2016 11:01:02 GMT</pubDate>
            <atom:updated>2016-07-12T15:54:34.531Z</atom:updated>
            <content:encoded><![CDATA[<p>By Lisa Wiswell, Bureaucracy Hacker at the Defense Digital Service</p><p>Though I haven’t done any complex buffer overflows, and I only got through the basics of Haskell, I’m a “hacker” in my own right — hacking Government bureaucracies around our outdated and often restrictive policies so we can get shit done at a pace consistent with the tech sector. That’s my job here in the Defense Digital Service, the DoD’s arm of the White House’s U.S. Digital Service — the government startup the Administration stood up to bring private sector talent and best practices into the federal government to improve critical services.</p><p>For the past seven years, I’ve worked with the Department of Defense to evolve its culture, particularly to interact better with the hacker and security community.</p><p>There was a time when DoD branded even the most professional hackers as criminals. And who can blame them? The OPM hack where Chinese hackers stole sensitive personal information, including social security numbers, of nearly 22 million people from both inside and outside the Government — that was just the icing on the cake. Had we had the ability to open up the OPM systems to professional hackers, who knows, perhaps it could have been prevented.</p><p>But in the last few months, we have made real progress on this front, resulting in a healthier perspective on what hacking is and isn’t. Hackers can help keep the Internet a safer place — by uncovering security weaknesses, and reporting holes that put at risk our most critical systems and data so they can be remediated in near real-time. Leveraging the talent and expertise that hackers bring to security challenge is part of why some of the best tech companies leverage crowdsourced vulnerability discovery and disclosure programs — and why some of us at the Pentagon knew we needed to as well.</p><h4>So, earlier this year, DDS convinced the Department to launch its first ever bug-bounty, “Hack the Pentagon.”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*Gfsg13P20JXS1S2h4FnFxQ.png" /><figcaption>Hack the Pentagon — Pilot Statistics</figcaption></figure><p>And, I’m proud to report today that the pilot greatly exceeded all of our expectations. 1,410 hackers registered. 252 submitted at least one vulnerability report. 1,189 reports were submitted and of those, 138 reports qualified and were paid out. 117 were the total number of hackers that received payouts ranging from $100 to $15,000. And precisely zero registered hackers that intentionally did anything nefarious, or malicious.</p><p>This is a big win. It proved to the skeptics who believed hackers are dangerous, childish, and intentional lawbreakers, that instead, the hackers who participated in Hack the Pentagon were extremely helpful. This has illuminated a positive shift in our attitude toward the hacker community — as strong partners in technology, recognized for their talent and patriotism.</p><p>Lawyers, contracting officers, DoD bureaucrats…we had to hack it all. But we built the concept knowing that what was most important was to provide a new way to let Americans help make us safer at the end of the day. See, the bad guys aren’t waiting around for us to announce a bug bounty, or to win an award…the bad guys are constantly hacking away at our systems looking for our vulnerabilities.</p><p>The Secretary of Defense, Ash Carter, has shown he is committed to finding novel approaches to our most challenging security challenges, rather than just throwing more money, hardware, and software at the problem. That means we need to find legal avenues for private citizens to scan DoD networks, and to provide details to DoD networks owners about found vulnerabilities, best practices, and misconfigurations. Listen, if we’ve got bad ports open, are running old software versions, or have misconfiguration issues, we want you to tell us about it!</p><h4>This will both advance the DoD’s security posture, and continue to extend olive branches to the hacker community, and researchers whose work entails scanning the Internet daily.</h4><p>Over the next several months you’re going to hear about a number DoD initiatives that will engage private citizens, not affiliated with the US Government to help with our most complicated security concerns. First, as part of our commitment to providing a legal avenue for the discovery and disclosure of vulnerabilities for DoD networks, websites, systems, and applications, DoD plans to develop a responsible disclosure policy and process for private citizens to report DoD vulnerabilities without fear of violating laws or regulations.</p><p>Additionally, last week, Secretary Carter announced his plan to launch a persistent DoD Bug Bounty program to continue to allow hackers to be paid to find security flaws in specific DoD websites, applications, binary code, networks, and systems. Rolling out an enduring vulnerability discovery and disclosure program will begin to normalize this as just another tool in our security toolkit — just as industry has done.</p><p>All the challenges taking Hack the Pentagon to market were well worth it. They allowed us to shift our thought that “security through obscurity” is effective, to a position that security must be open, innovative, and engaged with the broader Internet ecosystem. So stay tuned for more exciting news from the Pentagon in the coming months!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69486aa9f226" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-u-s-digital-service/hacking-the-pentagon-69486aa9f226">Hacking the Pentagon</a> was originally published in <a href="https://medium.com/the-u-s-digital-service">U.S. Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>