Enterprise risk management: let the board see strategic risk, and let evaluators and investors find the evidence
For listed and pre-IPO companies: a risk management system on COSO ERM and ISO 31000 that implements the TWSE practice code article by article — policy, organisation, appetite, KRIs, annual board reporting and disclosure — while bringing security, continuity, AI and privacy risk onto one risk map.
On 19 September 2022 the Taiwan Stock Exchange issued the Risk Management Practice Code for listed companies under Corporate Governance 3.0, drawing on COSO ERM 2017 and ISO 31000:2018. Adoption is encouraged, but Article 28 requires public disclosure of the risk policy, organisation and the frequency and dates of board reporting — companies that have not done so are visible in governance evaluations and investor questionnaires. ERM is not another document set; it is telling the board about existing internal control, security, continuity, AI and privacy risks in one method and one language.
02 Which companies need formal ERM now?
ERM is about the quality of board decisions. Formalising it pays back clearly when any of the following applies.
- Listed companies: governance evaluations, investor and ESG questionnaires ask about the risk policy, committee and board reporting
- Preparing for listing or institutional investors and needing a risk governance structure before application
- Several management systems (ISO 27001, 22301, 42001) each assess risk separately, and the board cannot see one risk map
- Supply-chain customers (OEMs, brands, financial institutions) require overall risk management and a supply-chain risk register in due diligence
- After a major event (supply disruption, cyber incident, FX, compliance) the board demands a formal system with KRI early warning
- A parent or group on COSO/SOX requires subsidiaries to speak the same language
Small non-public companies with a single business and concentrated risks can start with one ISO 31000 risk register and quarterly review; no committee is needed yet.
03 Frameworks and law: COSO ERM, COSO ICSR, ISO 31000, the practice code, internal control regulations
Five documents, one job each
Five components and 20 principles: governance and culture (board oversight, operating structure, culture, talent), strategy and objective-setting (business context, risk appetite, alternative strategies, objectives), performance (identify, assess, prioritise, respond, portfolio view), review and revision (substantial change, performance review, improvement), information, communication and reporting. The common language of US investors, auditors and SOX; no certification.
Principles (integrated, structured, customised, inclusive, dynamic, best available information, human and cultural factors, continual improvement), framework (leadership and commitment, integration, design, implementation, evaluation, improvement), process (scope, context, criteria; risk assessment = identification / analysis / evaluation; treatment; monitoring and review; recording and reporting; communication and consultation). The shared method behind the risk clauses of 27001, 22301 and 42001; a guidance standard, not certifiable.
Articles 4–5: policy content, board approval and disclosure; Articles 10–12: the board as top governance body, a risk committee (independent directors recommended as majority and chair) and an execution unit; Articles 13–15: duties of board, committee and execution unit with at least annual reporting; Article 16: operating units identify, assess and respond; Article 22: risk appetite; Articles 27–28: periodic reporting and public disclosure. Encouraged, scaled to size and risk profile.
Mandatory: internal control design and operation, self-assessment, internal audit, annual internal control statement. Internal control governs the effectiveness of control activities; ERM governs strategic risk and opportunity — complementary.
Supplemental guidance that applies the 5 components and 17 principles of the 2013 Internal Control—Integrated Framework to sustainability information one by one; it is guidance, not a certifiable standard. In Taiwan the legal basis is the internal control regulations: after the FSC amendment of 22 April 2024, from 1 January 2025 a listed company's internal control system must cover the management of sustainability information (Article 8, paragraph 4), and it is a mandatory item in the annual audit plan. Winners designs the sustainability information control points on the ICSR principles and uses ERM to put sustainability risk on the same risk map.
COSO components × code articles × deliverables (extract)
An extract of the mapping we deliver: left, the COSO component; middle, the code articles; right, how one document satisfies both and the evaluation questionnaire.
| COSO ERM 2017 | Practice code | One document |
|---|---|---|
| Governance and culture | Articles 4, 5, 7, 10–13 | Board-approved risk policy + organisational responsibilities + culture and training records |
| Strategy and objective-setting | Articles 13, 22 | Risk appetite statement (qualitative + quantitative) and strategic risk assessment records |
| Performance | Articles 15, 16 | Unified assessment method, risk register, KRIs and response plans |
| Review and revision | Articles 14, 15 | Annual effectiveness review and corrective action records |
| Information, communication and reporting | Articles 27, 28 | Periodic risk report template + website / MOPS disclosure page |
COSO ERM, ISO 31000, the TWSE Risk Management Code and the internal control regulations: framework, standard, code and law
Boards often ask "COSO or ISO 31000?" — but the four sit at different levels: two are international frameworks/standards without certification, one is a stock-exchange practice code (encouraged, with disclosure), one is a regulation (internal control). First ask whose question you need to answer.
| Item | Nature | Who and where | Mandatory? | How it is proven |
|---|---|---|---|---|
| COSO ERM 2017 | US COSO enterprise risk management framework (5 components, 20 principles) | Any organisation; the common language of US investors, auditors and the SOX world | Voluntary; no certification scheme | Self-assessment and board reporting; external assessment opinions possible, no certificate |
| ISO 31000:2018 | International risk management guidelines (principles, framework, process) | Any organisation, any risk type; the shared method behind the risk clauses of 27001, 22301, 42001 | Voluntary; a guidance standard, not certifiable | No certificate; demonstrated through risk policy, process documents and records |
| TWSE Risk Management Practice Code for Listed Companies (19 Sep 2022) | Practice code issued by the Taiwan Stock Exchange under Corporate Governance 3.0, drafted with reference to COSO ERM 2017 and ISO 31000:2018 | TWSE/TPEx-listed companies (encouraged, scaled to size and risk profile) | Encouraged; risk policy and operations to be disclosed on the company website or MOPS (Articles 5, 28) | Board-approved risk policy, risk committee / execution unit, report to the board at least annually (Articles 13–15) |
| Regulations Governing Establishment of Internal Control Systems by Public Companies (FSC) | Taiwan regulation | Public companies | Mandatory; annual internal control statement | Internal control system, self-assessment, internal audit reports, internal control statement |
Key differences
- There is no certificate for COSO ERM or ISO 31000; boards need the system to exist and report, not a certification.
- The practice code is not law, but Article 28 requires disclosure of the risk policy, organisation and the frequency and dates of board reporting — missing disclosure costs points in evaluations and investor questionnaires.
- Internal control regulations govern whether control activities are effective; ERM governs strategic risks and opportunities. Internal control without ERM leaves the board blind to strategic risk.
- The ISO 31000 process (scope, identification, analysis, evaluation, treatment, monitoring) underlies the risk clauses of 27001, 22301 and 42001 — one method shared by all systems.
How to choose
- Listed company answering governance evaluations and investor questionnaires → use the practice code articles as the skeleton and the COSO five components to structure board reporting.
- US customers, SOX 404 or a parent on COSO → COSO ERM 2017 first, ISO 31000 as the process method.
- Bringing security, continuity, AI and privacy risk into one risk map → ISO 31000 process as the common method; each management system only adds risk sources and treatments.
- Minimum regulatory compliance only → make the internal control regulations real first, then add the code's risk policy and annual reporting for the strategic layer.
What to share when implementing together
Share one base: risk policy (code Articles 4, 5 = COSO governance and culture = ISO 31000 framework), risk appetite (code Article 22 = COSO strategy and objective-setting), risk assessment method (ISO 31000 process = COSO performance = management-system risk clauses), KRIs and board reporting (code Articles 14, 15, 27 = COSO information, communication and reporting). Only audiences and disclosure formats differ.
How Winners works
Winners supports all four: COSO ERM framework build-out, ISO 31000 process design, risk policy / committee / annual reporting and disclosure under the practice code, and internal control systems and self-assessment. The first step is to identify who you must answer — board, evaluation, investors, customers — then choose the framework that leads.
Either entry works: start from your industry's pain points or from the standard you plan to adopt — we first clarify the differences, then give you the information and support.
04 Deliverables
05 Method (4 phases)
- Phase 1 | Diagnosis and governance design (3–4 weeks)
Interviews with board members, executives and units; inventory of internal control and each management system's risk assessment; gap analysis against the code; committee and execution unit design.
- Phase 2 | Policy, appetite and method (4–6 weeks)
Draft the risk policy, risk appetite statement and unified method; board approval.
- Phase 3 | Risk assessment and KRIs (6–8 weeks)
Identification and assessment workshops per unit; risk register and response plans; KRIs and dashboard; first committee report.
- Phase 4 | Reporting, disclosure and hand-over (3–4 weeks)
Board report, disclosure content, annual review mechanism; operations calendar and evaluation mapping handed over.
06 Cases and evidence
Anonymised engagements under NDA; client names are not disclosed. Only completed work is described; no outcome is guaranteed.
Semiconductor supplier
Established an enterprise risk management framework integrating ISO 31000 and COSO ERM, completed a supply-chain risk register, a KRI automatic alert dashboard and a quarterly risk committee reporting mechanism, meeting the annual-report risk disclosure requirements for listed companies.
07 Decision tools
Use the 10 questions to see maturity (each shows the COSO component and code article), then the "framework ≠ law" disclosure to choose the lead framework. Everything runs in your browser; no data is sent.
ERM maturity self-assessment (10 questions)
Answer per the five COSO ERM components and the TWSE practice code; each gap shows the code article — exactly what governance evaluations and investor questionnaires ask about.
- 01A board-approved risk management policy covering objectives, governance and culture, organisation, process, reporting and disclosure, published on the website or MOPS?COSO component: Governance & culture
Article: TWSE Code §4–5 - 02The board is the top risk governance body, with a risk committee (or functional committee) and a designated execution unit, responsibilities documented?COSO component: Governance & culture
Article: TWSE Code §10–12 - 03Risk management is in staff training and performance evaluation, and first-line units know how to escalate risks?COSO component: Governance & culture
Article: TWSE Code §7 - 04A written risk appetite / tolerance with qualitative and quantitative measures, linked to strategic objectives?COSO component: Strategy & objective-setting
Article: TWSE Code §22 - 05Risk assessment precedes annual strategy and major investment decisions, and the board confirms strategy is consistent with the risk policy?COSO component: Strategy & objective-setting
Article: TWSE Code §13 - 06A unified identification, analysis, evaluation and response process with a risk register covering strategic, operational, financial, compliance, cyber and ESG risks?COSO component: Performance
Article: TWSE Code §16 - 07Key risks have KRIs with thresholds and a defined escalation and response path when breached?COSO component: Performance
Article: TWSE Code §15、§22 - 08Risk assessments of the security (27001), continuity (22301), AI (42001) and privacy systems use one method and one risk map?COSO component: Performance
Article: ISO 31000 §5.4 - 09Risk management effectiveness is reviewed by the committee and reported to the board at least annually, and updated promptly on major change?COSO component: Review & revision
Article: TWSE Code §14–15 - 10Periodic risk reports have a fixed format and frequency, and operations (including frequency and dates of board reporting) are disclosed externally?COSO component: Information, communication & reporting
Article: TWSE Code §27–28
08 Our qualifications and approach
- Risk governance × multi-system integration
- Board reporting organised by the five COSO components, one method from the ISO 31000 process, and security, continuity, AI and privacy risk assessments folded into one risk map; code articles mapped one by one.
- Only what boards use and evaluators see
- Every deliverable maps to a code article and an evaluation indicator; we do not write thick reports boards will not read.
- Division of work with auditors and counsel
- We build the system, method and reports; internal control statements and financial reporting matters stay with the auditors; legal opinions with partner lawyers.
- Partner network
- Chinese Software Service Industry Association, ITRI, III, ISA Taiwan Section.
- Third-party profile: Taiwan Information Security Association (TWISA)
- Member profile in the Association’s newsletter No. 51: “Winners optimises ecosystem-wide enterprise risk management for companies, meeting cross-border compliance, supply-chain customer verification and sustainability requirements, and raising the overall effectiveness of risk management.” Newsletter (original, Chinese)
09 FAQ
What is the difference between ISO 31000 and COSO ERM? Which should Taiwanese companies choose?
Neither is certifiable. COSO ERM 2017 is a governance framework centred on strategy and performance (five components, 20 principles) and the language of US investors and auditors; ISO 31000:2018 is guidance on risk management principles, framework and process, and the shared method behind ISO management-system risk clauses. The TWSE practice code references both. In practice: COSO components to organise board-level governance and reporting, the ISO 31000 process for unit-level assessment — one system answering both.
Why do Taiwanese listed companies need an ERM framework?
The 2022 TWSE practice code is encouraged rather than mandated, but Article 28 requires disclosure of the risk policy, organisation and the frequency and dates of board reporting, which governance evaluations and investor questionnaires check; internal control regulations add the legal baseline. More practically, cyber, supply-chain, FX and compliance risks sit in different units, and the board needs one integrated risk map to make strategic decisions.
What is a KRI and how is it designed?
A KRI is a leading indicator before a risk materialises, such as supplier concentration, single-customer share, unpatched high-severity vulnerabilities or FX exposure. Design rules: 1–3 per key risk, quantifiable, with a data source, a threshold and an escalation path, linked to risk appetite. Code Article 15 requires the execution unit to set qualitative and quantitative measurement criteria.
How long does ERM consulting take?
Typically 4–6 months across four phases; about 3–4 months for companies with several ISO systems or a group COSO framework. The first board report usually lands at the end of month three.
Which risk mechanisms do semiconductor and electronics suppliers particularly need?
A supply-chain risk register (single sources, geopolitics, critical materials), KRIs for customer concentration and demand swings, cyber and trade secret risk (always in customer audits), export control and compliance risk, and business continuity (power, earthquake, supply disruption). All assessed with the same ISO 31000 method and mapped to customer due-diligence questionnaires.
Can ERM be integrated with ISO 27001, 22301 and 42001?
Yes, and it is our default: ERM provides the policy, appetite, method and board reporting; each management system only handles its own risk sources and treatments. The ISO 31000 process underlies those standards' risk clauses, so cyber, continuity and AI risk appear on one risk map.
Does your ERM consulting cover COSO ICSR (internal control over sustainability reporting)?
Yes. Since 1 January 2025 a listed company's internal control system must cover the management of sustainability information, and it is a mandatory item in the annual audit plan (internal control regulations, Article 8, paragraph 4). Winners designs the sustainability information control points on the 17 principles of COSO's 2023 ICSR supplemental guidance and links them to your existing finance-cycle controls; sustainability risk sits on the same ERM risk map as security and continuity risk and is reported to the board in one language. ICSR is guidance, not a certifiable standard; assurance opinions come from your auditor or an assurance provider.
Does Winners have Taiwanese ERM engagements?
Yes, presented anonymously under NDA: for example a semiconductor supplier's framework integrating ISO 31000 and COSO ERM with a supply-chain risk register, KRI alert dashboard and quarterly risk committee reporting. See the cases page or book a consultant for details.
We have already established an enterprise risk management (ERM) system. How can Winners Consulting help us keep improving it?
There is no ERM certificate: neither COSO ERM nor ISO 31000 is a certifiable standard, so improvement shows in operating records that the board and evaluators can see. We start from the system you already run rather than building a second one. We re-check your policy, organisation and disclosure article by article against the TWSE Risk Management Practice Code, recalibrate risk appetite and KRI thresholds, bring the risk assessments of ISO 27001, 22301, 42001 and other management systems onto one risk map, and set up annual effectiveness reviews with corrective-action records, so each year's board report and the Article 28 disclosure are backed by evidence. See our enterprise risk management (ERM) consulting service.
Another consultancy helped us establish our enterprise risk management (ERM) system. How can Winners Consulting help us embed it fully into day-to-day operations and make sure it genuinely prevents these risks?
The most common gap in ERM is a risk report that is updated once a year and then left unopened. We begin with a current-state diagnosis that compares the documents with what each unit actually does. Then we build ERM into processes you already run: risk appetite is discussed in strategy and budget meetings, committee reports go on the board's annual agenda, internal control self-assessment doubles as a check on control effectiveness, KRIs draw directly on ERP and finance data, and KCIs track whether controls are working. Three hand-off points leave a record: logging a new risk, escalating a KRI breach, and closing an audit finding. The Ahura enterprise risk management platform (at POC stage) keeps evidence and sign-off records on the company's own premises. See ERM technical integration: from KRIs and risk appetite to control effectiveness.
Frameworks and official sources
- TWSE Corporate Governance Center — press release on the Risk Management Best-Practice Principles for TWSE/TPEx Listed Companies (2022-09-19) (in Chinese)
- TWSE Corporate Governance Center — rules and Q&A issued by TWSE and TPEx (in Chinese)
- COSO — Enterprise Risk Management: Integrating with Strategy and Performance (2017)
- ISO 31000:2018 — Risk management — Guidelines
- Regulations Governing Establishment of Internal Control Systems by Public Companies — Laws & Regulations Database of the R.O.C. (Taiwan) (in Chinese)
- Taiwan Stock Exchange: FSC amends the internal control regulations to bring the management of sustainability information into the internal control system (in force 2025-01-01) (in Chinese)
- The IIA — COSO Releases New Supplemental Guidance on Achieving Effective Internal Control over Sustainability Reporting (ICSR), 2023-03-30
Last updated 2026-11-13
Learn More About Enterprise Risk Management
Certification services × risk glossary × latest insights
10 Next steps
Book a consultant (free first diagnosis)
60-minute online meeting on your internal control, management systems and board reporting, with the three things to close first under the code.
Book a consultantRequest scope and timeline
Four-phase scope and schedule based on company size, listing status and existing systems.
Request scopeDisruption risk? See ISO 22301
BIA, RTO/RPO and exercises, bringing continuity onto the same risk map.
See ISO 22301 serviceRelated Deep Insights
In-depth analysis by Winners consultants, 6,000+ words per article
