Archive for the 'Homeland Security' Category
By Mark Tempest
Join us at 5 pm (Eastern U.S.) on 21 April 2013 for our Episode 173: The War Returns to CONUS:
The events of the last week in Boston has brought back to the front of the national consciousness what, for the lack of a better description, is known as The Long War.
The threats we face are both domestic, foreign, and increasingly a mixture of both. Communication and transportation has created a breed of transnational threats that are not new, and whose causes, resources, and threat vectors are not as opaque as some may try to make them.
Starting out and working in, what are the lessons we should emphasize to mitigate the ongoing threat? As we continue in the second decade after 9/11/2013, what are we doing correctly, what still needs to be done – and what things are we wasting time and money on for little gain?
To discuss, our guest for the full hour will be Steven Bucci, Director, Douglas and Sarah Allison Center for Foreign Policy Studies at The Heritage Foundation.
Listen live at 5pm (or you can listen later) by clicking here.
By Mark Tempest
There is a fair bit of talk about the rush for the arctic for economic and strategic reasons – and where there is international interest on the seas, the nations involved need to think about what is the best way to secure their interests.
While the initial thought might be Navy – is the natural answer really the Coast Guard? If the USCG is the right answer, is it trained, manned and equipped for the job?
What does it need to do in order to fulfill its role – and why may it be the best answer to the question – who will show the flag up north?
Our guest this Sunday for the full hour from 5-6pm EST will be U.S. Naval War College Associate Professor James R. Holmes. As a starting point for our conversation, we will use his latest article in Foreign Policy: America Needs a Coast Guard That Can Fight: As the Arctic becomes an arena for conflict, the United States’ forgotten naval force will need to cowboy up.
Join us live or later by going to Midrats on BTR or picking up the show later from our iTunes page (lately there has been some delay in getting the show to iTunes, though, and the link may require iTunes).
In the Navy, our concept of an organization is dominated by the “chain of command” and the quintessential “org chart,” both of which are vertically focused. These concepts do a good job of telling us who we work for, and who works for us. However, they serve little purpose in outlining with whom we should work. These relationships are horizontal in nature and help us navigate the seams of an organization, seams which are readily apparent in a traditional, vertically-focused “org chart.” While vertical relationships are key to authority and responsibility, effective innovation, planning, and execution are typically dependent on horizontal relationships.
The Chief Petty Officers’ Mess is well known for establishing horizontal relationships. Chiefs utilize relationships established during CPO 365 and within the Chiefs’ Mess to solve problems and accomplish the mission. In essence, the effectiveness of the Chiefs’ Mess is based in large part on these horizontal relationships. These horizontal relationships need not be limited to the Chiefs’ Mess, however. Command members at all ranks, officer and enlisted, can and should seek to establish these relationships in order to make themselves and their command or organization more effective.
A good example is the somewhat recent emphasis on the N3/N2 (Ops/Intel) relationship, linking the operator to the intelligence professional, and vice versa. The result has been greater synchronization between these supporting entities. Another example is the establishment of the Information Dominance Corps (IDC), which seeks to establish a close working relationship between information-focused communities. Regardless of where these information-focused professionals work in an organization, a roadmap for their horizontal relationships has been pre-established by the formation of the IDC. The possibilities for horizontal relationships are truly endless, while the potential value in establishing and utilizing these relationships is immeasurable.
Establishing a horizontal relationship takes little effort. Warfare qualification programs, command functions, social events, and command organizations, such as the First Class Petty Officers Association, all encourage the establishment of horizontal relationships. Getting out of your work space and interacting with your peers is another method. Share each other’s roles and responsibilities and seek to identify overlap, and common or supporting efforts. Then establish a relationship and ensure you leverage it whenever necessary or feasible.
Horizontal relationships need not be limited to your own command or organization. Establishing relationships with other commands or supporting staffs can be beneficial as well. Horizontal relationships can also be established within a wider community, leveraging the collective thoughts of a large, diverse group. Tools like the IDC Self-Synchronization website enable establishment and utilization of such relationships.
So the next time you think about the chain of command or look at an org chart, focus on the horizontal vice vertical aspects of the organization. Identify the seams and look for places to establish horizontal relationships, relationships that will help make you and the command more effective. Then set out to navigate the seams.
LCDR Chuck Hall is an Information Warfare Officer and member of the Information Dominance Corps. He enlisted in the Navy in 1988 and served 13 years as a Cryptologic Technician (Interpretive) prior to commissioning as a CWO2. Subsequently selected for LDO, he transitioned to the Restricted Line once he completed his BA in Middle Eastern Studies. He currently serves on the CCSG-8 staff, embarked in USS DWIGHT D. EISENHOWER. When at home he enjoys spending time with his wife and three amazing children. He has also contributed to Connecting the Dots with his blog post Waiting to Lead.
Please join CDR Salamander and me on February 10, 2013 at 5pm Eastern U.S. for “Episode 162: Air Diplomacy, Air-Sea Battle, and the PAC Pivot”:
As we shift from ground combat in Asia and reset to a more natural position of a naval and aerospace power, are we thinking correctly on how to best leverage our resources and strengths?
How should we be using sea power and air power to create the right effects during peace, yet be poised to have the best utility at war? Are there concepts, habits, and systems that have had their time and should be moved aside for newer tools and ideas?
Our guest for the full hour will be Dr. Adam Lowther, Senior Fellow at the Center for the National Interest in Washington, DC.
He is the author of numerous books and articles on national security topics and previously served in the US Navy.
What happens when a global maritime power finds itself in a position where it can no longer sustain the global presence it once considered an essential requirement?
The US Navy has been in a period of decline in both numbers and capability for awhile, and as budgetary reality sets in and burn out starts to hollow remaining capabilities – the decline is set to continue for at least another decade.
How far the decline goes until stability sets in is unknown, but what is the best reaction to this reality? Are the lessons one can derive from history that can help policy makers shape direction and priority going forward?
Our guest for the full hour to discuss will be Daniel J. Whiteneck, Ph.D.
Dr. Whiteneck is a Senior Research Scientist at the Center for Naval Analyses. He has directed projects ranging from Tipping Point and the future of US maritime dominance, to the use of naval forces in deterrence and influence operations. He also led studies on naval coalition operations and maritime security operations focusing on counter-piracy and counter-proliferation.
Dr. Whiteneck deployed twice with Carrier Strike Groups for OEF and OIF. His CNA field assignments included two tours on numbered fleet staffs, as well as field representative to the Commander of NATO Joint Command Lisbon in 2004-05. He also did three tours in the Pentagon as CNA Scientific Analyst to N51, N31, and OPNAV DEEP BLUE.
He held academic positions at the Seattle University, the University of Colorado, and the Air Force Academy, before joining CNA. In addition to authoring a number of CNA studies over the past 14 years, he has published articles and book chapters on US and British global leadership and naval operations, NATO’s expansion and operations, and the role of conventional and strategic deterrence against terrorist networks and rogue states after 9/11.
The demands of the warfighter are like cheese processed through the lactose intolerant digestive tract that is military supply; though digestion is a vital process, it can be unspeakably painful and smell of rotten eggs. End-users already plagued by rapidly decreasing manning and time are now interrupted by long backorder lead times, artificial constraints on off-the-shelf solutions, and funding. Personnel are known to skip the supply system altogether, purchasing parts or equipment out of pocket when an inspection is on the line. This both hides the problem and takes from the pockets our sailors. The military has forgotten that supply exists for the utility the operator, not the ease of the audited. For the military supply system to regain the trust and capabilities necessary to serve the end-user, reforms to the way supplies are selected, commercial purchases are managed, and funding requested are necessary.
The first major problem is the Coordinated Shipboard Allowance List (COSAL). COSAL is a process by which the navy’s supply system determines what supplies it should stock on the shelves; items are ordered through the in-house supply system and the hits in the system raise the priority to stock. Unfortunately, COSAL is reactive rather than predictive and cannot meet the needs of either the new aches of an aging fleet or the growing pains of new ships. As ships grow long-in-the-tooth, parts and equipment once reliable require replacement or repair. New ships find casualties in systems meant to last several years. Equipment lists also change, leading to fleet-wide demands for devices only in limited, if any, supply. The non-COSAL items are suddenly in great demand but nowhere to be found. Critical casualties have month+ long wait-times for repairs as parts are back-ordered from little COSAL support. Commands attempt to fill their time-sensitive need by open purchasing these items from the external market, which are not COSAL tracked. This leads to either supply forcing the workcenter to order through supply and end-users waiting potentially months for critical backordered items, or the open purchase being accomplished and COSAL staying unchanged. Although difficult, the supply system should be more flexible to open-purchasing stock item equivalents due to time constraints while integrating open purchase equivalence tracking into the COSAL process. This bypasses the faults of COSAL’s reactionary nature while still updating the supply system with the changing demands.
The limitations on open purchasing (buying commercial off-the-shelf) create artificial shortages of material easily available on the street. Namely, when items are not under General Services Administration (GSA) contract, single vendor purchases or purchases for a single purpose cannot exceed $3,000, no matter how the critical need or short the deadline. This further exacerbates the problems from an unsupportive COSAL; if requirements exceed purchase limitations, requests are sent through a lengthy contracting process which wastes more time than money saved. The contracting requirement ignores the fact that from the work-center supervisor to the supply officer, everyone now has the ability to search the internet for companies and can compare quotes. Purchasers need not be encouraged to spend less money, since they have the natural deisre to stretch their budget as far as possible. Contracting opportunities also become more scarce as the end of the fiscal year approaches, since money “dedicated” to a contracting purchase is lost if the clock turns over and no resolution is found. This means money lost to the command and vital equipment left unpurchased. For deployed/deployable units, this can be unacceptable. The supply system exists to fulfill the operational needs of the training/deployed demand-side, not to streamline the risk-averse audit demands of the supply side. If not raising the price-ceilings of non-GSA purchases for operational commands, the rule against split purchasing by spreading single-type purchases across multiple vendors should be removed. Breaking out a single purchase amongst several vendors alleviates the risk that large purchases are being made to single vendors due to kick-backs. This would call for more diligence on the part of Supply Officers, but that is why they exist.
Finally, the recent Presidential Debates have shown the military’s poor ability to communicate the message that funding is becoming an increasingly critical issue force-wide. To many, the defense budget is so large that cuts are academic, savings no doubt hiding throughout the labyrinthine bureaucracy. However, for those of us who had no money to buy everything from tools to toilet paper for a month, it’s a more practical problem. Long before sequestration, Secretary Gates started the DoD on the path of making pre-emptive cuts before outside entities made those choices for the DoD. However, the military has made a poor show of communicating that these cuts have become excessive and are now cutting into the muscle of the force. Obeying the directive to cut funding does not require quietly accepting these cuts; now the Commander and Chief believes the military not even in need of a cut freeze, let alone a funding increase. With Hydra of manning, material, and training issues constantly growing new heads, the strategic communicators must come out in force to correct this misconception. While administrative savings can be found, our capabilities are paying the price for the budgetary experiment. Military leadership should, in part, involve advocacy; obedience requires the resources to execute the mission.
The supply system is a painful process, but with rather humble reforms, that pain can be both lessened and taken off the shoulders of whom the system exists to serve. With a reformed COSAL tracking open purchases, a loosened open-purchase limit that puts the stress on the supplier rather than operator, and better strategic communications about funding, we can apply a bit of lactaid to an otherwise painful process.
Much has been written of late about “Creating Cyber Warriors” within the Navy’s Officer Corps. In fact, three prominent and well-respected members of the Navy’s Information Dominance Corps published a very well articulated article by that very title in the October 2012 edition of Proceedings. It is evident that the days of feeling compelled to advocate for such expertise within our wardroom are behind us. We have gotten passed the WHY and are in the throes of debating the WHAT and HOW. In essence, we know WHY we need cyber expertise and we know WHAT cyber expertise we need. What we don’t seem to have agreement on is WHO should deliver such expertise and HOW do we get there.
As a proud member of both the Cryptologic Community and the Information Dominance Corps, I feel confident stating the responsibility for cultivating such expertise lies squarely on our own shoulders. The Information Dominance Corps, and more specifically the Cryptologic and Information Professional Communities, have a shared responsibility to “Deliver Geeks to the Fleet.” That’s right, I said “Geeks” and not “Cyber Warriors.” We don’t need, and despite the language many are using, the Navy doesn’t truly want “Cyber Warriors.” We need and want “Cyber Geeks.” Rather than lobby for Unrestricted Line status, which seems to be the center of gravity for some, we should focus entirely on delivering operational expertise regardless of our officer community designation.
For far too long, many people in the Restricted Line Communities have looked at the Unrestricted Line Communities as the cool kids in school. Some consider them the “in-crowd” and want to sit at their lunch table. Some think wearing another community’s warfare device validates us as naval officers and is the path to acceptance, opportunity, and truly fitting in. We feel an obligation to speak their language, understand the inner workings of their culture, and act more and more like them. Some have grown so weary of being different or considered weird that many would say we’ve lost our identity. Though establishment of the Information Dominance Corps has revitalized our identity, created a unity of effort amongst us in the information mission areas, and further established information as a legitimate warfare area, many continue to advocate that we are lesser because of our Restricted Line status. We seem to think we want and need to be Unrestricted Line Officers ourselves. Why? Sure, we would like to have direct accessions so that we can deliberately grow and select the specialized expertise necessary to deliver cyber effects to the Fleet. Yes, we would like a seat at the power table monopolized by Unrestricted Line Officers. And yes, we would appreciate the opportunity to have more of our own enjoy the levels of influence VADM Mike Rogers currently does as Commander, Fleet Cyber Command and Commander, U.S. TENTH Fleet.
But there is another path; a path that celebrates, strengthens, and capitalizes on our uniqueness.
In the private sector, companies are continually racing to the middle so they can appeal to the masses. It’s a race to the bottom that comes from a focus on cutting costs as a means of gaining market share. There are, however, some obvious exceptions, my favorite of which is Apple. Steve Jobs was not overly interested in addressing customers’ perceived desires. Instead, he anticipated the needs of the marketplace, showed the world what was possible before anyone else even dreamt it, and grew a demand signal that did not previously exist. He was not interested in appealing to the masses and he surely wasn’t focused on the acceptance of others in his industry. He was focused on creating unique value (i.e. meaningful entrepreneurship over hollow innovation), putting “a dent in the universe,” and delivering a product about which he was personally proud. We know how this approach evolved. The market moved toward Apple; the music, movie, phone, and computing industries were forever changed; and the technological bar was raised with each product delivered under his leadership. Rather than lobby for a seat at the table where other leaders were sitting, he sat alone and watched others pick up their trays to sit with him. Even those who chose not to sit with him were looking over at his table with envy, doing their best to incrementally build on the revolutionary advances only he was able to realize.
Rather than seek legitimacy by advocating to be part of Team Unrestricted Line, we ought to focus on delivering so much value that we are considered a vital part of each and every team because of our uniqueness. I am reminded of a book by Seth Godin titled “We Are All Weird.” In it he refers to “masses” as the undifferentiated, “normal” as the defining characteristics of the masses, and “weird” as those who have chosen not to blindly conform to the way things have always been done. For the sake of argument, let’s consider the Unrestricted Line Officers as the masses, those considering themselves “warfighters” as the normal, and the Information Dominance Corps as the weird. I say the last with a sense of hope. I hope that we care enough to maintain our weirdness and that we don’t give in to the peer pressure that could drive us to lobby for a seat at what others perceive to be “The Cool Table.” By choosing to be weird and committing more than ever to embrace our geekiness, the table perceived to be cool will be the one at which the four Information Dominance Communities currently sit. It won’t happen by accident, but it will happen, provided we want it to happen. Not because we want to be perceived as “cool,” but because we are so good at what we do, and we deliver so much unique value to the Navy and Nation, that no warfighting team is considered complete without its own personal “Cyber Geek.”
I sincerely respect the opinions voiced in the article to which I referred earlier in this post. However, I think we are better than we give ourselves credit for. Let’s not conform, let’s create. Let’s not generalize, let’s specialize. Let’s not be normal, let’s be weird. Let’s choose to be Geeks.
CDR Sean Heritage is an Information Warfare Officer who is currently transitioning from Command of NIOC Pensacola to Staff Officer at U.S. Cyber Command. He regularly posts to his leadership-focused blog, Connecting the Dots.
Over the past few weeks, senior military leaders and intelligence officials have publicly acknowledged the growing threat from foreign military forces to the US homeland. This may seem unrealistic given the overwhelming military advantage the United States has over any other nation’s military, but there are plausible scenarios where the US homeland could be vulnerable to attack, particularly during periods of US military operations overseas.
Before examining emerging threats that may place the security of the homeland at risk, one must first consider the complex problem of escalation. According to RAND, escalation can occur in several forms: vertical, horizontal and political. Escalation can also be carried out through conventional or asymmetric means. Certainly, attacks can be executed in the future to create a more complex hybrid escalation event. The US Military has already encountered the challenges posed by escalation during Operation Desert Storm.
As Iraqi President Saddam Hussein faced the reality of an overwhelming coalition force, he decided to use his over-matched military assets to attack civilian population centers in Israel. He also ignited oil fields in Southern Iraq in order to inflict environmental damage and to restrict coalition military movement. These are examples of horizontal and political escalation, respectively.
In discussing the new DOD Strategic Guidance, Dr. Janine Davidson recently noted that adversaries will likely go asymmetric and irregular to counter a US military advantage. This implies the US homeland will likely be in play should military force be used in the future. US military leaders and policy makers have not had to contend with this reality since World War II.
A host of legal/policy concerns, such as the Posse Comitatus Act and the imposition of wide-spread martial law, would challenge conventional thinking given these scenarios. An effective response would demand an unprecedented level of coordination and integration of Title 10 and Title 32 military forces with federal, state, and local law enforcement personnel. Some scenarios would likely have local law enforcement personnel performing ad hoc para-military operations. A significant military response within the homeland would certainly stress civil-military relations and threaten the civil liberties of US citizens, particularly those of certain ethnic groups associated with the adversary. Could this lead to increased radicalization or even threaten internal stability?
Current military capabilities that could be used to attack the US homeland include:
- Conventional attacks enabled by emerging technology
- Special Forces conducting direct action –Mumbai style attacks
- Weapons of Mass Destruction
- Improvised Explosive Devices
- Cyber Attacks
- Psychological Operations
- Economic Attacks
While these capabilities alone or in aggregate would certainly not defeat the US military, they can inflict damage to the homeland that would cause public support for military operations to either wane or force the military to take more aggressive action than would normally be prudent. Homeland attacks would also impose a significant cost imposition on the US, which would divert scarce resources away from other military operations.
Considering the prolonged military operations over the last decade, would US popular support for the wars in Iraq and Afghanistan have lasted as long as they have if US citizens were being killed in the homeland? In the future, would direct support for a critical ally, say Israel or Taiwan, withstand foreign military operations on the homeland or would US citizens demand military operations cease, as witnessed in Vietnam or Iraq?
Having to fight a two Combatant Command (COCOM) war has not been experienced by the modern US military since the National Security Act of 1947 established our current organizational structure. This scenario would provide an enormous challenge to coordinate and integrate operations between multiple COCOMs. An example the US could use as a precedent was having to respond to hurricane Katrina, while fighting limited wars in Iraq and Afghanistan. However during these events, leaders were not faced with command and control challenges or limited military resources. This would certainly not be the case in military operations against a near peer competitor.
The so called American way of war ensured the security of US interests over the past sixty years by taking overwhelming military force to the enemy’s doorstep. Unfortunately, the US will not be afforded that luxury in the future. Our nation’s military and civilian leaders must incorporate defending the homeland into their decision making calculus should military action be realistically considered in the future. The US public must also be aware that the decision to use military force will likely affect the livelihood of each American citizen in ways Americans have not witnessed during this generation.
The plausible scenarios associated with future wars will radically challenge our current perception of complex operations and will make the wars fought over the last 10 years seem like child’s play. The results of past operations speak for themselves and future wars will be even more complex and will demand a far greater level of strategic thinking and adaptation by both military and civilian leaders.
Robert Kozloski is a program analyst with the Department of the Navy and the author of “Rethinking Threats to The Homeland: Considerations for the Joint Force” currently under review at Joint Forces Quarterly.
Join us on Midrats for Episode 140: NORTHCOM and Disaster Response:
Everyone knows CENTCOM, many know PACOM or EUCOM … but what about NORTHCOM?
What is their role in national defense, and what special role does it have inside the United States – specifically in disaster response?
This Sunday, September 9th from 5-6pm EST, our guest for the full hour to discuss this and more will be Brigadier General Donald A. McGregor, the Deputy Director of Operations for Domestic Operations, Headquarters, United States Northern Command, Peterson Air Force Base, Colorado.
USNORTHCOM’s civil support mission includes domestic disaster relief operations that occur during fires, hurricanes, floods and earthquakes. Support also includes counter-drug operations and managing the consequences of a terrorist event employing a weapon of mass destruction.
NORTHCOM has been busy with forest fires, hurricanes and a whole lot more as it works with civilian agencies in the disaster area. Because hurricane season continues, earthquakes never stop and who knows what else can happen on a major level, this is a timely topic.
Russia has been increasing the reach of its navy in recent years, sending warships further afield as part of an effort to restore pride project power in a world dominated by the U.S. military.
That throws a wrench in our Maritime Strategy, it would seem. Or does it? What should our reaction be, militarily? And what, diplomatically? Should there be any?
- On Midrats 29 March 15 – Episode 273: Partnership, Influence, Presence and the role of the MSC
- The Pen and the Sword: An Interview with Professor Timothy Demy on Reading Fiction and Studying War
- On Midrats 22 March 2015 – Episode 272: Naval Professionalism; up, down, and back again – with Will Beasley
- Missile Defense and Budget Issues
- On Midrats 3/15/15 – Episode 271: “Red Flag and the Development USAF Fighter “