One Sensitive Source and the Soviet Navy's Fear of Small Boats

By Vera Kessler ·

Kept secret for decades, a 1987 CIA memorandum exposes the paranoid defensive posture of the Red Fleet and the high-stakes breach that delivered its rulebook to Langley.

A single misplaced mine in a harbor throat or a handful of combat swimmers in a dry dock can paralyze an entire fleet, turning billion-ruble warships into floating targets. For the Soviet Navy, the maritime service branch of the Soviet Armed Forces that spent the Cold War attempting to project power against NATO, this vulnerability was a source of systemic anxiety.

On April 30, 1987, the CIA distributed a translation of the Soviet Navy's secret combat regulations. The memorandum, addressed to the Director of Central Intelligence—the head of the agency and principal intelligence advisor to the president—did not just deliver technical data; it delivered the internal logic of the enemy's fear. The record, an "Intelligence Information Special Report," consists of a translation of Chapters 10 and 11 of a manual published in 1983 by the USSR Ministry of Defense, the government ministry that supervised the Soviet Armed Forces.

The Ghost in the Printing House

The document describes the translation as the "eighth report in the series," based on a 12-chapter book classified SECRET by the Soviets. It was printed by the Moscow Military Publishing House, an entity the record identifies only as the publisher of these regulations, with no further details on file. The CIA warns that the source of this report is "extremely sensitive," demanding a strict need-to-know restriction within recipient agencies.

If this file is shaped the way it looks, the desk's reading is that the "sensitive source" was not a signals intercept or a recovered briefcase, but a high-level human asset embedded deep within the USSR Ministry of Defense or the Moscow Military Publishing House. The physical possession of a printed, SECRET regulatory manual—and the accompanying warning about the source's sensitivity—suggests a mole with access to the very ink and paper of the Soviet state's strategic intentions.

There is a glaring four-year gap between the 1983 publication of the manual and the 1987 memorandum. The pattern suggests the CIA practiced a "slow-bleed" distribution of the material. By dripping the chapters out in a series of reports rather than a single dump, Langley could manage the asset's cover and avoid alerting Moscow to the exact nature and timing of the breach. The Americans didn't just want the manual; they wanted to keep the man who gave it to them alive.

The Geometry of Paranoia

Chapter 10 of the regulations, "Combat Actions to Defend Basing Areas and Sea Lines of Communication," reveals a Navy obsessed with the "near zone." The Soviet Navy did not view its bases as safe havens but as battlefields in waiting. To prevent strikes from the sea, air, and land, the regulations establish a concentric defense: a "far zone" to detect and disrupt, an "intermediate zone" to destroy submarines and small combatants, and a "near zone" to eliminate everything from "smart bombs" to "combat swimmer forces" (record, page 9).

This defensive posture required a desperate level of inter-service cooperation. The Soviet Navy, operating in the USSR—the transcontinental Marxist-Leninist state that spanned Eurasia—could not defend its coasts alone. The record shows they relied on the Ground Forces, the land-based military branch, to provide motorized rifle units for coastal defense, and the Air Defense Forces, the aerial warfare branch responsible for protecting Soviet airspace, to provide long-range surface-to-air missile complexes (record, page 8).

The irony is that while the manual describes a seamless integration of Army, Air, and Navy, it betrays a profound distrust of the ocean. The regulations mandate the creation of no fewer than two systems of fairways—one operating and several alternates—linked by "connecting fairways" to ensure ships could escape their bases even if the primary channels were mined (record, page 11). When time was too short for reconnaissance, the regulations ordered ships to exit "by guiding them behind sweeps" or to simply blow up minefields with underwater explosions of line charges and aerial bombs, accepting the risk that the remaining mines might still damage their own hulls (record, page 11).

The Fantasy of the Manual

Chapter 11 deals with the "Basing and Rebasing (Redeployment) of Large Units and Units." It defines a rigid hierarchy of ports: main basing points, dispersal basing points, and maneuver basing points. On paper, it is a masterpiece of bureaucratic organization. In practice, it is a map of fragility.

The desk's reading is that a significant gap existed between these theoretical combat regulations and the actual operational capabilities of the Red Fleet in 1987. Soviet military bureaucracy was notorious for producing prescriptive ideals—manuals that described how the military should work in a perfect world—while the material reality was one of equipment failure and crumbling readiness. The manual describes "automated control systems" and "special technical support," but it cannot account for the corruption and inefficiency that plagued the Soviet rear services.

Furthermore, the CIA's selection of what to translate is telling. The Table of Contents shows a "Chapter 3: Political Work," the ideological machinery used by the Communist Party to ensure loyalty within the ranks. The CIA ignored it. They didn't care about the Soviet Navy's ideological purity; they cared about its plumbing. By prioritizing the "Defense of Basing Areas" and "Redeployment" over the political apparatus, the intelligence community signaled that it viewed the Soviet Navy not as a political instrument, but as a logistical problem to be solved.

The Logic of the Breach

The record we have is raw intelligence data—a translation stripped of its analytic assessment. The CIA sent this to the Joint Chiefs and the Director of Naval Intelligence, men who didn't need a linguistic transcription; they needed a target list. The translation was the raw material for a broader strategy of deterrence: knowing exactly how the Soviets planned to protect their harbors meant knowing exactly how to break them.

If the pattern holds, the still-withheld pages of this series likely contain the specific coordinates and vulnerabilities of those "main basing points" and "dispersal points." The CIA provided the rulebook, but the subsequent analytic products—the ones that never hit the FOIA reading room—provided the kill chain.

The desk's reading is that the Soviet Navy's reliance on these rigid regulations was its greatest weakness. By codifying their defensive zones and fairway systems in a SECRET manual, they created a predictable script. The moment that manual landed on a desk in Langley, the Soviet Navy ceased to be a mysterious threat and became a scheduled event. The high-level asset in Moscow didn't just hand over a book; he handed over the blueprint for the Red Fleet's paralysis, ensuring that in the event of a hot war, the Soviet Navy would find its "alternate fairways" already mapped and its "near zones" already compromised. The cost of this breach was paid in the currency of Soviet security, bought and paid for by a man who decided that the future belonged to the West.

Sources

  1. COMBAT REGULATIONS OF THE SOVIET NAVY: THE DEFENSE OF BASING AREAS AND SEA LINES OF COMMUNICATION AND THE BASING AND REBASING (REDEPLOYMENT) OF LARGE UNITS AND UNITS — CIA FOIA Electronic Reading Room
  2. CIA Analysis of the Soviet Navy collection — CIA FOIA Reading Room
  3. Document PDF (COMBAT REGULATIONS OF THE SOVIET NAVY: THE DEFENSE OF BASING AREAS AND SEA LINES OF COMMUNICATION AND THE BASING AND REBASING (REDEPLOYMENT) OF LARGE UNITS AND UNITS)
  4. Background: United States Navy — Wikipedia