When the satellite link drops, cargo plans and instructions from the office stop reaching the ship, maintenance records stop reaching the office, and because crew internet use rides on the same link, operational traffic and crew traffic hold each other up. This page is for the IT and fleet managers of shipowners and ship management companies, and it explains how the network on board, the office network, and the applications in the cloud are connected.
Why IT is different at sea
Four things set a ship apart from a branch office on land. The link runs over a satellite, latency is high, there is a data cap, and cost follows every megabyte. The ship stays far from shore for weeks. No IT technician is on board, so faults are handled remotely. Navigation and engine systems (operational technology, OT) must not sit on the same network as the crew's phones, yet a single link often carries everything.
Then there is the flag. Most Turkish-owned ships fly a foreign flag, and the flag state and the classification society decide which cybersecurity rules apply. So before building the network, find out which rule binds you.
The office side is a separate job. At the shipowner's head office, fleet, maintenance, and purchasing applications work on data from the ships, and when the ship link slows down, the people using those applications decide on incomplete data. That is why we design the network on board together with the office and the cloud.
Connectivity options on board
You get the link from a service provider authorized by BTK; we build the network on top of the links. The table compares the technologies by general characteristics and gives no speeds or prices.
| Technology | General characteristics | Role in the network design |
|---|---|---|
| GEO VSAT (Ku and Ka band) | High-orbit (GEO) satellite at a fixed position, reached with a small antenna terminal (VSAT); wide coverage, relatively high latency | Common primary link |
| LEO satellite | Low orbit (LEO); lower latency. Coverage and authorization in Türkiye vary by service | Primary or second link, once its authorization status is confirmed |
| L-band satellite link | Small terminal, wide coverage, low data rate | Backup and safety link |
| 4G/5G near shore | Works only close to the coast or in port; data cap and unit cost are lower than satellite | Large transfers while in port |
Starlink and the situation in Türkiye
According to the sources we could reach, as of November 2026 Starlink does not hold BTK authorization in Türkiye. Statements by ministry officials reported in the press say either that the matter is not on the agenda or that talks are continuing, and we found no separate decision or announcement published by BTK. For use in Turkish territorial waters and ports, confirm the current status with your service provider and in BTK announcements.
Use outside territorial waters depends on the terms of your flag state and your service provider. Sources give different distances for the geographic limit, so we do not state one. We are not a reseller or partner of Starlink.
Multiple links and SD-WAN
SD-WAN is a network management method that uses several links together and steers traffic by measuring link quality. We put an SD-WAN-capable router and firewall on board and connect the links your service provider supplies. The router measures latency and packet loss continuously; when the primary link degrades, it moves traffic to the second link and returns when the link recovers.
To manage data caps and cost, we prioritize traffic: operations first (messages with the office, maintenance and cargo records, security updates), crew second. Crew video streaming does not run on the expensive link, and large updates and backup transfers wait until a cheap link is available. When the data cap is close to running out, the administrator gets a warning and the crew network is slowed by rule.
We test the failover settings on site with the ship's actual links; which link takes over at which threshold is written for each ship's link layout.
Network zones and untrusted networks
We recommend at least five network segments on a ship: navigation and communication, machinery and cargo, ship office and operations, crew, and guest or passenger. This layout rests on the zone logic of the International Association of Classification Societies (IACS) UR E26: in-scope systems are divided into security zones, only explicitly permitted traffic crosses a zone boundary, navigation and communication systems are not in the same zone as machinery and cargo systems, and wireless devices sit in a separate zone. IP interfaces of in-scope systems that open onto crew, administrative, and passenger networks are also within the rule's scope.
E26 and E27 apply to ships whose building contract was signed on or after July 1, 2024. For older ships they are not mandatory, but the same zone layout is good practice, and your flag state or class society may require it separately.
Networks outside the scope of E26 (such as crew and guest internet) count as untrusted networks, and the rule asks for them to be physically separated from the in-scope zones. We design to that requirement and limit crossings between zones with firewall rules; we use virtual LANs (VLANs) only inside networks of the same trust level. We hand over the zone diagram and an inventory of the devices in each zone as documents.
Connecting ship, office, and ARGE Cloud
Fleet management, maintenance, purchasing, and accounting applications usually run at the office or in the cloud, and the ship connects to them through an encrypted tunnel. We can run the applications on ARGE Cloud in a virtual private cloud (VPC) dedicated to you and connect the ship and the office to it. The satellite link is only the carrier under the tunnel; if you change the link, the tunnel and security rules stay the same.
For the connection between the shipowner's head office and its branches, we described the MPLS, SD-WAN-capable router, and IPsec options in the section on head office and branch connectivity.
Remote access: ARGE ZTNA
An engine manufacturer's service engineer or the technical superintendent at the office wants to connect remotely to a system on board. Under IACS UR E26, no IP address of an in-scope system is exposed to an untrusted network; communication uses an encrypted tunnel with endpoint authentication; remote access does not start until an authorized person on board explicitly accepts it, it can be ended from the ship, and every event is logged.
This is the part ARGE ZTNA covers: the user passes mandatory two-factor authentication (2FA) along with the password, only a registered device connects, the user is given only the permitted resource, every session and access decision is logged, and access is short-lived and can be revoked. Approval by an authorized person on board and ending the session from the ship are not offered as something the product does by itself; we design them together with the ship's firewall rules and a written procedure. We put what is covered and how in writing during discovery.
Rules and obligations
- International Maritime Organization (IMO) MSC.428(98) and the International Safety Management (ISM) Code: Cyber risks must be addressed in the ship management company's safety management system; the deadline is the first annual verification of the company's Document of Compliance after January 1, 2021.
- MSC-FAL.1/Circ.3: The IMO guidelines on maritime cyber risk management; check the IMO website for the current revision.
- IACS UR E26 and E27: Minimum requirements for network zones and system resilience on newbuilds; they apply to ships whose building contract was signed on or after July 1, 2024.
- Guidelines from the Baltic and International Maritime Council (BIMCO) and partners: The fifth edition of the guidelines on cybersecurity onboard ships, published in November 2024, is the industry's reference for putting this into practice.
- Türk Loydu: It has a cybersecurity guide and additional rules; if your class society is Türk Loydu, check the current rules.
- Turkish-flagged ships: The Turkish maritime administration may have separate requirements; confirm the current status with the administration.
The rules of your flag state and class society are what decide; ask them and your legal counsel which obligation applies to your ship. We build the network side of these rules and prepare their documents. We do not give legal advice.
Monitoring and backup
Because the link is narrow, monitoring traffic from the ship is kept small: link quality, data cap use, and device status are monitored centrally, and alerts go to your administrator. Monitoring hours and response scope are set out in the contract.
For backup we use an incremental method instead of full copies: the first full copy is taken over a cheap link while the ship is in port or near shore, and afterward only changed data is transferred. Backups are kept in the isolated backup zone on ARGE Cloud, and we test restores. Transfers are scheduled so they do not use up the data cap. A local copy of data held on a server on board also stays on the ship, so a restore can be done on board even if the link is down completely.
What we do and what we do not
We do not:
- Sell satellite links or subscriptions; we are not a reseller or partner of any link provider.
- Install navigation equipment or the Global Maritime Distress and Safety System (GMDSS).
- Give class approval; approval rests with the classification society.
We do:
- Design, install, and monitor the SD-WAN-capable router and firewall.
- Place the navigation and communication, machinery and cargo, office, crew, and guest networks in separate zones.
- Build the connection between ship, office, and ARGE Cloud.
- Open remote access with ARGE ZTNA.
- Set up monitoring and backup.
- Prepare the network zone diagram and asset inventory for readiness for an E26 class review.
- Supply the hardware through our multi-vendor procurement service.
The network layout for your situation
| Your situation | Layout we recommend |
|---|---|
| One link; work with the office stops when it drops | A second link on a different technology and an SD-WAN-capable router; automatic failover |
| Crew internet fills the operations link | A separate network segment, an operations-first rule, and a data cap limit |
| A supplier connects remotely to a machinery system | ARGE ZTNA with a registered device and a logged session; an explicitly defined allow rule at the zone boundary |
| Building contract signed on or after July 1, 2024 | E26 zone diagram and documents prepared from the start |
| Office applications use ship data | A VPC on ARGE Cloud; ship and office connect through encrypted tunnels |
Related services
- Firewall and endpoint security
- Infrastructure and security monitoring
- Backup and disaster recovery
- Corporate network
Frequently asked questions
Do you provide the satellite link? No. You get the link from a service provider authorized by BTK. We are not a reseller or partner of any link; we build the router, firewall, and network layout on top of the links.
Can I use Starlink in Turkish territorial waters? According to the sources we could reach, as of November 2026 Starlink does not hold BTK authorization in Türkiye, so using it in Turkish territorial waters is not authorized. Confirm the current status with your service provider and in BTK announcements. Use in international waters depends on the terms of your flag state and your service provider.
Are IACS E26 and E27 mandatory for my ship? They apply to ships whose building contract was signed on or after July 1, 2024. For other ships they are guidance, not a requirement, although your flag state or class society may require them separately. Ask your class society about your ship.
How do you separate crew internet from the operations network? Crew and guest networks count as untrusted networks. We give them their own segment and limit crossings between zones with firewall rules; on a ship within E26 scope, we reflect the physical separation the rule asks for in the design. We set a data cap and speed limit for crew traffic and give operations traffic priority.
Can VSAT, LEO, and 4G be used together, and what happens when a link drops? Yes; an SD-WAN-capable router manages the links together. When the primary link degrades, traffic moves to the second link and returns when it recovers. We write the rule for which traffic goes over which link according to data cap and cost. We measure the failover time on site and give it to you.
How can a supplier connect safely to a machinery system? The supplier connects through ARGE ZTNA: two-factor authentication, a registered device, only the permitted resource, and a logged session. We design the on-board approval and ending the session from the ship together with a firewall rule and a written procedure.
How is backup done on a ship when bandwidth is short? We take the first full copy over a cheap link while the ship is in port or near shore; afterward only changed data is transferred. Backups are kept in the isolated backup zone on ARGE Cloud. Transfers are scheduled for hours and links that do not use up the satellite data cap.
Which network documents are requested in an ISM audit? The auditor and the class society set the document list themselves. On the network side they usually ask for the zone diagram, the asset inventory, firewall rules, and remote access logs; we give technical support in preparing them. The audit decision rests with the flag administration or the organization it authorizes.