Nov 6, 2020

One Network Enterprises: The US$43mn Naval Contract

Technology
Supply Chain Management
Supplier Management
SCM
Oliver Freeman
4 min
US Navy Jets
The United States Navy has awarded One Network Enterprises a large contract for their company’s leading autonomous supply chain solution...

One Network Enterprises: The US$43mn Naval Contract

The United States Navy has awarded One Network Enterprises a large contract for their company’s leading autonomous supply chain solution.

One Network Enterprises, a global provider of multi-party business networks for autonomous supply chain management, today announced that it had been awarded a US$42.6 million contract by the Army Contracting Command on behalf of the United States Navy for the Naval Operational Business Logistics Enterprise (NOBLE) Naval Operational Supply System (NOSS) to begin modernisation of the entire operational supply chain. The award is the result of a competitive Other Transactional Authority (OTA) acquisition process.

Supporting the Navy End-to-End

The Naval Operational Supply System is an end-to-end Supply Chain Management (SCM) solution that supports Naval Operational Forces to include Maritime, Aviation, Expeditionary and Shore Support Units. The NOSS solution is a modernisation effort to replace legacy applications and systems, provide a standardised and scalable solution for use across the entire enterprise and consolidate all functional capabilities into an integrated solution. It includes supply, financial and property management capability for all material. NOSS will be the DoD's first material-agnostic SCM solution.

Traditionally, the DoD services have relied on multiple systems within their supply chain, with one or more systems managing a single commodity item. NOSS will manage and support all commodity types for the U.S. Navy through one global federated system. These commodities include munitions, parts and repairables, medical supplies, Petroleum, Oils and Lubricants (POL), food and food preparation, hazardous material, retail and all other items that the Navy needs to support their mission-critical operations. One Network will bring both its commercial experience and defence capabilities to the Navy to modernise around repeatable business processes across all commodity types.

Faith in an Industry-Leading Provider

"The confidence that the Navy has entrusted to One Network is another proof point regarding the capabilities of our multi-party network platform," said David Stephens, Executive Vice President and General Manager of Government Programs, One Network Enterprises. "The Navy will benefit from a modernised global platform that will never go legacy, supporting both ashore and afloat capabilities. In addition, One Network's federated platform-to-platform integration enables the Navy with a Delayed/Disconnected, Intermittently Connected, Low Bandwidth Environment (typically referred to as D-DIL), which is ideal for deployed operations afloat. We look forward to providing a truly global and mobile One Network solution operating on all Navy ships and submarines with access from every shore-based location while working in both unclassified and classified environments."

The effort also includes all tasks necessary to support a Limited Deployment (LD) of the NOSS solution. The LD solution requires the implementation of functional requirements needed to deploy the modernised solution in a production environment. The requirements include product definition analysis, commercial off-the-shelf configuration and associated development, testing, and integration in support of identified Limited Deployment sites.

Not the First, Not the Last

In addition to this award by the U.S. Navy, last month the United States Air Force (USAF) awarded a US$62M contract to One Network Enterprises for its Item Master Logistics Capability Initiative (IMLCI). One Network will help the USAF configure and model new Master Data Management business processes to support its portfolio of logistics initiatives worldwide.

“We are proud to be selected by the USAF for this important work in further improving mission readiness and supporting the warfighter,” said David Stephens, Executive Vice President and General Manager of Government Programs, One Network Enterprises. “Both One Network and Alion will be helping the USAF to configure and model new Master Data Management business processes to support their portfolio of logistics initiatives. The award extends One Network’s presence within the USAF and across the Department of Defense, and as our multi-party federated Master Data Management capabilities are deployed for the USAF, it strengthens our ability to provide even more value to our customers in the future.”

Since 2008, One Network Enterprises has supported mission-critical capabilities for multiple agencies of the U.S. Department of Defense, including the U.S. Army, Air Force, Marine Corps, and current work with the U.S. Navy, in conjunction with their teams and allies all over the world.

Share article

Jun 21, 2021

Google and NIST Address Supply Chain Cybersecurity

Google
NIST
SLSA4
Sonatype
Elise Leise
3 min
The SolarWinds and Codecov cyberattacks reminded companies that software security poses a critical risk. How do we mitigate it?

As high-level supply chain attacks hit the news, Google and the U.S. National Institute of Standards and Technology (NIST) have both developed proposals for how to address software supply chain security. This isn’t a new field, unfortunately. Since supply chains are a critical part of business resilience, criminals have no qualms about targeting its software. That’s why identifying, assessing, and mitigating cyber supply chain risks (C-SCRM) is at the top of Google and NIST’s respective agendas. 

 

High-Profile Supply Chain Attacks 

According to Google, no comprehensive end-to-end framework exists to mitigate threats across the software supply chain. [Yet] ‘there is an urgent need for a solution in the face of the eye-opening, multi-billion-dollar attacks in recent months...some of which could have been prevented or made more difficult’. 

 

Here are several of the largest cybersecurity failures in recent months: 

 

  • SolarWinds. Alleged Russian hackers slipped malicious code into a routine software update, which they then used as a Trojan horse for a massive cyberattack. 
  • Codecov. Attackers used automation to collect credentials and raid ‘additional resources’, such as data from other software development vendors. 
  • Malicious attacks on open-source repositories. Out of 1,000 GitHub accounts, more than one in five contained at least one dependency confusion-related misconfiguration. 

 

As a result of these attacks and Biden’s recent cybersecurity mandate, NIST and Google took action. NIST held a 1,400-person workshop and published 150 papers worth of recommendations from Microsoft, Synopsys, The Linux Foundation, and other software experts; Google will work with popular source, build, and packaging platforms to help companies implement and excel at their SLSA framework

 

What Are Their Recommendations? 

Here’s a quick recap: NIST has grouped together recommendations to create federal standards; Google has developed an end-to-end framework called Supply Chain Levels for Software Artifacts (SLSA)—pronounced “Salsa”. Both address software procurement and security. 

 

Now, here’s the slightly more in-depth version: 

 

  • NIST. The organisation wants more ‘rigorous and predictable’ ways to secure critical software. They suggest that firms use vulnerability disclosure programmes (VDP) and software bills of materials (SBOM), consider simplifying their software and give at least one developer per project security training.
  • Google. The company thinks that SLSA will encompass the source-build-publish software workflow. Essentially, the four-level framework helps businesses make informed choices about the security of the software they use, with SLSA 4 representing an ideal end state. 

 

If this all sounds very abstract, consider the recent SolarWinds attack. The attacker compromised the build platform, installed an implant, and injected malicious behaviour during each build. According to Google, higher SLSA levels would have required stronger security controls for the build platform, making it more difficult for the attacker to succeed. 

 

How Do The Proposals Differ? 

As Brian Fox, the co-founder and CTO at Sonatype, sees it, NIST and Google have created proposals that complement each other. ‘The NIST [version] is focused on defining minimum requirements for software sold to the government’, he explained, while Google ‘goes [further] and proposes a specific model for scoring the supply chain. NIST is currently focused on the “what”. Google, along with other industry leaders, is grappling with the “how”’. 

 

Share article