Customers and tenders require an ISO 27001 certificate. How does the CEO decide the scope and timing?
The service page observes that in supplier reviews by multinationals, government and financial tenders and cloud customer due diligence, 27001 is the first certificate asked for. The CEO's decision is not whether, but what to cover first:
- Step one: confirm the security requirements of customers, tenders and regulators, then define the certification scope. Base it on the product lines, sites and services actually being asked about; too narrow and customers will not accept it, too broad and the timeline grows.
- Edition: always implement ISO/IEC 27001:2022; the transition period for 2013 certificates ended on 31 October 2025.
- What auditors focus on: the risk assessment and the Statement of Applicability. Not all 93 controls are required; applicability follows the risk assessment, with reasons for any exclusion.
- Timeline (as listed on the service page): typically 4–8 months: gap analysis, system build, internal audit and management review, then stage 1 and stage 2 certification; existing IT governance shortens it noticeably.
Must the company appoint a chief information security officer? How many dedicated security staff?
It depends on where the company sits:
| Who | Rule | Requirement |
|---|---|---|
| All public companies | Internal control regulations, Article 9-1 | Allocate adequate people and equipment to plan, monitor and run information security |
| Listed companies with paid-in capital of NT$10 billion or more, Taiwan 50 constituents, or e-commerce revenue above a set share | FSC order of 28 December 2021 | Appoint a chief information security officer and set up a dedicated unit with a head and at least 2 dedicated staff by the end of 2022 |
| Other listed companies (except those with pre-tax losses in each of the last three years or net worth per share below par) | Same order | A dedicated head and at least 1 dedicated staff member by the end of 2023 |
For ordinary public and listed companies, official rules set no rank for the CISO; "senior vice president or above" applies to banks, financial holding companies and the securities and futures sector. Companies that are not public companies are not covered by these rules and can use them voluntarily.
Who approves the security policy, and how often should the CEO hear a security report?
- Cybersecurity Control Guidelines for Listed Companies, Article 4: the security policy is approved by a manager at senior vice president level or above and reviewed regularly. This is the rank of the approver, not of the CISO.
- Article 37: report on cybersecurity regularly to the board or management; the guidelines set no frequency. Under Article 41, listed companies may adopt them as appropriate to their industry, size and security risk; companies that are not public companies are not covered by these guidelines and can use them voluntarily.
- Banks and financial holding companies: the chief information security officer reports to the board every year on the previous year's information security.
- ISO 27001: the system goes through internal audit and management review, and the management review records are the evidence of the CEO's involvement.
- If the company is an entity in scope of NIS2: Article 20 requires the management body to approve the cybersecurity risk-management measures and oversee their implementation, and its members must follow training.
When a major security incident happens, what must the CEO account for externally?
- Annual report: Article 18, item 6 of the annual report regulations for public companies requires disclosure of the losses, possible effects and responses for major cybersecurity incidents.
- Internal procedure: Article 34 of the Cybersecurity Control Guidelines for Listed Companies requires incident response and reporting procedures.
- Reporting deadlines where the company does business in the EU:
| Law | Deadline |
|---|---|
| GDPR, Article 33 | Personal data breach: where feasible, within 72 hours of becoming aware, to the supervisory authority |
| NIS2, Article 23 | Significant incident: early warning within 24 hours, notification within 72 hours, final report within one month |
| EU CRA, Article 14 | Actively exploited vulnerabilities and severe incidents: early warning within 24 hours, notification within 72 hours; applies from 11 September 2026 |
One incident can trigger several deadlines; the CEO should make sure the response procedure has an incident classification step that decides which reports apply. Companies that are not public companies are not covered by these public-company rules and can use them voluntarily.
With ISO 27001, are the NIS2, EU CRA and GDPR requirements of European customers covered?
No. NIS2, the EU CRA and GDPR have no standalone certificate:
- NIS2: implement the Article 21 measures and Article 23 reporting; where the company is only a supplier to an entity in scope, the customer writes supply chain security requirements into the contract.
- EU CRA: complete the conformity assessment for the product category and affix the CE marking; from 11 December 2027, digital products without it may not be placed on the EU market.
- GDPR: demonstrate compliance with the RoPA, DPIAs, processor contracts, transfer mechanisms and breach records.
ISO 27001's value is the shared management backbone that shortens other timelines (as listed on the service pages): NIS2 from usually 4–6 months down to 2–3 months; ISO 22301 about 3–5 months; ISO 42001 certification usually within 4–6 months. When ranking priorities, the CEO can do 27001 first and add the others by customer and market.
How does ISO 27001 help with the TWSE ESG evaluation and annual report disclosure?
- ESG indicator S-12 (same wording in 2026 and 2027, assessed from the annual report): whether the company has built and disclosed a cybersecurity risk management framework, policy, concrete programmes and resources invested. Implementing ISO 27001, CNS 27001 or another information security management system standard with equivalent or better effect, with third-party certification, adds one point overall.
- Annual report: the same numbers (resources, programmes, certification results) serve the disclosure under Article 18, item 6.
- S-15: if the company requires suppliers to follow cybersecurity or privacy rules, 27001's supplier controls are supporting evidence.
The ESG evaluation covers listed companies; companies that are not public companies are not evaluated and can use the indicators voluntarily.
How does Winners Consulting help a CEO with ISO 27001?
This is Winners Consulting's own description; hold us to the questions above.
- Who leads: Winners Consulting is a consultant and does not issue certificates; vice-president and director-level consultants personally lead the work end to end, never outsourced, and the team holds ISO lead auditor qualifications
- Scope first: we confirm the security requirements of customers, tenders and regulators, then define the certification scope
- One risk map: the assessment framework uses ERM risk language so the 27001 risk register and the enterprise risk map speak to each other
- After certification: certified organisations can outsource their internal audit to Winners
- Named clients: MPI Corporation (ISO 27001 ISMS and trade secret protection consulting), 訊光資訊科技 (InfoLight) (ISO 27001 ISMS consulting)
- First step: the first mechanism diagnosis is free
Go deeper: ISO 27001 consulting, Which ISO 27001 consultant in Taiwan?, Outsourcing the ISO 27001 internal audit, CISO role page
How other roles see this service
Other services for this role
- ERM for the CEO: what to settle first on the board, the internal control statement and personal liability?
- ISO 37001 for the CEO: if an overseas agent pays a bribe, what liability falls on the company and on you?
- ISO 22301 for the CEO: how long can a site be down, and who signs off the RTO?
- Trade secrets for the CEO: when an engineer leaves with data, what must the company prove?
- EU CRA for the CEO: European orders, penalties and ownership. What to decide now
- NIS2 for the CEO: Article 20 management liability, fines and European customer demands
- EU AI Act and ISO 42001 for the CEO: staff AI use, fines and governance ownership
- GDPR and ISO 27701 for the CEO: penalties, cross-border transfers and ownership
- TISAX for the CEO: European OEM orders, assessment levels, timing and investment
- Digital transformation for the CEO: ROI, tax credits, security and disruption
- AI transformation for the CEO: first use case, ROI and accountability