Showing results for 
Search instead for 
Did you mean: 
Create Post

The Army's march forward means letting go of the past

Level 11

Not to be outdone in the race for federal network modernization, the United States Army last year issued the Army Network Campaign Plan (ANCP). Created by Lt. Gen. Robert Ferrell, the Army’s outgoing director, the ANCP “outlines current efforts that posture the Army for success in a cloud-based world” and provides “the vision and direction that set conditions for and lay a path to Network 2020 and beyond.”

These broad and bold statements encompass several things. First, there’s the Army’s desire to create a network that aligns with DISA’s Joint Information Environment (JIE) and the Defense Department’s modernization goals, which include better insight into what’s happening within its networks and tighter security postures. Second, there’s the pressing need to vastly improve the services the Army is able to deliver to personnel, including, as outlined in the ANCP, everything from “lighter, more mobile command posts to austere environments that will securely connect the network and access information.”

How unifying operations and security fits into the ANCP

The need for greater agility outlined in the ANCP dictates that operations and security teams become more integrated and unified. The responsibilities of one can have a great impact on the other. Working together, cybersecurity and operations teams can share common intelligence that can help them more quickly respond to threats and other network problems.

Similarly, the solutions that managers use to monitor the health and security of their networks should offer a combination of features that address the needs of this combined team. As such, many of today’s network monitoring tools not only report on the overall performance of the network, but also provide indications of potential security threats and remediation options.

Why letting go of the past is critical to the success of the ANCP

Combing operations and security teams is a new concept for many organizations and it requires letting go of past methodologies. The same mindset that contributes to that effort should also be applied to the types of solutions the Army uses moving forward, because the ANCP will not be successful if there is a continued dependence on legacy IT solutions.

It used to be fine for defense agencies to throw their lots in with one software behemoth controlling large segments of their entire IT infrastructure, but those days of expensive, proprietary solutions are over. Army IT professionals are no longer beholden to the technologies that may have served them very well for the past few decades, because the commercial market for IT management tools  now has lightweight, affordable, and easy-to-deploy solutions. The willingness to let go of the past is the evolution of federal IT, and is at the heart of all modernization efforts.

The fact that Ferrell and his team developed a plan as overarching as the ANCP indicates they are not among this group of IT leaders. In fact, the plan itself shows vision and a great desire to help the Army “be all it can be.” Now, the organization just needs to fully embrace new methodologies and technologies to reach that goal.

To read the extended article on Defense Systems


The talk of JIE is really more of a wait and see type of scenario.  Organizations  are taking a backseat before diving in head first.  Not sure if JIE will ever happen but it does provide some good discussion points.  


I hope they hit their targets with this plan. It sounds like a great improvement.


It should be an improvement over what they have....provided they do it right.

Level 11

You have first rate people serving, of course you need a first rate network.  Army personnel will not have a problem with the coming changes, they always adapt to the situation and overcome any obstacles. hooah!

Level 14

Still holding a wait and see attitude.

The title of this blog post: "The Army's march forward means letting go of the past", doesn't apply to just their IT framework. Also, you can insert thousands of "brick 'n mortar" -type companies into that title and the same rules apply. Dependencies, requirements, etc. can all get so messy when trying to free yourself from the constraints of underlying infrastructure.

As they move forward I hope they keep in mind lessons that should been learned in the past.  For example, during Desert Storm the military used 802.11b without encryption for mobile communications and monitoring, and the opposition was able to access the same information and use it against us.

When I heard the Center For Disease Control doesn't allow any wireless at all for their network, I was encouraged with their obvious acceptance of the vulnerabilities of wireless.

Level 20

Also the idea of increasing sharing of intelligence, security, and moving to some "cloud" not in your control all sometimes conflict with each other... I know our customers wouldn't probably be ok with us outsourcing our infrastructure to anyone...  It's the cloud not owned by you part I see a lot of problems with.  Everyone wants to save money but where do you draw the line with the risk part?


Once in a while I get asked by a non technical friend about ways to secure their data and in almost every case they are running wifi that is either unencrypted or easily broken.  People do not appreciate the easy breezy nature of wireless communications comes with some significant risks.

Level 15