Air Force software platform expansion stalled by cybersecurity concerns
Efforts to expand the Air Force’s software development environment, Platform One, have stalled after some senior military IT leaders raised cybersecurity concerns about the platform, FedScoop has learned.
The concerns center on officials’ understanding of the architecture, policies of the environment and a perceived lack of security documentation. Some officials have tried to outright ban the use of code stored in one of its repositories, and reciprocity talks with other services have been held up over differences of the risk levels each is willing to take, multiple sources with knowledge of the matter told FedScoop.
Platform One’s success, and replication across the military, could have huge impacts for developers that need a secure method of coding to have their products cleared by DOD authorizing officials. But to achieve widespread use, officials across multiple services need to sign off on its use, and reciprocity with similar coding environments needs to be negotiated among the services.
Platform One is one of the Air Force’s main offices for digital innovation. The service is focused on navigating around Department of Defense bureaucracy to build tech that it says is more secure than DOD’s current risk-averse processes. The office’s core tech runs on Google’s Kubernetes, an open-source system for securely storing code in containers. It has been touted by its leaders as a key enabler in the DOD’s push to make itself a digital organization by leveraging what’s called DevSecOps — a technical and cultural approach to writing code that integrates security at every level of development.

“As pioneers, all of these programs broke glass and were met by many with celebration and by some with hesitancy,” Lauren Knausenberger, the Air Force’s CIO, said in a statement provided to FedScoop. She added: “We’re doing our best to educate folks on new technologies and processes and use their experience to help continuously adapt.”
Instead of following the DOD’s de facto process for software authorization, Platform One was able to get its process cleared so that new code authorization is automated, essentially accrediting a recipe rather than testing each batch.
DOD’s process for software authorization forces developers to submit code to a months-long checklist-based approval process each time they want to make an update. Some IT officials say this can leave software systems vulnerable to breaches because they are forced to remain stagnant while updates are checked.
By focusing on the processes of writing code, advocates for Platform One say it is more secure, quicker and in line with commercial best practices.
“Platform One prioritizes cybersecurity over compliance checks. Do people want to be secure or do people want to be compliant? Both take work, and some prioritize one over the other,” Rob Slaughter, Platform One’s former director, told FedScoop.
But despite Platform One’s perceived improved security processes, officials that want to use it say they have concerns.
The problem for some, Slaughter said, is: “They [Platform One] just don’t have the homework in the right format.”
Speaking to FedScoop, former DOD CISO Jack Wilmer said the individual issues raised by officials were not outright dangerous on their own, but demonstrated that without a way for services to have a common understanding of mitigating cyber risk, it’s difficult to achieve reciprocity.
Several officials who have asked for Platform One’s security documentation said they were not provided with any, creating mistrust in the system. Officials who had discussed using Platform One or were familiar with its practices told FedScoop they felt the patching process was too ad-hoc for their comfort and authorization for new containers was too centralized.
Officials also had acute concerns around one of Platform One’s Iron Bank product, which stores open-source code in containers. The issues with Iron Bank center around a perceived lack of verification of who is contributing and a lack of a legal framework for issuing patches for code stored on the system.
Some of the concerns about the patching process and software supply chain for Iron Bank were brought to the attention of the DOD CIO’s office during a meeting about expanding the use of Iron Bank, according to two officials familiar with the meeting.
Emails reviewed by FedScoop indicate that officials have “a desire for more transparency and input into the vetting process” of containers in Iron Bank.
Danielle Metz, deputy CIO for information enterprise who chaired the meeting, said such meetings are regular occurrences to help develop Iron Bank’s tech.
“The implementation of software containers is a rapidly growing but still relatively nascent field for the DoD. The Air Force’s Iron Bank has been at the forefront of identifying secure and repeatable processes for software development and insertion into Platform One and other programs throughout the DoD,” she said in a statement to FedScoop.
Knausenberger heralded the role of Platform One in breaking new tech barriers in DOD and told FedScoop that many of the concerns come down to a misunderstanding of the new tech.
“These programs all do things differently,” she said.
The Navy is working on its own DevSecOps platform similar to Platform One called Black Pearl. Officials in the Navy and Air Force have been negotiating a reciprocity agreement to avoid the Navy re-doing work already accomplished by Platform One. But talks stalled over technical details concerning the way Platform One accepted risk and how it stored documentation about its security practices, officials said.
A Navy spokesperson told FedScoop in a statement that it is “strongly engaged” in platform collaboration and that it’s working to ensure the cybersecurity practices “are transparent and repeatable to maximize reciprocity.”
“The Department of the Navy and our partners are committed to seeing that work through,” the spokesperson said.
Navy officials had requested documentation through the Enterprise Mission Assurance Support Service (eMASS), an application that stores security packages. Since Platform One doesn’t follow the traditional compliance processes, it says its documentation is not in the format that is supported by eMASS. Instead the team “[automates] the vast majority of their security controls and checks, and store their real-time docs in their GIT repositories,” Knausenberger said.
“It still sometimes freaks out the security assessors because they are not used to finding real-time documents in a code repo,” she said.
Knausenberger added that Platform One sometimes attracts criticism because it regularly works with cybersecurity red teams — white hat hackers tasked with playing the role of the adversary — and. because the teams are good at what they do, they occasionally identify vulnerabilities.
“Each time they do, these teams take it very seriously, they learn from the findings, and they make fixes very quickly. Compare that to legacy programs that submitted a checklist at a point in time and may not know what issues are there now, or may not be able to fix them quickly. While change can make people uneasy this is the type of change we need to win,” Knausenberger said.
How the Army is getting ready for the next Project Convergence tests
To make one of the biggest changes to the use of its networks in decades, the Army is turning to tech to improve its testing.
Project Convergence, the Army’s contribution to Joint All Domain Command and Control (JADC2), is going to get its second major test this November. But before then, it needs to stress-test its tactical network to see if it’s ready to try and achieve interoperability with other services.
To prep for this, the Army has been conducting a range of virtual network tests to ensure that its systems can handle a project centered on increasing the amount of battlefield data used to make decisions.
“As a former signal officer, the last thing you want to find out is your system doesn’t work because of improper grounding or configuration that you could have dealt with in the lab or in some sort of hybrid environment,” said Maj. Kristen Pietrasz, an acquisition officer for the Army’s Command, Control, Communications, Computers, Cyber, Intelligence, Surveillance, Reconnaissance (C5ISR) Center.
JADC2 is the military’s new framework of building a connected battlefield where data from sensors across all domains can give commanders deeper insights into a battle. The Army’s response to the call to connect everything is Project Convergence, which focuses on connecting sensors that will improve targeting speed and accuracy.
In the fall of 2020, the Army assembled a team of coders, senior leaders and others in the desert of Yuma Proving Ground, Ariz., to conduct its first major test event. One of its lessons learned: networks need to be prepped in air-conditioned rooms, not in the dessert in late summer.
To help modernize its tactical network through virtual testing, the Army built the Joint Systems Integration Laboratory (JSIL) at Aberdeen Proving Ground (APG), Md. The JSIL digitally connects Army and other service labs in a virtual environment that the Army says reflects the conditions of JADC2.
“This, in turn, creates efficiency by enabling the services to address network challenges that would otherwise take up precious testing time during PC21,” the Army stated in a release.
The lab hosted two fully virtual tests already and recently conducted its first mixed virtual-live test event dubbed “communications exercises (COMMEX) 2.x.” The new type of mixed test connected to labs run by the Navy, Air Force and Marine Corps as well as “dismounted systems,” or platforms being operated in the air and in field exercises.
“In ten days, we achieved the same results that we would have if we had spent six weeks in the desert,” said Kim Moeltner, chief for the C5ISR Center’s Systems Engineering and Integration Branch.
By connecting with other services, the Army is already working toward achieving one of the major goals of Project Convergence 21 — linking other services to its system. One of the key goals of JADC2 is to achieve interoperability between the services, a milestone that would overcome both technical and cultural hurdles. Future Project Convergence tests will also include experiments involving allied and partnered militaries.
The next two COMMEXs will be more physical than virtual, taking place once again at Yuma Proving Ground to build and test air-to-ground mesh networks, not just the tactical network already in place.
“This has been instrumental because it allowed us to overlay laboratory experiments at the same time we were doing field experiments. We’ve done the laboratory piece, we’ve done the field piece, and this was new for us to be able to layer all three at the same time at speed, at scale and at range,” said Col. Tobin Magsig, commander of the U.S. Army Joint Modernization Command.
50% transition to EIS target remains elusive for agencies
Less than a quarter of agencies have completed 50% of their transition to the $50 billion Enterprise Infrastructure Solutions (EIS) contract intended to modernize their telecommunications and IT, despite the deadline for that target being March 31.
A total of 50 agencies — including 12 of the 24 Chief Financial Officers Act agencies — have achieved the 50% mark, according to the General Services Administration‘s monthly EIS Transition Progress Tracking Report dashboard for August.
Still more than 200 agencies have transition inventory and billing under the expiring Networx, Washington Interagency Telecommunications System (WITS) 3 and GSA Regional Local Service (RLS) contracts. Those contracts sunset on May 31, 2023, eight months after all agencies’ telecom inventory must be moved to EIS.
All the while, the EIS program has seen some shakeups of late.
Jim Russo, branch chief of the Solutions Development at GSA, retired from that role last month. He led a team of network and wireless engineering professionals working on the EIS program and had a hand in making secure telecom and network services like multi-protocol label switching, ethernet, Internet Protocol voice, managed network services, and cybersecurity offerings available through the contract.
Also last month Comcast announced a deal to acquire Defined Technologies, a subsidiary of MicroTech. GSA awarded MicroTech its EIS prime contractor status in 2017, but the company transferred the contract to Defined Technologies in November — meaning Comcast is poised to take over that business once the deal is closed.
While it’s a bit early to tell what the two developments could mean for agencies’ EIS progress, most have awarded their task orders.
GSA’s target for awarding all EIS task orders was Sept. 30, 2019, and currently, 142, or 68.3%, of all expected ones have been.
Among CFO Act agencies, only six have task orders outstanding.
None of the departments of Agriculture and Housing and Urban Development or the Environmental Protection Agency have begun awarding their single EIS task orders. Similarly, the Department of Energy hasn’t started the process for awarding the two task orders it has planned.
Meanwhile, the Department of Justice has awarded one of its two task orders, and the Department of Homeland Security has awarded only three of its 14 outstanding task orders.
Some agencies have completed their transitions to EIS: two medium and 32 small ones. The medium agencies are the Executive Office of the President and the Federal Deposit Insurance Corp.
DIU adds new venture funding pool for defense tech startups
The Defense Innovation Unit has added a new source of venture funding for defense tech startups to its ecosystem of innovation tools.
The National Security Innovation Capital (NSIC) is a program that aims to provide funding to hardware startups building tech that could be useful to the government. It will search for companies that need extra funding to get off the ground and make investments, a move that hopefully will inspire private sector groups to also add cashflow to the selected companies.
NSIC will provide a new avenue of funding for defense technology startups seeking to work with the Department of Defense. Currently, DIU mostly uses other transaction authority agreements to match companies with funding.
The new funding pool will support so-called “dual-use” startups, which provide technology that can both be deployed by the military and also in wider commercial industry.
“NSIC is an important new effort in expanding public-private partnerships to strengthen the national security innovation base,” said the team’s director, Tex Schenkkan.
The team will focus on hardware companies, which make up roughly 30% of the market of venture-backed startups. Many companies need to turn to foreign investment to get off the ground, a move that could disqualify them from future work with the government or even leave them open to IP theft.
“NSIC is an important part of accelerating emerging commercial technology into the DoD,” said Michael Brown, DIU Director. “Funding innovative dual-use technology to improve national security is critical in our nation’s strategic competition with China and providing the best technology for our military.”
The idea for the NSIC was first floated by Brown in a paper he wrote on China while serving as a presidential innovation fellow. China has been accused of funneling money, or “adversarial capital” to startups to block their future work with the U.S. government.
The effort is trying to solve a similar problem similar to one launched by acquisition and sustinament, called the Trusted Capital Digital Marketplace. That effort doesn’t provide any government money to startup. Instead, it vets “trusted” capital providers and connects them to startups eager to one-day work with the government.
“Our efforts are complementary but very different. NSIC’s support will be predicated on ensuring that a recipient company’s existing funding comes from trusted sources,” Schenkkan told FedScoop in a statement. “A condition of NSIC support will be company commitment not to accept future funding from adversarial sources.”
Technologist Waldo Jaquith joins GSA as senior adviser to Carnahan
Veteran public sector technologist Waldo Jaquith has joined the General Services Administration as a senior adviser to Administrator Robin Carnahan.
He takes up the post at the agency after previously holding a fellowship at the Beeck Center for Social Impact and Innovation at Georgetown University.
Prior to her appointment as GSA administrator, Carnahan also held a fellowship at the Beeck Center, where she worked with Jaquith to launch the State Software Collaborative — a practical research project designed to overhaul states’ reliance on over-complex procurements and off-the-shelf software. They also spent time together previously at GSA’s in-house tech consultancy 18F between 2016 and 2020.
Previously, Jaquith was a member of the Biden-Harris transition team, working on technology strategy and delivery, and was also a volunteer at U.S. Digital Service. Earlier in his career, he also worked at the Sunlight Foundation.
Between 2012 and 2014, he was a member of the Open Data Working Group at the White House, according to his LinkedIn.
In a note on Twitter announcing the appointment, Jaquith said that in the new post he would continue a lot of the work he undertook with Carnahan for years at 18F and then at the State Software Collaborative.
In a statement, GSA said that in the new role Jaquith will coordinate the agency’s efforts to support state, local, tribal and territorial initiatives.
OPM pushes for IT modernization working capital fund
The Office of Personnel Management says it supports the idea of starting a working capital fund to finance its backlog of necessary IT modernization projects if given congressional approval.
To jumpstart its modernization efforts, OPM needs more funding from Congress and authorized flexibilities to support such multi-year projects in the form of a working capital fund, senior agency leaders commented Monday in response to a recent National Academy of Public Administration study on a possible OPM reorganization.
NAPA recommended in its congressionally mandated March report that OPM focus on glaring IT inadequacies, while also concluding that OPM should remain an independent agency and not be folded into the General Services Administration, as proposed by the Trump administration. OPM is building NAPA’s recommendations into its fiscal 2022-2026 four-year strategic plan, it says in the response.
“OPM is committed to the policy changes and investments necessary to strengthen OPM’s role as the strategic human capital leader for the Federal Government,” OPM Director Kiran Ahuja wrote in her opening to the comments.
In its report, NAPA called on OPM to “modernize the [electronic Official Personnel Folder platform] and develop an employee digital record, upgrade technology systems supporting the federal retirement programs, enable a modern human capital data and analytics platform, and transform its website to be both user-centric and user-friendly.”
OPM said that not only will it “prioritize IT modernization and seek funding from Congress” for those stated projects — calling it a “top agency requirement” that requires “substantial resources to fully implement” — but it will also look to Congress for “dedicated funding to be used for specific, major OPM IT modernization projects” and the authority to establish a working capital fund. Both of those efforts, OPM says, are contingent on developing a roadmap for IT spending and “the completion of an enterprise-wide IT requirements and cost analysis to enable a more flexible and accountable internal process for funding IT operations and maintenance.”
In addition, OPM said it will look to the governmentwide Technology Modernization Fund to support its modernization efforts as well.
OPM also outlined other strategies to modernize IT systems, including improving governance, upskilling the workforce, evaluating systems for risk, expanding use of cloud technology and improving its collection and stewardship of federal personnel data.
The Modernizing Government Technology Act of 2017, which created the TMF, called for agencies to institute their own IT working capital funds, but few have done so since then, largely because of a lack of congressional authorization or hangups with their CFO colleagues or appropriators.
Civil rights organizations want nondiscrimination steps laid out in NIST’s AI guidance
A group of civil rights, tech and other advocacy organizations called for the National Institute of Standards and Technology to recommend steps needed to ensure nondiscriminatory and equitable outcomes for all users of artificial intelligence systems in the final draft of its Proposal for Identifying and Managing Bias with AI.
The definition of model risk — traditionally thought of as the risk of financial loss when inaccurate AI models are used — should be expanded to include the risk of discriminatory and inequitable outcomes, wrote the group in its Friday response to NIST’s draft proposal.
NIST released the proposal for public comment on June 22 with the goal of helping AI designers and deployers mitigate social biases throughout the development lifecycle. But the letter from 34 organizations — including the NAACP, Southern Poverty Law Center and mostly those in the housing and consumer credit space — makes 12 recommendations for improvements to NIST’s proposal and process.
“It is critically important for NIST to propose a framework that ensures that AI risk analysis works hand in hand with discrimination risk analysis. Moreover, efforts to identify AI risks must not exclude or undermine efforts to promote fair and equitable outcomes,” said Michael Akinwumi, chief tech equity officer at the National Fair Housing Alliance, in a statement. “Any new AI-related initiatives should be reviewed for potentially illegal discriminatory treatment or effect for communities of color and other underserved communities.”
Other proposal enhancements the group suggests include issuing actionable policy statements committing to consumer protection and civil rights laws and outlining expectations and best practices, as well as encourage AI developers to use a diverse workforce.
They are also calling on NIST to recommend regular civil rights and equity training to help personnel catch red flags and to ensure that AI providers are transparent about AI systems and their impact.
On the process side, the group called for NIST to issue a detailed action plan and engage with civil rights activists, consumer advocates and impacted communities.
NIST’s own staff should include people specializing in civil rights to assist agencies and organizations in assessing the potential discriminatory impact of their systems. Staffers working on AI issues should be diverse, according to the letter.
The group further recommended NIST share its methods, data, models, decisions and solutions openly.
Public research analyzing AI use cases and their impact on people and communities of color and other protected classes should be supported by NIST, the letter concludes.
Automation holds the key to faster benefits delivery and reduced fraud
Agencies may want to establish a national strategy for contact-tracing apps
Congress and federal agencies should consider establishing a national strategy for the development and deployment of contact-tracing applications ahead of future pandemics, according to a Government Accountability Office study released Thursday.
Exposure notification apps alert users if they were near a person who later tested positive for a disease like COVID-19, allowing for faster, broader contact tracing to slow the spread.
The absence of a national contact-tracing app led 26 states, territories and Washington, D.C. to seek out their own in a staggered fashion beginning in August 2020. Costs could reach as high as $700,000 and downloads range from 200,000 to 2 million from state to state.
“Policymakers could recommend a national app that public health authorities could decide to use based on their individual needs,” reads GAO‘s report. “A national app could add more functions by integrating exposure notification capabilities with test scheduling and vaccine delivery coordination.”
Current apps have a number of issues like the accuracy of their distance and exposure measurements, which can lead to inaccurate alerts.
A lack of independent privacy and security assessments, as well as federal legal protections, is a deterrent for potential users, and some states have struggled to encourage adoption.
There’s also the problem of a lack of data to evaluate how effective exposure notification apps actually are. The Department of Homeland Security Science and Technology Directorate‘s Silicon Valley Innovation Program currently has two projects developing app criteria, but they’re two years away from completion.
While GAO made no formal recommendations, it did suggest Congress and federal agencies promote research and development to address contact-tracing apps’ technical limitations. The Centers for Disease Control and Prevention, DHS, National Institutes of Health, and National Institute of Standards and Technology have assisted state development with guidance and funding, but additional resources and public-private partnerships are needed to create apps that will work beyond the COVID-19 pandemic for other diseases.
So far the CDC has funded app development in 64 jurisdictions through its Epidemiology and Laboratory Capacity for Prevention and Control of Emerging Infectious Diseases cooperative agreement, as well as research at the Massachusetts Institute of Technology’s Lincoln Laboratory into barriers to adoption and efficacy.
GAO also suggested the federal government consider standardizing app privacy and security practices. NIST started a study in early 2020 to develop exposure notification systems with strong privacy and cybersecurity controls.
Lastly GAO suggested the government promote best practices for app adoption and measurement.
The CDC issued guidance on the minimum and preferred characteristics of digital contact-tracing tools in May and December of 2020. Contact notification, data security and exposure risk level requirements were included, but some states had issues with app verification codes.
“States faced challenges in promptly providing people who tested positive for COVID-19 with a verification code necessary to notify other close contacts of potential exposure using the app,” reads the report.
IT Insights: Interview with AWS’s U.S. government VP Dave Levy on innovation in the public sector
Public sector organizations — from federal, state and local governments to nonprofits and healthcare businesses — are increasingly reaching out to leaders at Amazon asking, “How does Amazon innovate?”
It’s not just because Amazon has established itself as a model for innovation, says Dave Levy, who leads the U.S. government, nonprofit and healthcare businesses at Amazon Web Services (AWS). It’s also because AWS is working with so many public sector organizations to help them innovate, as well.
In this exclusive FedScoop interview, Levy talks about what helps propel innovation at AWS; how AWS has helped federal agencies innovate; and how the cloud is poised to accelerate innovation in the future:
FedScoop: How would you describe the underlying drivers that continue to fuel innovation at Amazon Web Services?
FedScoop: Can you point to examples of how AWS has helped federal agencies apply these principles in their own efforts to better serve citizens?
FedScoop: Looking longer term, what should federal agencies expect to see from AWS that can help them accelerate their adoption of cloud-enabled services?
Learn how AWS can help your agency capitalize on today’s cloud or contact us at AWS Public Sector.
This video interview was produced by FedScoop and underwritten by AWS.