New Android Malware 'Ajina.Banker' Steals Financial Data and Bypasses 2FA via Telegram

On the same subject

• 

  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/

• 

  February 7, 2024 | International, Land, C4ISR

  Adopt a treaty for semiconductor export control

  Opinion: The absence of a robust global semiconductor export control regime leaves the United States vulnerable in the technological race.

• 

  May 7, 2020 | International, Naval

  Navy Wants Robot Boats But Will Still Need Sailors To Fix Them

  "We need to find a balance of vehicle designs that enables the cost to be cheap enough that we can afford them, but it's not so highly optimized towards the purely unmanned spectrum that it's cost prohibitive to maintain them." By PAUL MCLEARYon May 06, 2020 at 3:27 PM WASHINGTON: The Navy needs to comb through a host of thorny issues before deploying a new fleet of unmanned ships to confront China, Russia, and Iran. “You don't hear me talking about artificial intelligence and machine learning and things like that just yet,” said Capt. Pete Small, the Navy's program manager for Unmanned Maritime Systems at a C4ISRnet conference this morning. “Those aren't my first concerns. My first concerns are about the field stability and sustainability of these systems right now.” The Navy just isn't equipped to deploy or sustain a new fleet of unmanned vessels yet. “Our infrastructure right now is optimized around manned warships,” Small said. “We're gonna have to shift that infrastructure for how we prepare, deploy, and transit” over large bodies of water before large numbers of unmanned vessels can be effective, he said. It's not clear where that planning stands, but the service has already invested tens of millions in the early work of developing a family of large and medium unmanned vessels, and is looking to vastly ramp that up in the 2021 budget, asking for $580 million for research and development. In 2019 an unmanned Sea Hunter prototype autonomous vessel sailed from San Diego to Hawaii, but it needed to repair several broken systems along the way, forcing sailors to board the ship. It was the first experiment of its kind, one the Navy has not repeated. Those mechanical problems point to work the Navy must do to reconfigure its logistics tail to meet the needs of a new class of ship. “We're going to have to transition from a [system] more optimized around our manned fleet infrastructure to a more distributed mix of these large manned platforms to smaller platforms,” Small said, “we're gonna need to talk about things like, tenders for heavy lift ships, or forward operating bases, things like that.” The early thinking is the service will use the ships as sensors deployed well forward of manned ships and carrier strike groups, which could be at risk if they maneuvered too close to contested waters. But the Navy isn't going to pin everything on a nascent fleet of robot boats — a new class of manned frigates is also being built to operate inside the range of enemy precision weapons. The frigates are going to be smaller and faster than current destroyers, with the ability to generate much more power so they can use lasers and other weapons for both offensive and defensive missions. The Navy is considering several sizes of USVs, including a large variant between 200 and 300 feet in length and having full load displacements of 1,000 tons to 2,000 tons. The ships should be low-cost, and reconfigurable with lots of room capacity for carrying various payloads, including mine hunting and anti-surface warfare. The 2021 budget submission proposes using research and development funding to acquire two more prototypes and another in 2022. Plans then call for buying deployable LUSVs at a rate of two per year. Medium unmanned ships will likely come in at between 45 to 190 feet long, with displacements of roughly 500 tons. The medium ships are thought to skew more toward mission modules revolving around intelligence, surveillance and reconnaissance payloads and electronic warfare systems. The first MUSV prototype was funded in 2019, and the Navy wants to fund a second prototype in 2023. Fundamental issues need to be sorted out before the Navy buys one of these ships. “We need to find a balance of vehicle designs that enables the cost to be cheap enough that we can afford them, but it's not so highly optimized towards the purely unmanned spectrum that it's cost prohibitive to maintain them,” Small said. If the maintenance is too complicated and time consuming, and “we have to take the whole vehicle out of the water and take it apart in some explicit manner to replace the parts, it's not gonna really support what we need in the field. So really, the sustainability of the technology is as important — if not more important — in the near-term than the technology itself.” https://breakingdefense.com/2020/05/navy-wants-robot-boats-but-will-still-need-sailors-to-fix-them/