Home › Insights › Frameworks & Regulation
Frameworks & Regulation

CII Owners and the CISO Requirement: What Singapore's Cybersecurity Act Actually Expects

Singapore's Cybersecurity Act and the 2026 Code of Practice require CII owners to name an accountable, suitably authorised security leader; this article sets out what that function must demonstrate and how a compliant interim arrangement is evidenced.

By Infracom Team19 November 20267 min read

Singapore's Cybersecurity Act does not simply ask critical information infrastructure (CII) owners to "have good cybersecurity." It requires a named, accountable security leadership function with the authority and competence to discharge specific duties, and it expects that function to be evidenced, not assumed. For mid-sized CII-adjacent operators without a standing CISO, the compliant answer is rarely "hire one immediately" — it is to put a properly mandated interim or fractional arrangement in place and document it the way an assessor will look for it.

What the Cybersecurity Act and the 2026 Code of Practice require

The Cybersecurity Act, which came into force on 31 August 2018, establishes a legal framework for the oversight and maintenance of national cybersecurity in Singapore. It sets out duties for owners of designated CII, and the Commissioner of Cybersecurity issues a Code of Practice under the Act to specify how those duties are met in practice. CSA's current code is the Cybersecurity Code of Practice for Critical Information Infrastructure 2026, which took effect on 29 July 2026 and superseded the previous edition.

The 2026 Code is explicit about security leadership. Clause 3.2.1 states that where a senior management member or equivalent, for example a Chief Information Security Officer (CISO), is designated for this purpose, the CIIO shall ensure that the individual is vested with the authority and competencies required to effectively discharge their cybersecurity responsibilities. Legal commentary on the updated Code is equally direct on scope: at least one member of senior management, or an individual working in or for the CIIO (for example, a designated Chief Information Security Officer) must possess the knowledge and awareness necessary to manage cyber risks across the CII, its interconnected systems and the CIIO's enterprise network, provide oversight of cybersecurity measures, and ensure their appropriate implementation.

This sits alongside a wider tightening of governance expectations. The 2026 Code imposes board-level accountability on CII owners and mandates Cyber Trust Mark certification (Tier 5) for all CII owners and their auditors. CSA's own announcement of the update confirms that CII owners are required to strengthen Board and senior management accountability and oversight for cybersecurity. In other words, the named security leader is not a stand-alone appointment — it is the operational expression of a board-level accountability chain that CSA now expects to see documented.

The Code also names the role operationally, not just structurally. Two of the plans a CII owner must maintain — the Cybersecurity Incident Response Plan and the Sectoral Heightened Alert Plan — are each required to be led by the CISO or a suitably qualified personnel. An assessor reviewing these plans will therefore ask, specifically, who leads them, and whether that person has the standing to do so.

Owners should also note the compliance calendar. Legal summaries of the update note that CIIOs should use the transition period between the Effective Date (29 July 2026) and the Compliance Date (29 July 2027, or 31 December 2027 for Cyber Trust Mark certification) to close gaps — including governance gaps around the security leadership function. Separately, under Clause 5.16 of the current Code, the CIIO shall be certified with Cyber Trust Mark Advocate (Tier 5) or its equivalent within 24 months of its designation, or by the date stipulated by CSA for an existing CIIO. The named security leader is typically the individual who owns that certification programme internally.

These obligations sit within the broader duties CSA has long placed on owners. CSA's explanatory material on the Act confirms that sections 10 to 16 set out the duties of the owner of a CII, including the duty to comply with codes of practice, to cause regular audits of compliance with the Act and applicable codes to be carried out by an auditor, and to carry out regular cybersecurity risk assessments of the CII at least once a year. A named security leader is who signs off, coordinates, and is accountable for each of these recurring obligations — which is exactly why CSA expects the role to be real, not nominal.

How this compares with MAS expectations for regulated financial institutions

Several CII sectors — notably banking and financial services — sit under both the Cybersecurity Act and the Monetary Authority of Singapore's Technology Risk Management Guidelines. The two regimes are not identical, but they reinforce the same principle: accountability has to be named and resourced, not implied.

← Swipe to compare →

DimensionCybersecurity Act / CCoP 2026 (CII owners)MAS Technology Risk Management Guidelines (regulated financial institutions)
Legal basisCybersecurity Act 2018, Code of Practice issued under section 35AMAS Notices and Guidelines issued under the Monetary Authority of Singapore Act
Named role expectedSenior management member or equivalent, for example a CISO, designated for cybersecurity oversightA Chief Information Officer and a Chief Information Security Officer, or their equivalents
Authority requirementThe individual must be vested with the authority and competencies required to effectively discharge their cybersecurity responsibilitiesThe CIO and CISO need requisite experience and expertise and should be accountable for managing the FI's technology and cyber risks
Board linkageBoard-level accountability is imposed on the CII ownerThe board and senior management should ensure the appointment of the CIO and CISO (or their equivalent)
Plan ownership testedIncident Response Plan and Sectoral Heightened Alert Plan, each led by the CISO or suitably qualified personnelTechnology risk management framework, incident reporting protocols, board risk committee minutes

Where a single operator sits under both regimes, the practical implication is that one properly mandated security leadership function, correctly documented, can usually satisfy both sets of expectations — provided the evidence trail is built with both in mind.

The evidence an assessor will actually look for

CSA auditors and MAS examiners do not take a title on an organisation chart at face value. In practice, a review of the security leadership function tends to test:

  • A documented mandate that names the individual (or the engaged fractional CISO) and sets out their authority, scope and reporting line to senior management or the board.
  • Evidence of competence relevant to the CII sector and its systems, not a generic security CV.
  • Minutes or board papers showing the function reports upward and that cybersecurity risk reaches senior management and, where required, the board.
  • Ownership of the recurring statutory obligations — the annual risk assessment, the compliance audit, and participation in cybersecurity exercises — attributable to a named person, not "the IT team."
  • Sign-off on the Cybersecurity Incident Response Plan and the Sectoral Heightened Alert Plan, consistent with the Code's requirement that these be led by the CISO or a suitably qualified individual.
  • A credible continuity arrangement — what happens if that individual is unavailable, and who deputises.

For an organisation without a standing CISO, the gap is rarely technical. It is the absence of a documented mandate, a visible reporting line, and a paper trail connecting the named leader to each of these recurring duties.

Preparing a compliant interim or fractional arrangement

A fractional or interim CISO arrangement can satisfy the Code's requirement, but only if it is set up to be demonstrably equivalent to a permanent appointment in substance. Practical steps include:

  1. Formalise the mandate in writing. Set out scope, authority, decision rights and escalation paths, and have it approved at board or senior management level rather than left as an informal engagement letter.
  2. Map the function against every recurring duty in the Act and the Code — risk assessment, audit, incident reporting, exercises, interconnected-system oversight — and assign named ownership for each.
  3. Build the evidence pack before it is asked for: organisation chart, mandate letter, reporting-line records, and minutes showing cybersecurity items reaching senior management.
  4. Align the arrangement with your Cyber Trust Mark pathway, since the Advocate (Tier 5) certification timeline and the security leadership evidence are reviewed together in practice.
  5. Review the arrangement against CCoP 2026 specifically, given the governance changes it introduces, rather than relying on the previous edition's expectations.
  6. Rehearse the continuity question. Document who steps in if the fractional CISO is unavailable, and keep that cover current.

Where AI systems enter the picture

CSA's rationale for updating the Code explicitly references the shifting threat picture created by AI-enabled attacks, and the security leadership function is expected to account for this. Where a CII owner's environment includes AI systems or AI agents — whether supporting operations, customer-facing services or security monitoring itself — the same accountability logic applies: someone named must own the governance, risk and security posture of those systems, mapped against frameworks such as ISO/IEC 42001, the NIST AI Risk Management Framework, MAS's AI risk guidance, CSA's Guidelines on Securing AI Systems and IMDA's Model AI Governance Frameworks. Where that ownership is currently informal or absent, it represents the same type of gap a CSA or MAS reviewer will flag in a security leadership function — and is addressed through a fractional Chief AI Officer engagement rather than by folding AI oversight informally into an already-stretched CISO role.

How Infracom helps

Infracom Consultancy Integration provides fractional CISO support for CII owners and CII-adjacent operators who need a named, properly mandated security leadership function without the cost of a full-time hire. We build the mandate, the reporting structure and the evidence pack an assessor will test — mapped to the Cybersecurity Act, CCoP 2026 and, where relevant, MAS's Technology Risk Management Guidelines — delivered by an all-Singaporean SQEP team at rates accessible to mid-sized organisations. Read more about the service at our fractional CISO page.

Sources (8)
  1. Cybersecurity Act
  2. Codes of Practice
  3. Technology Risk Management Guidelines
  4. Cybersecurity Code of Practice for Critical Information Infrastructure 2026
  5. Singapore's CSA issues updated Cybersecurity Code of Practice for Critical Information Infrastructure
  6. Cybersecurity Code of Practice to be Updated to Address APT and AI-enabled Threats
  7. MAS revises Technology Risk Management Guidelines for Financial Institutions
  8. Provisions in the Cybersecurity (Amendment) Act to Come Into Force on 31 October 2025

Get Infracom Insights by email

Practical cybersecurity governance and regulatory updates for Singapore and Australia. No more than a few emails a month; unsubscribe any time.

Infracom Consultancy Integration Pte Ltd

Your one-stop IT & cybersecurity partner — Singapore HQ since 2008, expanding to Australia in 2026.

506 Chai Chee Lane

Singapore 469026

Services
IT InfrastructureCloud SolutionsCybersecurityManaged ServicesData Center SolutionsIT Consulting
Consulting
SQEPGRCVAPT
GRC Services
Fractional CISOFractional CAIOData Protection OfficerInternal & Supplier Audit
Approach
MethodologyAbout UsInsightsStoreNewsletterPrivacy Policy
Hours

Mon – Fri
9AM – 6PM SGT

Follow us
© Infracom Consultancy Integration Pte Ltd. All rights reserved.Privacy Policy