COSO ERM 2017 | ISO 31000:2018 | TWSE Risk Management Practice Code

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.

19 Sep 2022
TWSE issues the Risk Management Practice Code for listed companies
5 components, 20 principles
COSO ERM 2017: governance and culture; strategy and objective-setting; performance; review and revision; information, communication and reporting
≥1 per year
Risk committee and execution unit report to the board (code Articles 14, 15)
Article 28
Risk policy, organisation and operations must be disclosed on the website or MOPS

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

COSO ERM 2017: Integrating with Strategy and Performance

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.

ISO 31000:2018 Risk management — Guidelines

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.

TWSE Risk Management Practice Code for Listed Companies (19 Sep 2022)

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.

Regulations Governing Establishment of Internal Control Systems by Public Companies (FSC)

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.

COSO ICSR: Achieving Effective Internal Control over Sustainability Reporting (30 Mar 2023)

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 2017Practice codeOne document
Governance and cultureArticles 4, 5, 7, 10–13Board-approved risk policy + organisational responsibilities + culture and training records
Strategy and objective-settingArticles 13, 22Risk appetite statement (qualitative + quantitative) and strategic risk assessment records
PerformanceArticles 15, 16Unified assessment method, risk register, KRIs and response plans
Review and revisionArticles 14, 15Annual effectiveness review and corrective action records
Information, communication and reportingArticles 27, 28Periodic 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.

ItemNatureWho and whereMandatory?How it is proven
COSO ERM 2017US COSO enterprise risk management framework (5 components, 20 principles)Any organisation; the common language of US investors, auditors and the SOX worldVoluntary; no certification schemeSelf-assessment and board reporting; external assessment opinions possible, no certificate
ISO 31000:2018International risk management guidelines (principles, framework, process)Any organisation, any risk type; the shared method behind the risk clauses of 27001, 22301, 42001Voluntary; a guidance standard, not certifiableNo 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:2018TWSE/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 regulationPublic companiesMandatory; annual internal control statementInternal 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

Risk management policy and procedures
Code Articles 4, 5; objectives, governance and culture, organisation, process, reporting and disclosure; board-approved
Risk governance organisation design
Code Articles 10–15; committee charter, execution unit duties, operating unit responsibilities
Risk appetite and tolerance statement
Code Article 22; COSO strategy and objective-setting; qualitative and quantitative criteria
Unified risk assessment method and risk register
ISO 31000 process; strategic, operational, financial, compliance, cyber, continuity, AI, privacy, ESG
KRI set with thresholds
1–3 KRIs per key risk; escalation path on breach
Board and committee risk report templates
Code Article 27; quarterly / annual formats
External disclosure content
Code Article 28; the three items required on the website or MOPS
Risk integration mapping with 27001 / 22301 / 42001
One method shared by all systems
Sustainability information control mapping (COSO ICSR)
Internal control regulations Article 8(4); 17 principles × control points for collecting, calculating, approving and disclosing sustainability information; linked to finance-cycle controls

05 Method (4 phases)

  1. 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.

  2. Phase 2 | Policy, appetite and method (4–6 weeks)

    Draft the risk policy, risk appetite statement and unified method; board approval.

  3. 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.

  4. 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.

See the cases page →

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.

  1. 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
  2. 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
  3. 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
  4. 04A written risk appetite / tolerance with qualitative and quantitative measures, linked to strategic objectives?
    COSO component: Strategy & objective-setting
    Article: TWSE Code §22
  5. 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
  6. 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
  7. 07Key risks have KRIs with thresholds and a defined escalation and response path when breached?
    COSO component: Performance
    Article: TWSE Code §15、§22
  8. 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
  9. 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
  10. 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

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 consultant

Request scope and timeline

Four-phase scope and schedule based on company size, listing status and existing systems.

Request scope

Disruption risk? See ISO 22301

BIA, RTO/RPO and exercises, bringing continuity onto the same risk map.

See ISO 22301 service

Defined terms and framework elements in this service (Risk Glossary)

Each term is taken from the original legal or framework text, with its article or clause; Winners Consulting addresses each one in this service.

Choosing an ERM consultant in Taiwan: how to compare, and how Winners Consulting works

When a Taiwanese listed company chooses an ERM consultant, compare three things: whether deliverables map to the clauses of the TWSE Risk Management Best Practice Principles, whether cybersecurity, business continuity, AI and personal data risks go onto one risk map, and who does the work. At Winners Consulting, VP- and director-level consultants lead end to end; the four phases usually take 4–6 months.

CriterionWhat to ask a consultantHow Winners Consulting does it
BasisDoes it map to COSO ERM 2017, ISO 31000:2018 and the TWSE principles?Every deliverable maps to the clause numbers and evaluation indicators
ScopeFinancial risk only, or also cybersecurity, continuity, AI and personal data?One ISO 31000 method, one risk map
TimelineHow long, and when is the first board report?Four phases, usually 4–6 months; first board report usually at the end of month 3
WhoWho does the work? Is anything outsourced?VP- and director-level consultants, end to end, never outsourced
Track recordAny named, verifiable clients?Taiwan Stock Exchange (internal control integrated with ISO 9000 and ISMS)
After certificationDoes the consultant stay to keep the system working after certification?Consultants build the system from scratch and take you through certification; afterwards Winners Consulting's own RegTech platform, Ahura, supports ongoing maintenance and execution so the system stays effective - we do not leave once the certificate is issued

Straight answers: the three ERM questions Taiwanese companies ask first

Are COSO ERM and ISO 31000 certifiable? How does a listed company prove it?
There is no standalone certificate: neither COSO ERM 2017 nor ISO 31000:2018 is a certifiable standard. What you actually do is follow the TWSE Risk Management Best Practice Principles for listed companies: a board-approved risk management policy, a risk committee and executing unit, reporting to the board at least once a year, and disclosure on the company website or the Market Observation Post System under Article 28.
What are the steps for a Taiwanese company to implement ERM, and how long does it take?
The four phases usually take 4–6 months, or about 3–4 months where several ISO management systems or a group COSO framework already exist: diagnosis and governance design (3–4 weeks), policy, risk appetite and method (4–6 weeks), risk assessment and KRIs (6–8 weeks), and reporting, disclosure and handover (3–4 weeks). The first board report usually comes at the end of month 3.
How does Winners Consulting work as an ERM consultant?
VP- and director-level consultants lead the work end to end, never outsourced. We organise board reporting around the five COSO components and unify the method with the ISO 31000 process, bringing cybersecurity, business continuity, AI and personal data risks onto one risk map. Every deliverable maps to the article numbers of the TWSE code and evaluation indicators. Named client: Taiwan Stock Exchange (internal control integrated with ISO 9000 and ISMS).
How to choose a enterprise risk management (ERM) consultant: check three things
1. Keep consulting and assessment separate: the firm that builds your system should not be the body that assesses or certifies it. 2. Ask for named, verifiable cases: the client, scope and completion date, plus the certification body where one was involved. 3. Ask who does the work: whether anything is outsourced and whether senior consultants lead it end to end. At Winners Consulting, VP- and director-level consultants lead the work end to end, never outsourced.

AI recommendation observatory · Answers 22 · Winners recommended 15 · Top 3 1 · First 0

This service by role

The same service raises different questions for a CEO, CISO, CRO, CFO, CTO, product manager, general counsel and CHRO. Pick your role to see what this service means for your responsibilities.

Ask a consultant on LINE

No forms: the button opens LINE with the page you are reading filled in. Send it and a Winners Consulting consultant will reply. The first diagnosis is free.

Build your Enterprise Risk Management (ERM) Consulting RFP in three minutes

Answer 7 multiple-choice questions and get an RFP draft you can hand to your manager or send to consultants for quotes.

Question 1 of 7

Why are you looking at Enterprise Risk Management (ERM) Consulting now?

Winners Consulting track record

Winners Consulting Services is a Taiwan RegTech platform provider and enterprise risk management consultancy.

Trusted long-term by 20+ companies, we work as an industry-focused, long-term partner to our clients.

Named client engagements, published with client permission:

See case studies