20 avril 2018 | International, Naval

Why the Navy wants more of these hard-to-find software developers

By:

With a relative dearth of cyber expertise in the military, Congress mandated last year the services begin direct commissioning pilot programs. The Navy, however has been doing direct commissioning for highly skilled software engineers for a few years, albeit on a small scale.

The cyber warfare engineer (CWE) program is a highly competitive program with officers on five year rotations performing software or tool development for cyber operators. CWEs serve as members of the cyber mission force, the Navy's cyber mission force teams that serve as the cyber warriors for U.S. Cyber Command, producing cyber tools, but can also conduct target analysis, vulnerability research, and counter-measure development against malicious cyber activities.

Since 2011, the Navy has only recruited 25 of these commissioned officers to its ranks.

“Twenty-five developers in the Navy as military officers is definitely not enough,” Lt. Christopher Liu, the most senior cyber warfare engineer told Fifth Domain in an interview at the Navy League's Sea Air Space conference April 9.

With a relative dearth of cyber expertise in the military, Congress mandated last year the services begin direct commissioning pilot programs. The Navy, however has been doing direct commissioning for highly skilled software engineers for a few years, albeit on a small scale.

The cyber warfare engineer (CWE) program is a highly competitive program with officers on five year rotations performing software or tool development for cyber operators. CWEs serve as members of the cyber mission force, the Navy's cyber mission force teams that serve as the cyber warriors for U.S. Cyber Command, producing cyber tools, but can also conduct target analysis, vulnerability research, and counter-measure development against malicious cyber activities.

Since 2011, the Navy has only recruited 25 of these commissioned officers to its ranks.

“Twenty-five developers in the Navy as military officers is definitely not enough,” Lt. Christopher Liu, the most senior cyber warfare engineer told Fifth Domain in an interview at the Navy League's Sea Air Space conference April 9.

“We definitely need to increase the billets and increase the amount that we can hire ... to have more talents to be able to work on the cyber mission,” he said. “As soon as the number increases, we'll be able to expand the program rather than just five years to eight years, hopefully make it into a 20 year career so people can get trained up and work on missions and not be forced into different fields.”

The Pentagon has been besieged by concerns about the DoD's ability to both retain and attract cyber talent among its ranks when similar jobs in the private sector pay significantly more.

Vice Adm. Michael Gilday, commander of 10th Fleet/Fleet Cyber Command, acknowledged in recent congressional testimony that the military is not competitive with the private sector and noted that the base pay for the CWE position is around $37,000 a year.

“That's what we pay somebody to answer the phones around here,” Senator Claire McCaskill, responded to Gilday interrupting him in frustration. “We're asking them to have incredible expertise. That seems to me totally unrealistic.”

Some current CWEs feel the work they're doing inside the Navy has greater meaning than similar work they did in the private sector.

“I find that this is a lot more fulfilling,” Ensign Jordan Acedera, the most junior CWE told Fifth Domain. “You finish a project, you're given something that's a lot more challenging and that really tests you.”

For Lt. (j.g.) George John, who was formerly writing software at a stock trading company, work with the CWE provides a better environment that's not driven so much by profit margins and hitting quarterly revenue targets.

“We don't have to worry about profitability or bringing to market,” he said. “We can pursue a little more ... what's possible. Throw stuff against the wall, see what sticks, take our time to figure out a plan of action.”

One of the biggest challenges, however, is lack of knowledge of the program, even inside the Navy.

“You still walk across captains and commander who say 'CWE, what in god's name is that,” John said.

With more CWE personnel in the force, the Navy could build a more informed and skilled software engineering cadre, the group said.

“There's tons of software. Everybody has some type of software pet project,” John said. “To be able to get more CWEs on those things and coordinate with one another and say here's what [Consolidated Afloat Networks and Enterprise Services] is doing with their communications and their infrastructure. How are we doing that differently on the base side? You can talk and address security concerns with one another.

Just within the cyber operations realm, Liu said, as the headcount increases, the CWEs could work on the requirements the operational community within the cyber mission force rather than having to prioritize projects. They could even start to look at developing capability prior to a specific requirement coming in as a means of staying ahead of the game as opposed to waiting for and reacting on requirements from operators.

https://www.defensenews.com/digital-show-dailies/navy-league/2018/04/11/why-the-navy-wants-more-of-these-hard-to-find-software-developers/

Sur le même sujet

  • US military targets deepfakes, misinformation with AI-powered tool

    1 août 2023 | International, C4ISR

    US military targets deepfakes, misinformation with AI-powered tool

    Discerning fact from fiction is vital to military operations. The task is increasingly complex as bad information floods social media and other channels.

  • Report slams Norwegian Navy for training, safety shortfalls in the run-up to frigate sinking

    13 novembre 2019 | International, Naval

    Report slams Norwegian Navy for training, safety shortfalls in the run-up to frigate sinking

    By: David B. Larter WASHINGTON – The bridge watch team on the stricken Norwegian frigate Helge Ingstad was distracted, inadequately trained and failed to take adequate precautions while transiting close to land, according to an accident report released Friday by the Norwegian government. The watch standers on Helge Ingstad, which collided with the Maltese-flagged tanker Sola TS and subsequently sunk outside Sture Terminal near the mouth of the North Sea, were busy conducting a watch turnover and attempting to conduct training during the navigation in the channel, which it was conducting at 17-18 knots. “The Navy lacked competence requirements for instructors. The Navy had assigned the officer of the watch a role as instructor which the officer of the watch had limited competence and experience to fill,” the report reads. “Furthermore, the Navy had not given the officer of the watch assistant sufficient training and competence to operate important bridge systems while training the officer of the watch assistant trainee at the same time.” The Norwegian publication VG reported last December that the ship's captain, Capt. Preben Østheim, was asleep in his cabin during the transit through the strait near Sture, which is less than three miles across at its narrowest point. The report, which also faulted the tanker for failing to mitigate potential risks and the vessel traffic control service for inadequate monitoring, takes special aim at the Navy for a lack of qualified navigators, and for short-changing the training of junior officer, leaving bridge watch teams underqualified. “As a consequence of the clearance process, the career ladder for fleet officers in the Navy and the shortage of qualified navigators to man the frigates, officers of the watch had been granted clearance sooner, had a lower level of experience and had less time as officer of the watch than used to be the case,” the report found. “This had also resulted in inexperienced officers of the watch being assigned responsibility for training. The level of competence and experience required for the lean manning concept (LMC), was apparently not met.” The accident report shows that the bridge team confused the Sola TS for a stationary object on land, and because the watch standers were distracted with training, they were not fully engaged with monitoring the communications on the radio. “A more coordinated bridge team with more information sharing would have been more capable of detecting the tanker sooner,” the report said. “Achieving good teamwork is particularly challenging in the case of bridge teams whose members are constantly being replaced. “Furthermore, the bridge team was part of a culture characterized by great confidence in each other's skills, and this may have contributed to the perception of them being in full control of the situation and thus less vigilant and sensitive to weak signals of danger.” The report is part one of a two-part report and only encompasses the actions that led to the collision. Further findings about the actions after the collision will be released as part of a second report to be released later. ‘Not Particularly Demanding' According to the report, the transit through the body of water known as the Hjeltefjord “was not considered particularly demanding, as the fairway is open and offers a good view all around,” the report found, which likely contributed to a sense of complacence among the crew. That echoes the sentiments of the Capt. Østheim, who told VG he didn't think he needed to be on the bridge during that transit. “After 12 years at sea, I know the coast as my own pocket, so I know exactly when I need to be on the bridge and when I can rest,” Østheim told VG. There is generally little traffic through the channel and there is no traffic separation scheme. The Sola TS, which the report said was likely creating some visual confusion for Ingstad's watchstanders because of its illuminated deck lights at night, announced it was underway on the radio during the exact time that Ingstad's watchstanders were turning over, likely causing them to miss the transmission, the report reads. “At the same time as Sola TS notified of her departure from the Sture Terminal, the watch handover between the officers of the watch started on HNoMS Helge Ingstad, while the officer of the watch trainee continued to navigate the frigate,” the report reads. “During the watch handover, the officer of the watch being relieved and the relieving officer of the watch observed an object at the Sture Terminal, to starboard of the frigate's course line. The ‘object' was observed both visually and on the radar display in the form of a radar echo and AIS symbol. The two officers of the watch discussed, but did not clarify, what the ‘object' might be. “Both officers of the watch had formed the clear perception that the ‘object' was stationary near the shore and thus of no risk to the frigate's safe passage.” The situation was made even more perilous by the fact that Ingstad did not have its Automatic Identification System on, which would have notified traffic service and Sola TS of Ingstand's location. Traffic Service lost track of Ingstad because operators had their displays zoomed in too far, the report found. Collision As the Ingstad came closer to the terminal, the Sola TS, which the officer was convinced was a stationary object by the terminal, was appearing on radar to have made some distance between the pier and the water, but the officer was still not sure it wasn't a stationary object becoming more clear on the radar screen because Ingstad was closer to it. “A more experienced officer of the watch would probably have had greater capacity to pick up on weak signals of danger and be better equipped to suspect that his/her own situational awareness suffered from misconceptions,” the report read. “The officer of the watch thought, however, that the course had to be adjusted slightly to port to increase the passing distance to the ‘object'.” In the minutes before the collision, the Sola TS established contact with Ingstad's officer of the watch to get them to take an avoidance maneuver by turning to starboard. But the watch still thought that the Sola was a stationary object and that turning to starboard would run into it. “When HNoMS Helge Ingstad did not alter course, the master on Sola TS ordered ‘stop engines' and, shortly afterwards, the pilot ordered full speed astern on the engines,” the report read. “These two measures were carried out only short time before the collision, and were therefore without material effect. “When the officer of the watch on HNoMS Helge Ingstad understood that the ‘object' giving off light was moving and on direct course to collide, it was too late to avoid the collision.” ‘I don't feel shame' The decision of the captain to not be on the bridge or, at the very least, to have posted a special navigation detail with the ship so close to land is perplexing, said retired U.S. Navy cruiser skipper Capt. Rick Hoffman, a career surface warfare officer. “If I'm within five miles of land I'm going to have some kind of navigation detail posted,” which in the U.S. Navy means a team of more qualified watch standers, extra lookouts and more than likely either the Commanding Officer, Executive Officer or both, would be on the bridge overseeing the watch. It's further perplexing as to why the officer of the deck, or officer of the watch, was conducting training during a transit so close to land, Hoffman said. “[The officer of the deck should be] looking out the window and completely focused on the transit,” he said. “We would not use that as a training opportunity. The OOD and the Conning Officer has no other task.” However, Østheim told VG in December he has no regrets about his actions, though he accepts that he was overall responsible for the ship. “I don't feel any shame,” he said. “As the ship's chief, I of course have the overall responsibility for the ship and its crew. It's extremely sad that this happened. It's an accident that should not happen, but I don't feel any shame.” https://www.defensenews.com/naval/2019/11/12/safety-report-slams-the-norwegian-navy-for-training-safety-shortfalls-in-the-runup-to-frigate-sinking/

  • Aviation summit opens amid jet shortages, supply chain turbulence

    22 juillet 2024 | International, Terrestre

    Aviation summit opens amid jet shortages, supply chain turbulence

Toutes les nouvelles