Back to news

August 6, 2024 | International, C4ISR, Security

INTERPOL Recovers $41 Million in Largest Ever BEC Scam in Singapore

INTERPOL recovers $41 million from a $42.3 million business email scam targeting a Singapore firm using its global payment mechanism.

https://thehackernews.com/2024/08/interpol-recovers-41-million-in-largest.html

On the same subject

  • OMFV: Army Seeks Industry Advice On Bradley Replacement

    February 27, 2020 | International, Land

    OMFV: Army Seeks Industry Advice On Bradley Replacement

    Having rebooted the Optionally Manned Fighting Vehicle program, the Army is now is asking industry input on how to achieve nine goals, from survivability to mobility to streamlined logistics. By SYDNEY J. FREEDBERG JR.on February 26, 2020 at 4:01 AM Two months ago, the Army cancelled its original solicitation to replace the M2 Bradley troop carrier after no company could meet the strict requirements. This afternoon, the Army officially asked for industry input on how to achieve nine broadly-defined “characteristics” for the future Optionally Manned Fighting Vehicle. “Feedback may be submitted in any form (concepts, information papers, technical papers, sketches, etc.),” says the announcement on SAM.gov. “The Army would like to obtain this initial feedback prior to 06 March 2020.” This call for suggestions on how to move forward comes just weeks after the Army issued a surprisingly apologetic survey asking industry what they did wrong the first time around. It's part of a newly humble approach in which the Army doesn't prescribe formal requirements up-front but instead lays out broad objectives and asks industry how best to achieve them. The chief of Army Futures Command, Gen. Mike Murray, gave reporters a preview of the nine characteristics three weeks ago, but the list announced today is much more detailed – though still leaving plenty of room for companies to brainstorm solutions. Our annotated highlights from the announcement – the emphasis is in the original: Background: The OMFV, as part of an Armored Brigade Combat Team (ABCT), will replace the Bradley to provide the capabilities required to defeat a future near-peer competitor's force. The Army is seeking a transformational increase in warfighting capability, not simply another incremental improvement over the current Bradley Fighting Vehicle. Concept of employment: As part of an ABCT, the OMFV will not fight alone, but rather as part of a section, platoon, and company of mechanized infantry.... “Near-peer competitor” is Pentagon jargon for “China or Russia” – chiefly Russia in this case, since the plains of Eastern Europe are a far more likely arena for armored warfare than Pacific islands. That the Army wants “transformational” improvements, not “incremental” ones, shows there's still some real ambition in the vision for this vehicle. At the same time, the OMFV will still fight “as part of an ABCT,” meaning the existing Armored Brigade Combat Team organization — not as part of some all-new organization with all-new equipment, as was once envisioned for the cancelled Future Combat Systems. Survivability. The OMFV must protect the crew and Soldiers from emerging threats and CBRN environments. The OMFV should reduce likelihood of detection by minimizing thermal, visual, and acoustic signatures. In other words, the vehicle needs to give the crew a chance of survival against cutting-edge anti-tank missiles, precision-guided artillery, attack drones and other such “emerging threats,” as chemical, biological, radiological, and nuclear contamination (CBRN). That does not mean the vehicle itself has to survive intact. The way this is worded, if a hit totals the OMFV but the soldiers inside can walk away, the Army will count that as a win. (The JLTV 4×4 truck takes this same approach to roadside bombs). So the OMFV doesn't necessarily have to have heavy armor protecting the entire vehicle. It could have a heavily armored crew compartment, light armor elsewhere, and an Active Protection System to intercept incoming threats. (The Russian T-14 Armata uses this combination). It also should avoid being spotted in the first place by eye, ear, or thermal sensor, which might favor designs with hybrid-electric motors that can switch from hot, noisy diesels to a battery-driven stealth mode. Mobility. The OMFV must have mobility that can keep pace with the Abrams in a combined arms fight through rural and urban terrain. That's the M1 Abrams main battle tank, which the existing M2 Bradley and M109 Paladin howitzer were also designed to keep up with. This is another aspect of that “concept of employment” that calls for the OMFV to slot into existing formations and work closely with existing vehicles. Note also the reference to “rural and urban terrain,” which will come up again: Traditionally the Army has avoided city fighting, but as urban sprawl covers ever more of the planet, technology and tactics have to adapt to brutal close-quarters combat. Growth. The OMFV must possess the growth margins and open architecture required for rapid upgrades and insertion of future technologies such as mission command systems, protection systems, and sensors. This characteristic is really where you get the potential for “transformational” improvements. The M2 Bradley was originally introduced in 1980 and, after 40 years of upgrades, it has very little margin left to handle additional weight or – even more important nowadays – power-hungry electronics. The Bradley's lack of room to grow has driven the Army to try replacing it three times already: the original OMFV requirements cancelled this year; the Ground Combat Vehicle cancelled in 2014; and the Future Combat Systems cancelled in 2009. Hopefully, fourth time's the charm. Lethality. The OMFV-equipped platoons must defeat future near-peer soldiers, infantry fighting vehicles, helicopters, small unmanned aerial systems, and tanks as part of a Combined Arms Team in rural and urban terrain. This is a more ambitious hit list than the Bradley, which sports machineguns for killing infantry, a 25 mm autocannon to destroy light armored vehicles, and the obsolescent TOW missile for taking on heavy tanks. The Pentagon is increasingly worried about small drones, which ISIS terrorists have used as flying IEDs and Russian artillery has used as spotters for barrages. With Russia and China developing increasingly sophisticated anti-aircraft systems, there's also a concern that US fighters may not be able to keep enemy attack helicopters at bay, forcing ground forces to handle that threat themselves. These aerial targets require more sophisticated tracking systems, and drones may be best dealt with by electronic jamming or lasers rather than bullets. Weight. The OMFV must traverse 80% of Main Supply Routes (MSRs), national highways, and bridges in pacing threat countries, and reduce the cost of logistics and maintenance. Designs must allow for future growth in components and component weights without overall growth of vehicle weight through modularity and innovation. Weight is the issue that has bedeviled Bradley replacements for two decades. The FCS vehicles, optimized for air transport, were too light to carry adequate armor; GCV was too heavy; and the original OMFV couldn't meet its air transport requirements and its protection requirements at the same time. With most bridges in Eastern Europe unable to safely take weights over 50 tons, too much heavy armor can cripple your mobility. Logistics. The OMFV must reduce the logistical burden on ABCTs and must be equipped with advanced diagnostic and prognostic capabilities. Advanced manufacturing and other innovative techniques should be included in the design that reduce the time and cost of vehicle repairs. There are two big factors that make a vehicle hard to keep supplied and in working order. One is weight – heavier vehicles burn more fuel – and the other is complexity. High-tech is usually high-maintenance. The US military is hopeful that AI-driven predictive maintenance can detect and head off impending breakdowns, and that 3D printing can produce at least some spare parts on demand without a long supply line. Transportability. The OMFV must be worldwide deployable by standard inter- and intra-theater sea, waterway, air, rail, and road modes of transportation. The original OMFV requirement very specifically called for two of the vehicles to fit on a single Air Force C-17 jet transport, which proved undoable with the weight of armor desired. This time, the Army isn't specifying any particular aircraft. In practice, armored vehicles are almost always shipped by sea and, where possible, stockpiled on allied soil well before a crisis erupts. On land, since tracked vehicles aren't designed to drive hundreds of miles by road, they're usually deployed to the battle zone by train or tractor-trailer, both of which have their own weight limits. Manning. The OMFV should operate with the minimal number of crew members required to fight and win. The OMFV should allow commanders to choose between manned or remote operation based on the tactical situation. This is the objective that gave the OMFV its name: Optionally Manned Fighting Vehicle. Now, since it's a Bradley replacement, the OMFV is supposed to be a troop carrier – specifically, the heavily armed and armored kind known as an Infantry Fighting Vehicle – so by definition it needs to carry people. But the Army is intensely interested in having the option to run it by remote control, or maybe even autonomously, to (for example) scout out especially dangerous areas or carry casualties back to an aid post without pulling healthy soldiers out of the fighting line. Training. The OMFV should contain embedded training capabilities that are compatible with the Synthetic Training Environment (STE). STE is the Army's total overhaul of its training simulators, drawing on commercial gaming technology to develop an array of virtual and augmented reality systems using a common database of real-world terrain. Instead of having to use a simulator in a warehouse somewhere, the Army wants troops to be able to run virtual scenarios on the same vehicles they'll actually fight with. All these characteristics are intertwined – and after its past troubles, the Army is acutely aware that maximizing one, such as protection, may compromise another, such as transportability. That's another thing the service wants feedback on, the announcement says: “The Army is interested in industry partners' ability to meet the desired characteristics and what trades” – that is, trade-offs – “may be necessary.” https://breakingdefense.com/2020/02/omfv-army-seeks-industry-advice-on-bradley-replacement

  • How the Air Force data strategy is evolving

    August 31, 2018 | International, C4ISR

    How the Air Force data strategy is evolving

    By: Valerie Insinna The Air Force's ambitious new intelligence, surveillance and reconnaissance strategy calls for a sensing grid that fuses together data from legacy platforms (such as the RQ-4 Global Hawk), emerging technologies (like swarming drones), other services' platforms and publicly available information. Artificial intelligence will decipher that data. Such a system may sound like science fiction, but the service believes it could be up by 2028. Lt. Gen. VeraLinn “Dash” Jamieson, the deputy chief of staff for ISR, explained the genesis for the Air Force's new “Next Generation ISR Dominance Flight Plan,” which lays out the service's goals for the next 10 years. She spoke recently with Valerie Insinna of sister publication Defense News. C4ISRNET: First, why does the Air Force need a new ISR plan? LT. GEN. “DASH” JAMIESON: This Flight Plan really does go out for 10 years. We did it because, primarily, we have a National Defense Strategy that was written, and crafted, and came out in January. It looks at a changing complex world with a great power competition. We see that the character of war is potentially changing based off of technologies that are being fielded and that are under development today. So that is one reason. The other reason really predates the NDS. When I took over the A2, the chief of staff, Gen. [David] Goldfein, really looked at me and said, “Dash, your ISR Enterprise is very airman intensive.” So I took an evaluation with my team, and it is extremely airman intensive. The airmen are applying new things to old tools. How we share the outcomes of our sensing capability is via PowerPoint that our airmen construct using Excel spreadsheets to look at the data, identify what is the data, and try to then manually layer the data in this construct. To get at some fused data, to get at what are the trends, that approach is not going to give us the ability to actually conduct our operations at the speed of relevance across the entire spectrum of conflict. More importantly, it drags out our decision cycle for our war fighter. When you drag out your own decision cycle, the adversary has the ability to get inside of your decisions and to disrupt those decisions. C4ISRNET: What can you do? JAMIESON: Our intent is to actually get inside the adversaries' decision cycle and create chaos. Once you do that, that really is a tough, tough problem to get out of. We established a framework and we have two major efforts. One was how we integrate and balance our ISR portfolio. We take a look at what we have today, what we see are our seams and our capability gaps, and we determine how we make investments on that. But our other major effort is, “What is my future pathway, what are those lines of effort that are going to give us an advantage?” We came up with three macro categories. First, it's disrupt the technologies, and see what capabilities and options that brings you. The second is how we bolster lethality and readiness with what we're going to do to the enterprise. Then, third, it's how we establish foundational capabilities that transcend this entire framework. C4ISRNET: How does that manifest itself? JAMIESON: You have to have a data strategy because you actually have to have standards on how you are going to condition your data. How are you going the access your data? How is your data gonna move for your infrastructure? How are you gonna secure your data? How do you ensure your data is not up for malicious attack? We did talk to industry. Then, we also worked with our acquisition professionals and said we really need to have an agile capability development concept annex. That really gets at how we prototype, how we do DevOps, what is the environment and how we get at acquisition of software in a very different paradigm. C4ISRNET: What does that mean for the force? JAMIESON: In 10 years, our digital airmen will be the preponderance of the force. Our airmen right now, a majority of the ones 24 and under, come in already knowing how to code. So what skill sets do we know come up for ISR where coding is fundamental? How does that affect our retention capability? Because we want to empower and unleash them to develop new skill sets that will complement where we're going with the ISR enterprise. Finally, we want to partner much deeper with our think tanks, our academia, our labs so that we are sharing right up front. C4ISRNET: You've talked about a collaborative sensing grid that uses advanced technology. What does that look like? JAMIESON: No longer are we going to invest primarily in just the air domain. We're gonna look at capabilities in and from space. We're also working with our joint partners to integrate in surface and subsurface capabilities, so that our sensing grid of tomorrow is no longer a sensor looking in a specific domain with a specific in. If we initially look at the first Predator, we had motion video that was EOIR, electro optical infrared. Then, maybe we need to have SAR. Then when we went to hyperspectral, we went to EO/IR and [synthetic aperture radar], because we're getting multiple ins in a domain. C4ISRNET: Is this a place to use AI? JAMIESON: We want to have algorithms to get at ensuring that the data is pure and not malicious or false. But we are going to take that, and we're going to use that with our exquisite capability to really flesh out that sensing grid. We're going to do it so now that we now have resiliency, it's not just in one domain or one capability. If we look at high altitude, what can I do from a manned and an unmanned capability? From a persistent, standoff and stand-in capability? We're going to look at swarming, we're going to look at even hypersonic capability — that give us a multitude of new capabilities to form this fencing grid. The beauty of the sensing grid is it doesn't forget what we have already fielded. Our airmen are looking at why is something happening, what are the trends. In other words, we fielded a sensor to answer a question. What we're trying to develop is how I get the data so that I can fuse it, look at it, then ask the right questions. C4ISRNET: What goals do you have over the next 10 years to really bring that into the ISR infrastructure? JAMIESON: The real importance of cloud computing ... and when I talk about cloud computing, I'm really talking about it as a service. The service that we're trying to get is really a platform, infrastructure and software. I'm not just looking for a data-storage hub. I'm looking for a partnership with industry. I'm not necessarily looking for just one industry partner; I'm looking for multiple industry partners in a multi-cloud concept, because each one of the big five, if we just were to use that, has their expertise. We want to be able to take that expertise and use it. When I say platform, infrastructure, software, I'm really talking about the capability that they give me to field at scale. Every time you turn on your Tesla updates are instantaneous, and I want my ISR enterprise to have those type of instantaneous updates on the infrastructure so that I can continue to prototype my applications. The data is what we're going to use to develop those applications. We've told industry, “You can make applications and we're going to buy applications from you. The data is ours. But we want to partner with you on the ability to create algorithms, applications, different software packages.” C4ISRNET: You talked about private sector partnerships, but how do you overcome or address the fallout from Project Maven? JAMIESON: We have been talking a lot about this. I don't see this as a problem for the ISR enterprise, I don't really see this as a problem for DoD. I see this as a U.S. public issue that needs to be debated and discussed. Because when we look at artificial intelligence and you look at how you develop algorithms, there's always a bias when we put the math together. The bias is formed by the humans that are putting that math together. What I mean by that is, the bias right now is whether we are going to use Western values. We value privacy, we value life, liberty and the pursuit of happiness. Our competitors, as we've seen, do not value privacy. Nor do they value life, liberty or the pursuit of happiness. They have a completely different construct. I think the American public needs to have a discussion on where do we want to go. How do we want to approach this? What does it mean to us as a society? How are we going to protect our privacy? How are we going to protect our values? In lieu of that, then how does that apply to our national defense? We absolutely welcome that debate. We want to have that dialogue. C4ISRNET: Do you envision capability upgrades for the Global Hawk or Reaper? Are we going to see certain platforms phase out, or new platforms built into the budget? JAMIESON: As we look at where we are with our [remotely piloted aircraft, or RPA], U-2, our Rivet Joint capability now, it was pretty airmen intensive. What we are doing is developing algorithms to take the data off those platforms in a much faster cycle. I don't want to do processing, exploitation and dissemination in a reach-back mode in the future. I want to process, to exploit right on the aircraft or right on the sensor so that I can actually take that data, condition it, and then use it with other data so that I can get out better quality of information into the joint war fighter. Think of the Reaper. Today, we take the data off. If it's full-motion video, my airmen are actually identifying the object and looking at patterns of life after staring at that video for hours on end. What we're gonna do is automate that entire process and that is what Maven is doing. But we are developing algorithms much faster. In the next two to four years, it will be processed at the sensor. So that allows the airmen to no longer take the hours to do the processing. It takes a lot of bandwidth, it takes a lot of time. We want to do all that onboard the sensor so that I can fuse the data from the sensing grid. The reason I want to fuse the data from the sensing grid is because I want to identify certain characteristics. C4ISRNET: Did the Flight Plan address capabilities at the platform level, such as whether new systems were needed? Or were you purely focused on exploiting data? JAMIESON: We have to go back and identify first where are our big gaps, because we are in a cost-effective modernization way forward. Do I look at what I need from a space capability? Do I look at what I need from a swarming RPA? Do I look at autonomous remotely piloted aircraft, whether they are high altitude or minis that go for a specific length? We want to have a balanced portfolio of standoff, penetrating and persistent capabilities. C4ISRNET: Are you going to invest in swarming capabilities? Or some sort of hypersonic vehicle that can do ISR? JAMIESON: It is in the mode of being thought about. But you have to look at what technologies are real today and what technologies are really going to be there for tomorrow. You don't want to commit early to something that isn't gonna give you the best payoff. C4ISRNET: Are there any concrete goals that you guys are looking at to make sure the department is staying on track? JAMIESON: I'm pretty direct, and I'm pretty blunt. In our classified ISR Flight Plan, I've got an implementer for every single annex with milestones, goals, objectives and pathways so that, starting in 2018, we have the deliverables to ensure that we do stay on path. We don't know what's going to happen with the internet of things. That could be just as disruptive as the internet was. https://www.c4isrnet.com/intel-geoint/isr/2018/08/30/how-the-air-force-data-strategy-is-evolving/

  • Leonardo signs contract to upgrade Italian Armed Force’s identification systems to new NATO standard

    March 6, 2020 | International, C4ISR, Security

    Leonardo signs contract to upgrade Italian Armed Force’s identification systems to new NATO standard

    Rome, March 5, 2020 - Leonardo has signed a contract with the Italian Defence authorities to supply and install ‘New Generation Identification Friend or Foe' (NGIFF) identification equipment, updated to the latest NATO Mode 5 Baseline 3 standard, for the Italian Armed Forces' land and naval platforms. The contract is worth approximately €75 million and will last for six years. Leonardo will supply several hundred NGIFF interrogators and cryptographic units in order to upgrade dozens of land and naval platforms across 15 different classes and types. The NGIFF systems will allow the Italian Armed Forces to maintain full interoperability with other NATO forces in joint operations as the alliance mandates the use of ‘Mode 5'-capable systems in its Minimum Military Requirements (MMR) for Air-to-Air and Surface-to-Air Identification. The Mode 5 standard confers a number of benefits in terms of identification and security. Identification Friend or Foe (IFF) technology is essential to military operations as it allows allied forces to be distinguished from potential threats. Under this contract, the equipment for Italy's land and naval platforms will provided entirely by Italian industry. Notably, Leonardo's Mode 5 NGIFF equipment uses the company's own cryptographic unit, which is the only alternative to a U.S. cryptographic system available on the market. Future contractual developments are planned which will see Leonardo equip further Italian aircraft and helicopters with the same capability, bringing them in-line with NATO standards. Leonardo is a worldwide leader in Mode 5-capable NGIFF technology. Previously, the company has been chosen by the UK Ministry of Defence to upgrade the IFF systems of over 400 air, land and naval platforms in collaboration with a partner company. View source version on Leonardo : https://www.leonardocompany.com/en/press-release-detail/-/detail/leonardo-signs-contract-to-upgrade-italian-armed-force-s-identification-systems-to-new-nato-standard?f=%2Fhome

All news