July 24, 2024 | International, C4ISR, Security
Microsoft Defender Flaw Exploited to Deliver ACR, Lumma, and Meduza Stealers
Microsoft patches Defender flaw exploited to deliver info stealers ACR, Lumma, Meduza in global campaign
September 30, 2020 | International, C4ISR, Security
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.
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/
July 24, 2024 | International, C4ISR, Security
Microsoft patches Defender flaw exploited to deliver info stealers ACR, Lumma, Meduza in global campaign
January 2, 2019 | International, Aerospace
By: Valerie Insinna ASHINGTON — Boeing won't be delivering the first KC-46 tanker to the Air Force in 2018 as planned, due to Defense Secretary Jim Mattis' surprise ouster from the Pentagon, a source told Defense News on Monday. The Air Force had intended to accept the first KC-46 by the end of December and was awaiting signature from Mattis, which would finalize the delivery plans, Reuters first reported on Dec. 20. However, later that day, Mattis announced that he would step down from the top Defense Department post in February, and just three days later, President Donald Trump tweeted that Mattis would wrap up his work as secretary of defense by the end of 2018. With sweeping changes in leadership at the Pentagon imminent, a decision on KC-46 was pushed out, a source close to the program told Defense News. The situation was further complicated because Deputy Secretary of Defense Patrick Shanahan — who by the end of Dec. 31 will temporarily take over Mattis' role as defense secretary — is a former Boeing executive and must recuse himself from all decisions involving the company. Boeing declined to confirm that the delivery would not take place on Dec. 31. “KC-46 remains a top priority and we look forward to delivering tanker aircraft in partnership with the Air Force,” said Kelly Kaplan, a spokeswoman for the company, in a statement to Defense News. The Air Force did not immediately respond to a request for comment. The delay is a blow for Boeing, which had promised to deliver the first tanker by the end of 2018 after a string of missed delivery dates stemming back to August 2017. “We continue to make steady progress toward final certification of the KC-46 tanker,” Boeing's CEO Dennis Muilenburg said in an October earnings call. “We are working with our U.S. Air Force customer toward completing all the steps required to deliver the first tanker aircraft this quarter." The company has now racked up more than $3 billion in pre-tax charges on the program, as it is responsible for any costs beyond the $4.9 billion fixed price contract value originally awarded in 2011. Boeing officials are hopeful that the Air Force will be able to move forward with delivery after a set of meetings in early 2019, one source said. But at the moment it is unclear who will authorize the KC-46 delivery with Shanahan barred from the process, though it may fall to Air Force Secretary Heather Wilson or to Ellen Lord, undersecretary of defense for acquisition and sustainment. The Air Force plans to buy 179 KC-46s throughout its program of record. McConnell Air Force Base in Kansas is set to become the first installation to receive the new tankers, and training for pilots and boom operators has already begun. https://www.defensenews.com/air/2018/12/31/first-kc-46-delivery-stalled-by-mattis-departure
November 1, 2021 | International, Aerospace
The final delivery of GE's F110 engines would occur in 2031, and the engine deliveries would help produce 136 F-15EXs.