Naval Intelligence Division (Israel)

The Naval Intelligence Division supports Israeli Navy commanders with maritime intelligence and contributes naval expertise to the wider Israeli intelligence system. Its personnel build the Navy's maritime picture and may communicate directly with commanders in the field to help identify people they encounter.[1] Aman, the IDF's Military Intelligence Directorate, professionally guides the Navy's intelligence body alongside Air Force intelligence and the intelligence departments of the regional commands.[7]

Public sources describe the division's relationship with Aman differently across historical periods. Reuven Ashkenazi recalled that naval intelligence answered to both the Navy commander and the head of Aman, advising Aman on naval matters while receiving most of its resources from the Navy.[4] A 1988 account characterized the organization as semi-autonomous within military intelligence, with its personnel not ordinarily subordinate to the Director of Aman except when providing consultative assistance on naval matters.[8] A general reference work also describes Israel's military intelligence community as including "numerous tactical intelligence units maintained by the individual branches" of the IDF.[9]

Accounts from different periods indicate several recurring functions. In 1977, documented concerns included adversary naval order of battle, foreign maritime capabilities, seaborne threats, and targeting studies for naval gunfire, amphibious assaults, and commando operations.[8] In 2015, the division's commander described an annual process for prioritizing a "top five" list of emerging threats, with examples including torpedoes, naval mines, and enemy units capable of threatening Israeli assets.[5]

Sources trace Israeli naval intelligence to both the pre-state Palyam, the maritime branch of the Palmach, and a formal intelligence department established within the new Israeli Navy's Operations Branch in May 1948.[8][3] Palyam members had served as mates aboard ships carrying illegal immigrants before statehood, monitoring foreign captains; a later reference account described Palyam as the basis of Israel's first naval intelligence service.[8]

The first chief intelligence officer of the new department was Shimon Horn, supported by district intelligence officers in the south and north.[3] Its initial capabilities were severely constrained. Coastal observation posts reported passing vessels' descriptions, direction, distance from shore, speed, armament, and flags. Because the Navy's wider mission had not yet been settled, the department had difficulty directing collection toward more defined objectives.[3]

Information about enemy naval capabilities was frequently based on open publications and estimates rather than verified operational intelligence. On May 7, 1948, intelligence officer Pinhas Pik compiled a list of 42 Egyptian vessels by name, detailing their tonnage, dimensions, speed, engine power, armament, and crew size. He relied principally on international naval reference works, including Jane's Fighting Ships.[3] Published standard specifications did not confirm that each vessel actually carried the listed equipment or possessed the expected personnel and operational proficiency.[3]

In October 1948, naval intelligence was placed under the general intelligence service for security, censorship, and counterespionage matters, while the Navy retained responsibility for planning its own intelligence activity. The general service was to rank requests for aerial photography, and the Navy's intelligence officer was to participate in discussions about general intelligence priorities.[3]

Collection efforts soon extended beyond Israel's coastline. Shimon Horn coordinated with the Foreign Ministry's research department, sought naval information from overseas, and proposed placing agents in selected ports. Naval personnel were to be attached to the "Da'at" foreign stations for maritime matters. Proposals to use merchant shipping and seafarers as an intelligence network were also discussed, although at least one such proposal was not implemented.[3]

Preparations for Operation Horev brought closer coordination with the intelligence departments of the Air Force and the Southern Front. The Navy sought aerial photographs of enemy ports and ships, and from December 20, 1948, its intelligence work was summarized in a daily publication covering enemy ports, coastal and port defenses, vessels, armament, sailing schedules, and inspections of ships entering ports.[3]

A report on the department's structure was published on October 31, 1949. Command passed from Zvi Kohanovsky to Yaakov Fish, while Haim Rafaeli headed a tactical department containing research and foreign-fleets sections. The wider organization also included port, photography, hydrographic, and meteorological sections and issued periodic intelligence updates.[3]

The Herzl Institute's Navy-history project, initiated in 1993, conducted interviews through 2001 and preserves participants' recollections of nearly three decades of the Navy's early history.[10] Reuven Ashkenazi's testimony describes both improvised early collection and the branch's later transformation into a modern intelligence organization.

Ashkenazi recalled that in 1948–1950 Navy personnel recruited foreign ship captains visiting Haifa to bring back material, principally photographic negatives, from Alexandria and Port Said. He estimated that the effort lasted a year to a year and a half before a reorganization in Military Intelligence ended the Navy's independent activity and strengthened coordination through Aman.[4]

Ashkenazi returned to "Branch Yam 4" in 1958 as head of its collection section, gathering open and non-public material and coordinating with Aman to obtain collection priority for the Navy. He said the branch then depended heavily on Aman for information about adversaries, with the support available affected by personnel and funding.[4] After command and intelligence training, he took over the branch in 1963 and remained until 1971. He described it as encompassing field security, research, collection, photography, and drafting functions before it became the Intelligence Department.[4]

After the Six-Day War, Ashkenazi submitted a staff paper proposing the development of naval intelligence over the following ten to fifteen years. He recalled that the organization became nearly independent, moved from subordination to the head of the Navy Department to direct subordination to the Navy commander, and changed from an approximately 8 a.m.–5 p.m. working day into a continuous 24-hour operation.[4]

The branch established intelligence officers across Navy units to brief and train personnel and maintain maps and aerial photographs. Collection teams joined operational voyages near enemy coasts, monitoring communications and later radar activity to develop tactical and electronic intelligence.[4] It produced weekly selections on Arab navies, technical studies of weapons and electronics, and illustrated material on enemy tactics. At a French tactical training facility in Toulon, naval intelligence personnel played the opposing force and assessed whether Navy units applied the intelligence they had received.[4]

Ashkenazi also recalled that naval intelligence supported ten to fifteen operations beyond enemy lines during the War of Attrition, mainly in the Sinai–Egypt area, providing intelligence to maritime and land commanders and helping identify possible landing beaches.[4] In a separate testimony, Zvi Keinan recalled serving as a combat intelligence officer under Shimon Horn in 1948, collecting and distributing intelligence and identifying enemy vessels during a wartime aerial mission before reporting their position and direction by radio.[11]

A 1988 reference account provides a detailed snapshot of Naval Intelligence as it stood in 1977. It described a small, centralized service of approximately 110 personnel that supported naval units while remaining semi-autonomous within the wider military intelligence establishment.[8]

Six departments operated under the Deputy Director of Naval Intelligence: Organization and Administration, Security, Production, Targeting, Protocol, and Collection. Organization and Administration handled routine duties, while the Security Department, with about twelve staff, performed limited counterintelligence work at Navy headquarters and naval bases.[8]

The Collection Department had approximately seventeen employees and gathered intelligence through naval attachés, small-boat coastal operations, the merchant marine, and cooperation with Air Force Intelligence. The Production Department was the largest component, with about forty staff divided between Arab- and Soviet-navy specialties. It analyzed mobile naval forces in the Mediterranean, using information arriving at naval headquarters, including signals intelligence, and produced studies of enemy order of battle and special weapons.[8]

The Targeting Department had approximately twenty personnel in Egypt/North Africa and Syria/Lebanon divisions. Its duties included coastal studies for naval gunfire, beach studies for amphibious assaults, special studies for commando operations, and target folders on Lebanese, Syrian, and Egyptian ports.[8] These personnel figures and departmental arrangements apply specifically to 1977 and should not be read as a description of the division's current organization.

Published accounts since the early 2000s illustrate the division's analytical and operational-support functions. During the Karine A case in 2001, a small research unit studied the maritime forces of Hezbollah and Palestinian groups, combining material from different intelligence agencies and passing relevant findings to senior officers and operational forces. Its work was divided broadly between maritime terrorism and international shipping, including the tracking of suspicious vessels, ship purchases, and insurance.[12]

A young officer identified as Lieutenant Anat connected an August 15, 2001 report stating "We bought a ship" to a planned arms-smuggling operation. The account says she interpreted "house" as a code for a ship and "cars" as fishing boats intended to collect an Iranian weapons cargo near Alexandria and transfer it to Gaza. Analysts then spent months identifying the ship, its route, and its location.[12]

Brigadier General Hezi Meshita, then head of Naval Intelligence, coordinated collection priorities and relationships with Israeli and foreign intelligence agencies. He recommended intercepting the ship in the Red Sea because it might be lost if it reached the Mediterranean. American satellite and photographic-aircraft coverage helped locate the vessel and provided updates, although Meshita said Israel did not receive everything it requested.[12] Israeli monitoring used Ofek and commercial satellite services, while American coverage enabled more continuous tracking. After Shayetet 13 and the Air Force intercepted the ship in January 2002, investigators found 83 flotation containers holding 54 tons of weapons and related equipment.[13][12]

In 2015, the division's commander described its role in the IDF's "campaign between wars," which the report characterized as hundreds of covert operations far from Israel's borders, many involving naval forces. The division monitored arms transfers to Hezbollah and shipments into Syria, assessed their contents and military significance, and prioritized emerging threats.[5]

Detailed study of new weapons and their operational implications was described as a core function. The commander characterized Russian Yakhont coastal-defense missiles in Syria as a strategic threat to Israeli ports and offshore gas platforms and warned that they could potentially be transferred to Hezbollah. He also cited the C-704 missiles seized from the Gaza-bound Victoria in 2011 as an opportunity for analysts to examine a weapon physically alongside other intelligence methods.[5]

Naval Intelligence personnel may enter operational planning from one week to three months before a mission. Intelligence assessments can affect tactical choices when a unit commander requests one approach and analysts recommend another based on the threat picture, although final operational responsibility remains with the commander.[5]

A March 2026 Mako report described an operation against Iranian naval infrastructure in the Caspian Sea in which Naval Intelligence and Aman helped guide an Air Force attack. Researchers characterized the maritime area, located Iranian vessels and facilities, worked with joint Navy–Air Force teams on targeting and the required effects, and supported the operation in real time from the Air Force command center.[6]

In the 2024 Batroun operation, Israel Hayom reported that Naval Intelligence monitored Hezbollah operative Imad Amhaz from the end of 2021 and that an analyst proposed abducting him in September 2024. The division supplied Shayetet 13 with information about Amhaz and his routine, and its personnel monitored the raid from the Navy's command center during the night of November 1–2, 2024.[14]

Tracking seaborne weapons transfers has been a prominent documented function of Naval Intelligence since at least the early 2000s. The Karine A case demonstrated its ability to sustain a months-long analytical effort focused on a single smuggling vessel.[12]

The Israeli Navy subsequently intercepted the merchant vessel Francop on November 3, 2009, approximately 100 miles west of Israel, seizing weapons reported as destined for Hezbollah.[13] A Navy-wide overview separately lists producing and evaluating photographs of maritime space among the Navy's objectives and describes its air wing as including maritime reconnaissance aircraft operating from Ashdod and Haifa on the Mediterranean and Eilat on the Red Sea. The source does not assign those responsibilities specifically to the Naval Intelligence Division.[15]

The 2015 interview reported that Naval Intelligence had provided information and an assessment about Hamas's developing maritime commando capability two years before Operation Protective Edge. The Navy began developing the Aqua Shield seabed sensor system to warn of approaching divers, but the system was deployed only after the operation.[5] The commander argued that disputes over whether Hamas's force should be called a "naval commando" risked obscuring the threat, while distinguishing its capabilities from those of Israel's own naval commando unit.[5]

The division's operational significance lies in converting maritime collection and analysis into intelligence that commanders and combat units can use. It works closely with Shayetet 13, the Navy's special-forces commando unit, which operates at sea, on land, and in the air from its permanent base at Atlit.[15] Shayetet 13 specializes in maritime intelligence gathering, sea-to-land incursions, counterterrorism, sabotage, hostage rescue, and boarding. It was formed in 1948 by Yohai Ben-Nun from men drawn from the Palyam, and its existence was made public in 1960.[16]

The Karine A interception and the Batroun raid illustrate a recurring division of labor in which Naval Intelligence supplies assessments, target information, and real-time situational awareness while Shayetet 13 conducts the physical operation.[12][14] In the Batroun case, Unit 504, rather than Naval Intelligence, conducted the subsequent interrogation of Imad Amhaz.[14]

A 2025 INSS analysis offers broader recommendations rather than a description of the division's organization. It argues that maritime threats require dedicated analytical and research capabilities and that continuous naval presence can improve the quality and availability of intelligence, particularly in distant areas such as the southern Red Sea.[17]

The Naval Intelligence Division is designated N2 within the Israeli Navy's staff structure.[2] Public accounts identify its commanders at brigadier general or rear admiral rank. Brigadier General Hezi Meshita led the division during the Karine A operation in 2001–2002, while the commander interviewed by Ynet in 2015 was identified only as Brigadier General Y.[12][5]

Yuval Eylon was appointed head of the Israeli Naval Intelligence Division, identified by INSS as INI/N2, in December 2019. The profile places his appointment during an expanding confrontation over Iranian entrenchment in Syria and a developing Iranian naval challenge. At the end of his service in the post, he became head of the Navy's Operations, Plans, and Policy Division, N3, during Operation Guardians of the Walls.[2]

A separate 2024 INSS publication describes Eylon as having served for 30 years in Israeli Navy command and staff positions, with his last post rendered in English as "head of the Navy's Shipping Intelligence Division." The available sources do not clarify whether this is an alternative translation of the N2 post or a distinct organizational label.[18]

Several episodes and analytical questions associated with Naval Intelligence remain contested or depend on retrospective or attributed accounts.

Reuven Ashkenazi recalled that naval intelligence assessed in late April 1967 that the Egyptian Navy was ready for war before the June conflict. He also said that in 1973 an officer named Rami Luntz was the first, in his recollection, to identify that war was approaching rather than an exercise. Ashkenazi said these internal assessments were conveyed to Aman and were not publicly known at the time.[4] The claims are not independently corroborated by the other sources gathered here and reflect one officer's memory decades after the events.

A 2010 Ynet analysis of the Mavi Marmara flotilla interception criticized Naval Intelligence for failing to anticipate severe violence by a group aboard the vessel and described coordination with Aman's Research Division as deficient. It suggested possible explanations, including competing collection priorities, constrained resources, and caution about intelligence activity in Turkey, while arguing that these did not resolve all questions about the assessment. The criticism was journalistic analysis, not a finding identified by the source as the conclusion of a formal inquiry.[19]

Israel Hayom's description of the alleged Hezbollah "Secret Naval File," a project reportedly intended to develop a civilian merchant vessel for attacks, is attributed to Israeli Naval Intelligence personnel and military sources and is not independently corroborated in the gathered material.[14] Threat assessments and operational claims in the 2015 Ynet interview and the March 2026 Mako report should likewise be understood as attributed military assessments rather than independently verified conclusions.[5][6]