Guest Speaker Discusses PACFLT N6 Priorities
Capt. Victor Taylor, USN, emphasized that commercial technology is now inseparable from modern warfighting, providing unprecedented speed, capability and agility, while introducing significant cyber and supply-chain risk. The Department of War can no longer rely on custom-built systems or five-to-10-year acquisition cycles. Commercial operating systems, cloud services, open-source libraries, microelectronics, artificial intelligence and other technologies increasingly underpin weapons, command-and-control systems, logistics, unmanned platforms and communications. The challenge, Taylor argued, is adopting this innovation at commercial speed without allowing vulnerabilities to become the Achilles' heel of military operations.
Taylor framed his approach around understanding both ourselves and the adversary. His priorities include model-based systems engineering to understand architectures; mission-thread and data-flow analysis to identify dependencies; cyber-risk and threat analysis using frameworks such as MITRE ATT&CK; and translating technical vulnerabilities into operational mission impact. This methodology enables commanders to prioritize remediation, patching, resiliency and resources around the systems most critical to warfighting. Security must be designed into capabilities from the beginning rather than added afterward, and industry must recognize supply-chain protection as a shared national-security responsibility.
During the Q&A, Taylor addressed concerns about defense-industrial-base security and evolving requirements such as CMMC. He acknowledged that security controls do not always produce an obvious commercial return and cautioned against either treating minimum compliance as sufficient or imposing controls that make systems unusable. Policy and doctrine often lag technology by years, particularly as artificial intelligence and software capabilities evolve rapidly. Industry, he said, therefore has a responsibility to act as an honest broker and deliver what warfighters need today while government works to modernize outdated policies.
Taylor also stressed the shortage of software engineering expertise and encouraged younger professionals to continuously learn, ask questions and develop skills beyond formal military training. Because the department cannot secure or modernize everything simultaneously, leaders must identify critical mission threads and model their hardware, software, data flows, vulnerabilities and single points of failure. He cited nuclear command, control and communications as an example of a mission whose architecture must be thoroughly understood and protected.
Asked about operating in contested environments, Taylor argued that the department has foundational problems even in permissive environments. Rapidly fielded capabilities-accelerated during COVID-19 and by demands for greater connectivity aboard ships-sometimes introduced vulnerabilities without fully considering consequences. Speed must therefore have both magnitude and direction: leaders need sufficient information to make deliberate decisions while moving quickly.
Finally, Taylor identified decision-making and organizational fragmentation as major barriers. The department suffers from "application fatigue" and "system fatigue," with too many stakeholders, tools and disconnected decisions. Strategy should drive applications and systems, not the reverse. Operational commands may not control acquisition dollars, but their time, expertise, mission priorities and warfighter feedback strongly influence investment. Taylor challenged industry to bring mature, secure solutions that solve real operational problems now rather than prototypes requiring months of additional development. He further emphasized that scarce resources require prioritization: security must receive attention commensurate with mission importance, even when that means delaying capabilities, finishing incomplete efforts and resisting the temptation to chase every technology.
Taylor framed his approach around understanding both ourselves and the adversary. His priorities include model-based systems engineering to understand architectures; mission-thread and data-flow analysis to identify dependencies; cyber-risk and threat analysis using frameworks such as MITRE ATT&CK; and translating technical vulnerabilities into operational mission impact. This methodology enables commanders to prioritize remediation, patching, resiliency and resources around the systems most critical to warfighting. Security must be designed into capabilities from the beginning rather than added afterward, and industry must recognize supply-chain protection as a shared national-security responsibility.
During the Q&A, Taylor addressed concerns about defense-industrial-base security and evolving requirements such as CMMC. He acknowledged that security controls do not always produce an obvious commercial return and cautioned against either treating minimum compliance as sufficient or imposing controls that make systems unusable. Policy and doctrine often lag technology by years, particularly as artificial intelligence and software capabilities evolve rapidly. Industry, he said, therefore has a responsibility to act as an honest broker and deliver what warfighters need today while government works to modernize outdated policies.
Taylor also stressed the shortage of software engineering expertise and encouraged younger professionals to continuously learn, ask questions and develop skills beyond formal military training. Because the department cannot secure or modernize everything simultaneously, leaders must identify critical mission threads and model their hardware, software, data flows, vulnerabilities and single points of failure. He cited nuclear command, control and communications as an example of a mission whose architecture must be thoroughly understood and protected.
Asked about operating in contested environments, Taylor argued that the department has foundational problems even in permissive environments. Rapidly fielded capabilities-accelerated during COVID-19 and by demands for greater connectivity aboard ships-sometimes introduced vulnerabilities without fully considering consequences. Speed must therefore have both magnitude and direction: leaders need sufficient information to make deliberate decisions while moving quickly.
Finally, Taylor identified decision-making and organizational fragmentation as major barriers. The department suffers from "application fatigue" and "system fatigue," with too many stakeholders, tools and disconnected decisions. Strategy should drive applications and systems, not the reverse. Operational commands may not control acquisition dollars, but their time, expertise, mission priorities and warfighter feedback strongly influence investment. Taylor challenged industry to bring mature, secure solutions that solve real operational problems now rather than prototypes requiring months of additional development. He further emphasized that scarce resources require prioritization: security must receive attention commensurate with mission importance, even when that means delaying capabilities, finishing incomplete efforts and resisting the temptation to chase every technology.