Port cyber security in India: what DGMA Circular 46 asks of ports

DGMA Circular 46 of 2026 puts cyber risk into the PFSA and PFSP. What is advisory, what CERT-In already requires, and what evidence to keep per port system.

Ahuva Electronic Technologies · Published

Key points

  • DGMA Circular 46 of 2026, dated 4 August 2026, advises port facilities to add cyber risk to the port facility security assessment (PFSA) and to carry the resulting measures into the port facility security plan (PFSP).
  • The circular is advisory. Its operative paragraphs say 'may', 'should', 'are encouraged' and 'strongly advocated'. It does not use 'shall' or 'must', and it sets no deadline, penalty or reporting form.
  • Paragraph 5 names the areas to look at first: access control and identification, CCTV and surveillance, cargo and terminal operating systems, vessel traffic and communication systems, remote access, third-party vendors, and data storage and networks.
  • The binding duties come from elsewhere. CERT-In's directions of 28 April 2022 require listed incidents to be reported within 6 hours and ICT logs to be kept for a rolling 180 days.
  • The circular lists no evidence. The table on this page is our own mapping from each circular item to port systems and to records an auditor could reasonably ask to see.
  • Circular 54 of 2026, on cybersecurity awareness training, is listed under IT & E-Governance. Its title covers workspace, mobile and email security habits. Treat it as staff training, not as a port requirement.

What does DGMA Circular 46 of 2026 ask port facilities to do?

DGMA Circular 46 of 2026 asks port facilities to treat cyber risk as part of port security under the ISPS Code. The Directorate General of Maritime Administration issued it on 4 August 2026 under file number 25-59011/1/2023-MSB. It has 10 paragraphs and was issued with the approval of the Competent Authority.

The reasoning comes first. Paragraph 1 says cyber threats have emerged as a potential source of security incidents. Paragraph 2 says ports now rely on IT and operational technology (OT), including terminal operating systems, cargo handling systems, vessel traffic management systems, access control, surveillance and communication networks. Paragraph 3 lists the threats: unauthorised access, malware, ransomware, phishing, remote access weaknesses, third-party access and compromise of connected systems. The remaining paragraphs set out what a port facility may do.

  • Assess (paragraph 4): include cyber risk in the PFSA, covering critical cyber assets, vulnerabilities, threat vectors and impacts, and run periodic vulnerability assessments with timely fixes
  • Focus (paragraph 5): give particular consideration to named system areas, separate IT from OT, and set cyber requirements for vendors and contractors
  • Plan (paragraph 6): carry mitigation measures into the PFSP, and test backup, recovery and business continuity
  • Prepare people (paragraph 7): build PFSO awareness, name an officer or function for cyber risk, and run awareness sessions, drills and simulations
  • Respond (paragraph 8): set procedures for incident reporting, response, containment and recovery, and review measures over time
  • Refer (paragraph 9): use published guidance, including the IAPH port guidelines, IMO Resolution MSC.428(98) and MSC-FAL.1/Circ.3
  • Govern (paragraph 10): set up a mechanism like the DGS one, built around a Chief Information Security official, with certification or audit

Is DGMA Circular 46 advisory or binding?

DGMA Circular 46 is advisory. Every operative paragraph uses advisory wording, and the document never says 'shall' or 'must'. It also sets no deadline, names no penalty and asks for no report back to DGMA.

Three parts are worded more firmly than the rest. Paragraph 7 says PFSOs 'should possess adequate awareness' of cyber risk, paragraph 8 says measures 'should be periodically reviewed', and paragraph 10 says a similar institutional mechanism in all port facilities is 'strongly advocated'. On their wording, these are still recommendations, not duties.

The port security rules do not fill that gap yet. The word 'cyber' does not appear in the Merchant Shipping (Ships and Port Facility Security) Rules, 2026 (G.S.R. 909(E)). Rule 18(5) does require the PFSA to include 'identification and evaluation of important assets and infrastructure requiring protection', but it does not say whether digital systems count. The Bureau of Port Security Rules, 2026 list cybersecurity only as a topic that BoPS security standards may cover, and as of 30 October 2026 we found none published. Our note on the BoPS rules covers those rules in full.

How strongly each paragraph of Circular 46 is worded
ParagraphSubjectExact wordingForce
4Cyber risk in the PFSA'may consider incorporating'Advisory
4Vulnerability assessments'may also undertake'Advisory
5Named system areas'Particular consideration may be given'Advisory
5IT and OT segregation'may also be considered'Advisory
6Measures in the PFSP'may be incorporated, as applicable'Advisory
6Backup and recovery tests'may periodically test'Advisory
7PFSO awareness'should possess adequate awareness'Advisory, firmer wording
7Named cyber officer or function'may designate'Advisory
7Awareness sessions and drills'are encouraged to conduct'Advisory
8Incident procedures'may establish'Advisory
8Periodic review of measures'should be periodically reviewed'Advisory, firmer wording
10CISO-type mechanism, certification or audit'strongly advocated'Advisory, firmest wording

Which port systems does Circular 46 cover?

Circular 46 names categories of system, not products. Paragraph 5 lists access control and identification systems, CCTV and surveillance systems, cargo and terminal operating systems (TOS), vessel traffic and communication systems, remote access arrangements, third-party service providers and vendors, and data storage and network infrastructure.

Gate systems are not named. In our reading, a gate lane falls under two of those categories at once: access control and identification for the vehicle and driver, and cargo and terminal operating systems for the container and its data. A port that leaves the gate out of its cyber assessment because the circular does not say 'gate' would miss a system that touches both.

Paragraph 5 also reaches past the port's own staff. Cyber requirements 'may be considered' for service providers, vendors, contractors and personnel with access to critical systems. Where a port outsources maintenance, that covers the companies that maintain the cameras, the VTMS and the terminal software.

What evidence could an auditor ask for, system by system?

An auditor could ask for records that show each circular item was considered and acted on, but Circular 46 lists no evidence itself. The last column below is our suggestion, not an official checklist. Where a CERT-In or IMO document names the control, we cite it. Treat the table as a starting point to agree with your assessor.

Circular 46 items mapped to port systems and possible audit evidence (our mapping)
Circular itemPort systems affectedEvidence an auditor could ask for
Para 4: cyber risk in the PFSAAll: TOS, VTMS, access control, CCTV, gateInventory of hardware and software with versions and patch level (CERT-In government guidelines 3.6); assessment showing the impact of each system's failure on security and operations
Para 4: periodic vulnerability assessments and timely fixesTOS, VTMS, access control servers, video servers, network devicesDated scan reports; a fix log with closure dates; signed risk acceptance for anything left open
Para 5: access control and identificationPass issue system, readers, controllers, biometric terminalsList of unique and privileged accounts; proof default passwords were changed; record of accounts closed for leavers (IMO guidelines 3.5, Protect .1 and .2)
Para 5: CCTV and surveillanceCameras, video recorders, video management system, video wallsNetwork diagram showing cameras in their own zone (CERT-In government guidelines 4.7.1); default credentials changed before use (4.17); stated footage retention period
Para 5 by our reading: gate systemsANPR, RFID, weighbridge, boom barrier, gate operating software, link to TOSList of gate interfaces and the accounts behind them; logs from the gate application; written procedure for running the lanes if the link to the TOS fails
Para 5: cargo and terminal operating systemsTOS, cargo handling systems, port community system linksData-flow map of external connections; review of privileged users; dated restore test of the TOS database
Para 5: vessel traffic and communication systemsVTMS, radar and AIS feeds, VHF, links to the ICCCInventory of every outside connection to the VTMS; diagram showing how an ICCC feed is separated; list of who can change configuration
Para 5: remote accessVendor VPNs, remote maintenance toolsRemote access tunnelled, encrypted and logged, with multi-factor authentication (CERT-In audit guidelines 2025); list of active vendor accounts
Para 5: third-party providers and vendorsMaintenance contractors, cloud and software vendorsContract clauses on security, right to audit and incident reporting (CERT-In government guidelines 8.2, 8.3); vendor audit report (8.4); software bill of materials (8.5)
Para 5: IT and OT segregation, data storage and networksCore network, firewalls, storage, OT networksZone diagram and firewall rule review; OT device networks segmented from IT (IMO guidelines 3.5, Protect .3); proof that cross-zone traffic is denied by default (CERT-In government guidelines 4.7.1)
Para 6: backup, recovery and business continuityTOS, VTMS, access control, video storageDated restore tests; business continuity and disaster recovery plans with test results (CERT-In government guidelines 3.5)
Para 6: protection of personal dataPass records, biometric data, visitor records, CCTV footageRecord of what personal data each system holds, who can reach it and how long it is kept
Para 7: awareness, named officer, drillsPFSO, security staff, control room operatorsWritten designation of the officer or function; attendance records; drill or simulation reports with actions closed
Para 8: incident reporting and reviewAll systems, security operations centre if one existsIncident procedure with the CERT-In 6-hour step; CERT-In point of contact on record; incident register; 180 days of logs; clocks synced to NIC or NPL time
Para 10: CISO role, certification or auditWhole port facilityAppointment order; cyber security policy; audit reports and the fix plan that followed

Which cyber rules already bind a port or terminal?

CERT-In's directions of 28 April 2022 are the clearest binding cyber rule for a port or terminal. They apply to service providers, intermediaries, data centres, body corporate and Government organisations. On a plain reading, a port authority is a Government organisation and a terminal company is a body corporate. These entities 'shall mandatorily report cyber incidents as mentioned in Annexure I to CERT-In within 6 hours of noticing such incidents or being brought to notice about such incidents'. They also 'shall mandatorily enable logs of all their ICT systems and maintain them securely for a rolling period of 180 days'. Circular 46 paragraph 8 suggests reporting procedures but sets no time limit. The CERT-In time limit of 6 hours applies either way.

Port operational systems are inside the reporting list. Annexure I of the directions includes attacks on 'Critical infrastructure, SCADA and operational technology systems and Wireless networks', and attacks on Internet of Things devices and associated systems. Non-compliance may invite punitive action under section 70B(7) of the IT Act. Our separate note on the CERT-In directions covers the details.

CERT-In has also issued two sets of guidelines that give the detail Circular 46 leaves out. The table shows where each document stands for a port.

Where each cyber document stands for an Indian port facility
DocumentStatusWhat it adds for a port
DGMA Circular 46 of 2026AdvisoryPuts cyber risk into the PFSA and PFSP; names the system areas
CERT-In directions, 28 April 2022Binding on the entities it names6-hour reporting; 180-day logs held within Indian jurisdiction; clock sync to NIC or NPL; a named point of contact
CERT-In Comprehensive Cyber Security Audit Policy Guidelines, version 1.0, 25 July 2025Stated as binding on empanelled auditors and on auditee entities covered under the relevant provisionsAuditees are expected to cover all ICT systems at least once a year; audit types include ICS and OT security testing; multi-factor authentication for remote access
CERT-In Guidelines on Information Security Practices for Government EntitiesExpected of government entities under central ministries, including public sector enterprisesNominate a CISO; internal audit at least once in 6 months; third-party audit at least once a year
IMO MSC-FAL.1/Circ.3/Rev.4, 28 May 2026Recommendations, primarily intended for shipsSix functional elements and a list of minimum controls

What does paragraph 10 of Circular 46 mean by certification and audit?

Paragraph 10 strongly advocates an institutional mechanism for cyber security in all port facilities, with certification or audit, but it names no scheme, auditor or standard. It points to DGS Office Order 133/2025 of 21 November 2025, where it says the Chief Information Security official's role is critical. We did not find that order in the DGMA listings we checked as of 30 October 2026, so we cannot say what it contains.

CERT-In's documents are the nearest published detail. The government entity guidelines tell senior management to nominate a CISO and give that person's details to CERT-In as point of contact. They also ask for a third-party security audit at least once a year and say CERT-In empanelled auditors may be used. A private terminal is not named in those guidelines, but can use them as a baseline.

An ISO/IEC 27001 certificate is not named in the circular. The IMO guidelines list that standard among additional references, and say the use of such references is at the discretion of users. A port should not assume a certificate alone answers paragraph 10.

How do the IMO cyber guidelines fit a port?

The IMO guidelines are useful to a port but were not written for one. Circular 46 paragraph 9 cites MSC-FAL.1/Circ.3 without giving a revision. The current text is Rev.4, dated 28 May 2026, and paragraph 2.3.1 says the guidelines 'are primarily intended for ships'. Paragraph 4.4 says to use the most current version of any guidance.

Rev.4 still helps, for three reasons. Its Identify element covers ship and port interfaces. Its list of further guidance includes the IAPH Cybersecurity Guidelines for Ports and Port Facilities. And its six functional elements (Govern, Identify, Protect, Detect, Respond and Recover) give a port a ready structure for the cyber part of a PFSA. Paragraph 3.5 calls the listed controls 'the minimum controls that should be implemented'.

Resolution MSC.428(98), adopted on 16 June 2017, is about safety management systems under the ISM Code, which is a ship-side regime. It recognises ports and port facilities as stakeholders, but it puts no duty on them.

  • Designate a person or entity accountable for cybersecurity activities
  • Keep an inventory of digital systems, with dependencies and network connections
  • Use unique credentials, separate privileged accounts, and change all default passwords
  • Segment OT device networks from IT networks, and collect and securely store logs
  • Run annual basic cybersecurity training for all employees, and OT-specific training for OT users
  • Keep records of cyber incidents and carry out root cause analysis

Does DGMA Circular 54 of 2026 apply to ports?

DGMA Circular 54 of 2026 should not be read as a port requirement. The listing, dated 1 September 2026, gives its title as 'Cybersecurity Awareness Training on Physical & Workspace Security, Mobile Security and Email Security Habits'. It sits under IT & E-Governance, not under the Nautical Wing that issued Circular 46. Nothing in that title points to port facilities.

For port staff, the training duty to work from is Circular 46 paragraph 7, along with the annual training that IMO Rev.4 lists.

How should a port add cyber risk to its PFSA and PFSP?

A port should get cyber risk into the next PFSA review first, then route any change to the plan for approval. Circular 46 sets no method, so the order below is our suggestion. It follows paragraphs 4 to 8 of the circular.

The PFSO does not run the PFSA alone. Rule 18(1) of the 2026 security rules says the PFSA 'shall be carried out by the designated authority or recognised security organisation', and the designated authority is now BoPS. Rule 19(1) says the plan 'shall be prepared and implemented by the port facility security officer'. So the PFSO's job on the assessment is to supply the system facts and press for cyber to be covered.

Plan changes carry a process step. Rule 19(4) says 'The designated authority shall approve the amendments made to the port facility security plan.' Rule 19(5) says the plan 'may be kept in an electronic format and shall be protected by procedures to prevent its unauthorised access, deletion, destruction, or amendment.' Network diagrams and system lists added for cyber purposes are sensitive, so keep them under the same protection.

  • List every system in paragraph 5 and name one owner for each, including the vendor who maintains it
  • Map the connections between systems: gate to TOS, VTMS to ICCC, cameras to the video platform, vendors to everything
  • Work out what happens to security and operations if each system is lost, altered or exposed, and give that to whoever carries out the PFSA
  • Run vulnerability assessments on critical systems and record what was fixed
  • Move the agreed measures into the PFSP and its procedures, and send the amendment for approval
  • Test restores and run one cyber drill with the security and IT teams together, then record the results

What is still unclear about Circular 46?

Several points in Circular 46 cannot be settled from the published record as of 30 October 2026. A port should write down how it has read each one, so that the reasoning can be shown later.

  • Whether a PFSA or PFSP reviewed by BoPS will be expected to include cyber content, given the circular's advisory wording
  • How paragraph 4 works now that rule 18(1) has the designated authority or a recognised security organisation carry out the PFSA, since the circular came before the 2026 rules
  • What DGS Office Order 133/2025 requires, and how much of it a port should copy
  • Which certification or audit paragraph 10 has in mind
  • Which publication paragraph 9 means by the 'Maritime Cybersecurity Assessment Guide', since it names no specific agency
  • Whether BoPS will issue binding cyber standards, and what they will say

How Ahuva approaches port cyber security

Ahuva's cybersecurity work covers network, endpoint and application security, SOC, SIEM and SOAR, NGFW, IDS/IPS, WAF and zero-trust, and VAPT and compliance. Ahuva holds ISO 9001:2015 and ISO 27001:2022 certification. Its first command control centre, in 2015, was a major port project with integrated security systems.

Frequently asked questions

Is DGMA Circular 46 of 2026 mandatory?
No. The circular is advisory. It uses 'may', 'should', 'are encouraged' and 'strongly advocated', never 'shall' or 'must', and it sets no deadline or penalty.
Does Circular 46 require cyber risk in the PFSA?
It advises it. Paragraph 4 says port facilities 'may consider incorporating' a cyber security risk assessment as part of the PFSA. Paragraph 6 says resulting measures 'may be incorporated, as applicable' in the PFSP.
Does Circular 46 cover terminal operating systems and VTMS?
Yes. Paragraph 2 names terminal operating systems and vessel traffic management systems. Paragraph 5 asks for particular consideration of cargo and terminal operating systems and of vessel traffic and communication systems.
How fast must a port report a cyber incident in India?
Within 6 hours of noticing it or being told of it, for the incident types in Annexure I of CERT-In's directions of 28 April 2022. That time limit comes from CERT-In. Circular 46 sets none.
Does a port need a CISO under Circular 46?
Not as a binding rule. Paragraph 7 says a port facility may designate an officer or function, and paragraph 10 strongly advocates a mechanism like the DGS one, where the Chief Information Security official's role is critical. CERT-In's guidelines ask government entities under central ministries to nominate a CISO.
Has BoPS published cyber security standards for ports?
We found none as of 30 October 2026. The Bureau of Port Security Rules, 2026 list cybersecurity as a topic its standards may cover.

Sources

  1. DGMA Circular No. 46 of 2026: Maritime Cyber Security Risk Management for Port Facilities under the ISPS Code (4 August 2026) · Directorate General of Maritime Administration
  2. ISPS & Maritime Security circulars · Directorate General of Maritime Administration
  3. Circular 54 of 2026: Cybersecurity Awareness Training on Physical & Workspace Security, Mobile Security and Email Security Habits (1 September 2026) · Directorate General of Maritime Administration
  4. MSC-FAL.1/Circ.3/Rev.4: Guidelines on Maritime Cyber Risk Management (28 May 2026) · International Maritime Organization
  5. Resolution MSC.428(98): Maritime Cyber Risk Management in Safety Management Systems (16 June 2017) · International Maritime Organization
  6. Directions under sub-section (6) of section 70B of the IT Act, 2000 (No. 20(3)/2022-CERT-In, 28 April 2022) · CERT-In
  7. Comprehensive Cyber Security Audit Policy Guidelines, version 1.0 (25 July 2025) · CERT-In
  8. Guidelines on Information Security Practices for Government Entities · CERT-In
  9. Merchant Shipping (Ships and Port Facility Security) Rules, 2026 (G.S.R. 909(E), 23 October 2026) · Gazette of India
  10. Merchant Shipping (Bureau of Port Security) Rules, 2026 (G.S.R. 883(E), 14 October 2026) · Gazette of India

Scoping a system like this? Talk to the team that designs, builds and maintains it.

Contact us