Here are the three companies selected to design hypersonic missile interceptors for MDA

On the same subject

• 

  September 30, 2020 | International, C4ISR, Security

  The DoD needs data-centric security, and here’s why

  Drew Schnabel The U.S. Department of Defense is set to adopt an initial zero-trust architecture by the end of the calendar year, transitioning from a network-centric to a data-centric modern security model. Zero trust means an organization does not inherently trust any user. Trust must be continually assessed and granted in a granular fashion. This allows defense agencies to create policies that provide secure access for users connecting from any device, in any location. “This paradigm shift from a network-centric to a data-centric security model will affect every arena of our cyber domain, focusing first on how to protect our data and critical resources and then secondarily on our networks,” Vice Adm. Nancy Norton, director of the Defense Information Systems Agency and commander of the Joint Force Headquarters-Department of Defense Information Network, said at a virtual conference in July. How does the Pentagon's AI center plan to give the military a battlefield advantage? The Pentagon's artificial intelligence hub is working on tools to help in joint, all-domain operations as department leaders seek to use data to gain an advantage on the battlefield. Andrew Eversden To understand how the DoD will benefit from this new zero-trust security model, it's important to understand the department's current Joint Information Environment, or JIE, architecture; the initial intent of this model; and why the JIE can't fully protect modern networks, mobile users and advanced threats. Evolving DoD information security The JIE framework was developed to address inefficiencies of siloed architectures. The goal of developing a single security architecture, or SSA, with JIE was to collapse network security boundaries, reduce the department's external attack surface and standardize management operations. This framework helped ensure that defense agencies and mission partners could share information securely while reducing required maintenance and continued infrastructure expenditures. Previously, there were more than 190 agency security stacks located at the base/post/camp/station around the globe. Now, with the JIE architecture, there are just 22 security stacks centrally managed by the Defense Information Systems Agency to provide consistent security for users, regardless of location. “This paradigm shift from a network-centric to a data-centric security model will affect every arena of our cyber domain, focusing first on how to protect our data and critical resources and then secondarily on our networks,” Vice Adm. Nancy Norton, director of the Defense Information Systems Agency and commander of the Joint Force Headquarters-Department of Defense Information Network, said at a virtual conference in July. To understand how the DoD will benefit from this new zero-trust security model, it's important to understand the department's current Joint Information Environment, or JIE, architecture; the initial intent of this model; and why the JIE can't fully protect modern networks, mobile users and advanced threats. Evolving DoD information security The JIE framework was developed to address inefficiencies of siloed architectures. The goal of developing a single security architecture, or SSA, with JIE was to collapse network security boundaries, reduce the department's external attack surface and standardize management operations. This framework helped ensure that defense agencies and mission partners could share information securely while reducing required maintenance and continued infrastructure expenditures. Previously, there were more than 190 agency security stacks located at the base/post/camp/station around the globe. Now, with the JIE architecture, there are just 22 security stacks centrally managed by the Defense Information Systems Agency to provide consistent security for users, regardless of location. Initially, the JIE was an innovative concept that took the DoD from a highly fragmented architecture, in which each agency managed its own cybersecurity strategy, to an architecture in which there is a unified SSA. However, one of the early challenges identified for the JIE was managing cloud cybersecurity as part of the SSA. The components in the JIE — the Joint Regional Security Stacks family's internet access points and cloud access points — have traditionally focused on securing the network, rather than the data or user. As more DoD employees and contractors work remotely and data volumes increase, hardware cannot scale to support them. This has created ongoing concerns with performance, reliability, latency and cost. A cloud-first approach In response, the DoD leverages authorized solutions from the Federal Risk and Authorization Management Program, and it references the Secure Cloud Computing Architecture guidance for a standard approach for boundary and application-level security for impact Level 4 and 5 data hosted in commercial cloud environments. The purpose of the SCCA is to provide a barrier of protection between the DoD Information Services Network and the commercial cloud services that the DoD uses while optimizing the cost-performance trade in cybersecurity. Defense agencies are now exploring enterprise-IT-as-a-service options to move to cloud, and reduce the need for constant updates and management of hardware. Through enterprise-IT-as-a-service models, defense agencies will be able to scale easily, reduce management costs and achieve a more competitive edge over their adversaries. Before the pandemic hit, defense agencies were already moving to support a more mobile workforce, where employees can access data from anywhere on any device. However, a cyber-centric military requires security to be more deeply ingrained into employee culture rather than physical protection of the perimeter. The next evolution to secure DISA and DoD networks is to embrace a secure access edge model with zero-trust capabilities. The SASE model moves essential security functions — such as web gateway firewalls, zero-trust capabilities, data loss prevention and secure network connectivity — all to the cloud. Then, federal employees have direct access to the cloud, while security is pushed as close to the user/data/device as possible. SP 800-27, zero-trust guidance from the National Institute of Standards and Technology, provides a road map to migrate and deploy zero trust across the enterprise environment. This guidance outlines the necessary tenants of zero trust, including securing all communication regardless of network location, and granting access on a per-session basis. This creates a least-privilege-access model to ensure the right person, device and service have access to the data they need while protecting high-value assets. As the DoD transforms the JIE architecture to an as-a-service model with zero-trust capabilities, defense agencies will experience cost savings, greater scalability, better performance for the end user and war fighter, improved visibility, and control across DoD networks — and ultimately a stronger and more holistic cybersecurity capability moving forward. https://www.c4isrnet.com/opinion/2020/09/29/the-dod-needs-data-centric-security-and-heres-why/

• 

  May 28, 2020 | International, C4ISR, Security

  Joint AI Center Turns To Air Force cloudONE As JEDI Stalls

  The Joint Artificial Intelligence Center needs three things: new acquisition authorities, more staff, and the cloud. With JEDI delayed ‘potentially many more months,' director Lt. Gen. Jack Shanahan said, he's turning to an Air Force alternative. By SYDNEY J. FREEDBERG JR.on May 27, 2020 at 2:25 PM WASHINGTON: The legal battle over the JEDI cloud-computing contract has slowed down the Pentagon's AI program, the director of the Joint Artificial Intelligence Center acknowledges. In the meantime, Lt. Gen. Jack Shanahan told an AFCEA webcast last week, JAIC will turn to a new Air Force program our longtime readers are already familiar with: cloudONE. Cloud computing matters for AI because machine-learning algorithms need lots of data and lots of processing power. A shared cloud can offer both with far greater efficiencies of scale than any single organization's in-house network. JEDI was meant to provide a single “general purpose” cloud to all users across the Defense Department, including Shanahan's Joint AI Center. But it has been mired for months in legal battles over which company should have won the contract, Microsoft Azure or Amazon Web Services. “It slowed us down, no question about it,” Shanahan told the AFCEA audience. “Azure, AWS, I will never get into a company discussion. I'm agnostic,” he said. “[But] if we want to make worldwide updates to all these algorithms in the space of minutes, not in the space of months running around gold disks, we've got to have an enterprise cloud solution.” JEDI can't be that solution today, Shanahan acknowledged, but “we now have a good plan to account for the fact that it will be delayed potentially many more months.” For instance, as the COVID-19 pandemic spread, the Joint AI Center urgently stood up what they call Project Salus – named for the Roman goddess of health and safety – to pull data from 70 different sources, find patterns, and predict trends for US Northern Command and the National Guard. Salus went from a sketch on a “bar napkin” to a functional bare-bones system (what's called a Minimum Viable Product) in 29 days, Shanahan said. With JEDI unavailable, he turned to an existing Air Force cloud run out of Hanscom Air Force Base, which he'd previously used as head of Project Maven. But the Hanscom-based cloud is “an interim solution that will end ... here later in the fall,” Shanahan said. “Because of that, we are pivoting to the cloudONE environment.” CloudONE & Beyond So what's cloudONE? Like JEDI, it's a new cloud-computing capability that the Air Force hopes will be available to a wide range of users from across the Department of Defense. Unlike JEDI, it's not a joint program run by the Office of the Secretary of Defense, but a service program, run by the Air Force. In fact, cloudOne is part of a whole package of computing initiatives – deviceONE, dataONE, et al – that the Air Force acquisition chief, Will Roper, began pushing (and branding) aggressively last year. Further, while JEDI is meant as the Defense Department's “general purpose” cloud, Roper's many ONEs are all intended to serve a single purpose, albeit a broad one: military command and control. Together, Roper's projects will make up what the Air Force is calling its Advanced Battle Management System. ABMS, in turn, will be an Air Force component of the future Joint All-Domain Command and Control (JADC2) meta-network to share battle data between all the armed services across all five “domains” of warfare: land, sea, air, space, and cyberspace. Artificial intelligence is essential for JADC2, since human analysts can't pull together that much data from that many sources fast enough to make a difference in combat. The JAIC is far too small to build the whole JADC2 network – that's up to the far better-resourced services – but it can help. “We're not here to build JADC2,” he said. “We're here to find AI-enabled solutions that stitch seams together from all the services, who're [each] developing some version of JADC2.” The objective is to automate and accelerate the often-laborious process of bringing American firepower to bear. That “kill chain” includes everything from spotting a potential target with some kind of sensor, confirming what it is with other sensors, deciding to strike it, picking an aircraft, warship, or artillery battery to execute the strike, and then giving that shooter precise targeting data. Currently most of that requires human beings relaying coordinates and orders over the radio, typing them into terminals by hand, or even scrawling them on sticky notes because one network can't transfer data to another. “Accelerated sensor-to-shooter timelines are so important – to me, this is what the next couple of years will be about, and each of the services has a really strong programs in sensor-to-shooter,” Shanahan said. “What we're trying to bring is the AI/ML solutions.” To do that job, however, the JAIC needs more people and more legal authorities to conduct acquisitions on its own – although it will never be the size of the services' acquisition bureaucracies. For example, while Shanahan initially focused on lower-risk, non-combat applications of AI like maintenance, on May 18 the JAIC awarded Booz Allen Hamilton a landmark contract worth up to $800 million for AI “to support warfighting operations [and] decision-making and analysis at all tiers of DoD operations.” But JAIC did so in partnership with the civilian General Services Administration (using GSA's Alliant 2 contract vehicle), just as it's done past contracts through the Defense Information Systems Agency and other established organizations, because it doesn't have the necessary authorities and personnel in-house – yet. “I couldn't ask for better support,” Shanahan said, “but it's not going to be fast enough as we start putting more and more money into this capability development. We need our own acquisition authority.” In particular, he sees JAIC as a potential early adopter of the new streamlined process for software development and acquisition recently rolled out by the Pentagon's acquisition chief, Ellen Lord. The JAIC also needs to get bigger. Founded in summer 2018 with just four staff, JAIC has now grown to 175 personnel (counting contractors) and must keep growing, Shanahan said. But that larger staff won't include Shanahan: JAIC's founding director retires from the Air Force next month. https://breakingdefense.com/2020/05/joint-ai-center-turns-to-air-force-cloudone-as-jedi-stalls/

• 

  October 16, 2020 | International, Land

  Soldiers to evaluate new light tank prototypes

  Jen Judson WASHINGTON — The U.S. Army is preparing a soldier vehicle assessment of two different light tank prototypes for infantry brigade combat teams that will start in January 2021 at Fort Bragg, North Carolina. The assessment will run through June 2021, according to the service. BAE Systems and General Dynamics Land Systems were chosen in December 2018 to each build 12 prototypes of the Army's future mobile protected firepower, or MPF, vehicle identified in the service's ground combat vehicle strategy published in 2015. The service had found the capability one the service lacks. GDLS is building a vehicle that takes the United Kingdom's AJAX chassis and combines it with an M1 Abrams tank turret. BAE Systems' design is an updated M8 Buford armored gun system with new capabilities and components. “I just had my deep dive today on the SVA [soldier vehicle assessment] with the 82nd [Airborne],” Maj. Gen. Brian Cummings, the Army's program executive officer for ground combat systems, told Defense News in a recent interview. Work is ongoing to prepare ranges and roads for the arrival of the prototypes, he said. The MPF is going to be critical for the infantry because it provides infantry brigade combat teams with an organic capability to take care of impediments to forward progression such as gunfire from a machine gun nest or another enemy vehicle. The Army is expected to choose a winner in 2022. The first units will get MPF in fiscal 2025. The Army plans to initially build 26 vehicles, with an option to build 28 more and retrofit eight prototypes. GDLS told Defense News in an interview ahead of the Association of the U.S. Army's annual conference that it has delivered three vehicles to the Army. One is at Aberdeen Proving Ground, Maryland, going through characterization and mobility testing and preparing for firing. Another is at Yuma Proving Grounds, Arizona, undergoing desert testing and preparing for soldier training. Five more prototypes are in “some form of checkout, getting ready for their final inspection report to deliver to the government,” a GDLS spokesperson said, and the company is on track to deliver all of the vehicles this year. BAE is looking forward to the assessment because the two prototypes are so different from one another, said Jim Miller, the company's senior business development director for combat vehicles. The BAE's offering is smaller — fitting in between the Joint Light Tactical Vehicle and a Stryker in terms of size — while GDLS' vehicle is bigger, as it's based on the M1 Abrams chassis. The BAE's MPF prototype can be transported via a C-130 aircraft. Three can fit on a C-17 aircraft. And even though it is small, it has the survivability of BAE's Armored Multipurpose Vehicle, Miller said. The Army is requiring the vehicle be C-17 transportable. Soldier assessments for other recent competitions have weighed heavily into decisions, Miller added. “I think the soldier vehicle assessment is going to be really important,” he said. “Did we get this right? Now which one is closer to the mark?” https://www.defensenews.com/digital-show-dailies/ausa/2020/10/15/soldiers-to-evaluate-new-light-tank-prototypes/