Singapore

Singapore Cybersecurity Act 2018

59 controls. 215 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

59 controls 215 frameworks share controls with it Singapore verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

Singapore Cybersecurity Act 2018 Evidence & Implementation Kit

59 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
SCA-AC-1Access Control and Privileged Access for CII0
SCA-DR-1Disaster Recovery and Continuity for the CII0
SCA-IR-1Incident Response Plan Aligned to Sector Requirements0
SCA-IR-224x7 Detection and Response Capability0
SCA-LOG-1Logging, Monitoring, and Retention0
SCA-NSC-1Network Segmentation and Zoning of the CII0
SCA-S10Annual Risk Assessment67
SCA-S11Annual Audit0
SCA-S14Incident Notification0
SCA-S2Interpretation and Definitions96
SCA-S26Licensing Framework27
SCA-S28License Conditions0
SCA-S3Appointment of Commissioner0
SCA-S32Investigation of Cybersecurity Threats0
SCA-S35Emergency Measures0
SCA-S36Penalties for Non-Compliance0
SCA-S4Commissioner Functions and Duties0
SCA-S5Cybersecurity Codes and Standards0
SCA-S7CII Designation0
SCA-S9Compliance with Codes and Directions0
SCA-SC-1Supply Chain Cybersecurity for CII0
SCA-VM-1Vulnerability and Threat Management for CII0
SGCYBER-1Critical Information Infrastructure (CII) Designation and Registration88
SGCYBER-2Codes of Practice, Standards, Audits0
SGCYBER-3Cyber Incident Reporting0
SGCYBER-4Licensing of Cybersecurity Services0
SGCYBER-5Investigation, Enforcement, Cooperation0
16BProvide information to help decide whether third-party-owned systems are CII0
16ESecure the owner's commitment to supply information; furnish it and notify material changes within 14 days0
16FSecure the owner's commitment to maintain prescribed cybersecurity standards0
16GComply with directions, including to require the owner to maintain standards0
16HOwnership changes and changes in circumstances: commitments and 7-day notifications0
16IIncident reporting for third-party-owned CII: owner commitment, own reporting and detection0
16JAudits and risk assessments through the owner; reports to the Commissioner within 14 days0
16KNotify material changes to the legally binding commitments within 14 days0
16LParticipate in cybersecurity exercises when directed0
17A-DSystems of temporary cybersecurity concern: provide information0
17ESystems of temporary cybersecurity concern: comply with directions0
17FSystems of temporary cybersecurity concern: report incidents and maintain detection0
35AComply with the applicable codes of practice and standards of performance0
ACTThe Cybersecurity Act 2018 as amended: structure and status0
CCOPThe Cybersecurity Code of Practice for CII (Second Edition Revision One)0
CIVIL-PENALTYOffences and civil penalties (Parts 3 to 3D, s 37A)0
DESIGNATIONDesignation and definitions (ss 2, 7, 9, 9A, 16A, 16C, 16D, 17, 17B, 17C)0
ESCI-FDIParts 3C and 3D (entities of special cybersecurity interest, major foundational digital infrastructure): published, not in force0
PENDINGPublished, not yet in force: Digital Infrastructure Bill 20260
S10-1Furnish information on the design, configuration, security and operation of the CII0
S10-5Notify material changes to the CII within 30 days0
S12Comply with the Commissioner's written directions0
S13Report changes in ownership of the CII within 7 days0
S14Report prescribed cybersecurity incidents and maintain detection mechanisms0
S15Biennial compliance audit, annual risk assessment and reports within 30 days0
S15-3Comply with directed re-audits, further assessment and Commissioner-ordered audits0
S16Participate in cybersecurity exercises when directed0
S19-20Cooperate with incident response officers investigating threats and incidents0
S24Hold a licence to provide or advertise licensable cybersecurity services0
S26-27Truthful applications and compliance with licence conditions0
S29Keep engagement records for 3 years and allow licensing officer monitoring0
S8Provide information to help the Commissioner decide whether a system is CII0

Tell me when Singapore Cybersecurity Act 2018 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • data subject notification template (Thai)
  • risk assessment criteria
  • communication channel records
  • incident notification procedure
  • CSA notification log
  • incident triage records
  • legal review documentation
  • outcome tracking
  • ministerial authorisation records
  • request documentation

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for Singapore Cybersecurity Act 2018, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition