South Korea's SBOM Mandate: What It Requires, and What It Takes to Meet It
| Interlynk

South Korea plans to require SBOMs for public-sector IT by 2027, with procurement restrictions on IT products that have detected vulnerabilities. Here is what is settled, what is not, and what it takes to prepare.
Overview
South Korea is moving software supply chain security from guidance toward a government procurement requirement. On 22 October 2025, as part of a cross-agency Comprehensive Information Security Measures package developed under the leadership of the Office of National Security and announced by the Ministry of Science and ICT (MSIT), the government said it will institute a system requiring a software bill of materials for public-sector IT systems and products starting in 2027, and will restrict procurement of IT products found to have vulnerabilities.
The package was a response to a bad year. A series of breaches in 2025, including the ones at SK Telecom, KT, and Lotte Card, pushed software supply chain security up the national agenda. The same package announced a security inspection of more than 1,600 IT systems across the public, financial, and telecom sectors, and it expanded mandatory security disclosure to all listed companies.
A separate step, eight months later, set the strategic direction. On 24 June 2026, MSIT and the National Intelligence Service (NIS) published a dedicated Software Supply Chain Security Roadmap. It is organized around three goals: preventing supply chain attacks, detecting and responding to them faster, and strengthening the policy foundation, including international cooperation. The roadmap expands the idea of SBOM-based security management. It is not the legal instrument behind the 2027 requirement, but it shows where Korea is heading: using software component information to understand exposure and act on it, not just to file a document.
For vendors, that shift in intent is the part that matters. Generating an SBOM is the starting point. Trusting it, keeping it current, and connecting it to vulnerability response is the harder work, and a submission requirement does not produce any of that on its own. The rest of this post looks at what the government has actually committed to, where the details are still missing, and how to prepare while they fill in.
Key Facts
What is changing: South Korea plans to institute an SBOM submission system for public-sector IT systems and products starting in 2027, announced in the October 2025 Comprehensive Information Security Measures.
Procurement consequence: the same package announced restrictions on procuring IT products with detected vulnerabilities. The exact criteria, how remediation is handled, and how a vulnerability finding maps to exclusion have not been specified.
Who is driving it: MSIT and the NIS, prompted by major 2025 breaches including SK Telecom, KT, and Lotte Card.
What is still unsettled: accepted SBOM formats, required fields, submission and update procedures, and validation criteria have not been published. The June 2026 roadmap sets direction, not the compliance specification.
Why it matters beyond Korea: it follows the United States and the EU Cyber Resilience Act in moving SBOMs from best practice toward regulation, and it adds a commercial edge by linking procurement to vulnerability status.
What the Announcements Actually Establish
The announcement put three separate things together, and coverage tends to blur them. Taken one at a time:
The submission requirement. The October 2025 package states that a system requiring SBOM submissions for public-sector IT systems and products will be instituted starting in 2027. This is a real shift from Korea's 2024 Software Supply Chain Security Guidelines, which were recommendations. What it is not yet is a finished specification. The announcement does not set the accepted formats, the required fields, the submission and update cadence, or how submissions will be checked. Those details decide what compliance actually involves, so they are worth tracking as MSIT turns the policy into operational rules.
The procurement restriction. The government said it will restrict procurement of IT products found to have vulnerabilities. This is the part that gives the mandate weight, because it attaches a commercial outcome to a security finding. It is also easy to overstate. The announcement does not set the vulnerability threshold, say how remediation is weighed, or say whether a match between a disclosed CVE and a submitted SBOM would automatically exclude a product. The direction is clear, but the mechanism has not been announced. Vendors should prepare for a procurement environment where demonstrating what is in a product, and managing its known vulnerabilities, matters more, without assuming they know the exact trigger.
The scope. The SBOM submission requirement, as announced, covers public-sector IT systems and products. The broader security program reaches further: the 1,600-system inspection covered public, financial, and telecom systems, and the disclosure rules now apply to all listed companies. But a wider inspection is not the same as a wider SBOM submission rule. The published announcements do not establish that the 2027 requirement automatically extends to financial, telecom, or platform companies. Korea is clearly raising software supply chain expectations across sectors. It has not said every sector inherits the public-sector SBOM submission requirement.
Korea Is Not Moving Alone
Other regulators got here first, and Korea is working from the same premise: software transparency only matters when it changes a real decision.
In the United States, the first SBOM minimum elements were set in 2021. In July 2026, CISA and international partners published updated 2026 Minimum Elements that add fields such as component hashes, license data, tool information, and generation context, with more emphasis on machine-readable SBOMs. The EU Cyber Resilience Act takes a different route. Instead of a submission to a regulator, it requires manufacturers to document their components and manage vulnerabilities across the product lifecycle. Its reporting obligations for actively exploited vulnerabilities and severe incidents have applied since 11 September 2026, and its main requirements apply from 11 December 2027.
Korea's version pairs an SBOM submission initiative with procurement restrictions on vulnerable products. The mechanisms differ, and Korea has not adopted CISA's elements or the CRA's structure. These are benchmarks, not Korean compliance specs. But the underlying demand is the same in every market: a credible inventory of what is in your product, kept current, and connected to a process that can act when something in it turns out to be vulnerable. A company that builds to meet one of these regimes well is most of the way toward the others.
A Submission Mandate Is Easy to Meet Badly
An SBOM and a useful SBOM are not the same thing, and an example shows how they come apart.
Picture a vendor shipping a firmware-based product to a government agency. It generates an SBOM from its package manifest. The file is valid CycloneDX or SPDX, carries the expected metadata, and submits cleanly. But the firmware also statically links a cryptographic library the package manager never reports, bundles a real-time operating system, and ships a vendored networking stack that was never in the dependency manifest. The vendor has an SBOM. When a vulnerability is disclosed in that TLS library next year, the SBOM will not show it, and neither the vendor nor the agency will know the product is affected.
A useful SBOM has to do three things.
Coverage. It has to capture what actually ships, including the transitive dependencies, statically linked libraries, and bundled runtimes that manifest-based tools can miss. This is hardest for embedded software, firmware, and connected devices, which is exactly the software at the center of Korea's push.
Accurate identification. A list of component names is not enough. Precise versions, package identifiers, supplier details, and dependency relationships are what let a component be matched against vulnerability data at all. A complete-looking SBOM with weak identifiers fails that match quietly, and completeness by itself does not make an inventory trustworthy.
Operational use. When a CVE is published, you need to know which products and releases contain the component, whether it is actually exploitable in your product, and what to do next. That means the SBOM is connected to vulnerability data and a response process, not sitting in a folder.
These are the same two problems we have written about before. One is whether you can trust the SBOM a supplier hands you, since a supplier can submit a valid file that does not describe what shipped. The other is what an SBOM actually does when a component turns malicious, since an inventory tells you where a component is but does not detect bad behavior on its own. Korea's procurement restriction raises the stakes on both, because a weak SBOM is no longer only an audit gap. It can affect whether your product gets bought.
What This Means for Vendors Selling Into Korea
If you supply software or connected devices to Korean public-sector customers, 2027 is a planning milestone, and the work takes long enough that it cannot wait for the final specification. These steps are worth starting now, because they hold regardless of the administrative detail:
Generate SBOMs from actual product releases, not just source manifests, so firmware, embedded components, bundled runtimes, and statically linked libraries are included.
Treat SBOM quality as something you measure. Check completeness, fix missing metadata, and make sure components carry identifiers precise enough for reliable vulnerability matching.
Connect SBOMs to vulnerability management, so a new disclosure gives you a fast, reliable answer about which products and releases are affected.
Stand up a VEX and remediation workflow, since not every vulnerability in a component affects the product that contains it, and you need a defensible way to record and communicate that.
Evaluate supplier SBOMs for coverage, accuracy, and provenance instead of accepting a file because one was provided.
For a baseline of what a usable inventory should contain, our note on the CISA 2026 minimum elements sets a floor that carries across regimes. None of this work is wasted if you also sell into the US or the EU.
Where Interlynk Fits
Interlynk works on the three parts of this that decide whether a mandate produces real security: generating an accurate inventory, measuring its quality, and turning it into vulnerability response.
lynkctl generates build-aware SBOMs for software that is hard to inventory any other way. Manifest-based tools do well with package managers and modern app builds. Firmware and embedded software are where they fall short. lynkctl captures the transitive dependencies, statically linked libraries, bundled runtimes, and container contents a manifest can miss, which is what makes an inventory match what actually ships. For the telecom equipment makers and device vendors at the center of Korea's push, that is the hard part of the problem.
sbomqs, our open-source SBOM quality scorer, evaluates CycloneDX and SPDX SBOMs and flags gaps in component identification, completeness, and metadata against recognized baselines including NTIA and BSI. It makes quality something you can measure instead of assume, and ENISA's October 2026 Technical Advisory lists it among the open-source quality-scoring tools in its SBOM tool stack. That matters most when SBOMs change hands. A device maker receiving an SBOM from a supplier, and a vendor producing one for a customer, both need a way to tell whether it is complete and accurate enough to base a vulnerability decision on.
The Interlynk platform ingests SBOMs, evaluates their quality, risk-assesses components against vulnerability and advisory data, manages VEX assertions, and notifies stakeholders when a new disclosure changes the exposure of something already shipped. That is the layer Korea's approach quietly assumes a vendor already has. Interlynk does not scan for or detect malware, and it is not a Korean regulatory certification. It is how the inventory, the matching, and the response work across the product lifecycle.
The Bottom Line
South Korea's 2027 SBOM initiative is a real step. It announces an SBOM submission requirement alongside procurement restrictions for vulnerable IT products, which brings software transparency and vulnerability management closer to government purchasing decisions. The implementation details still have to emerge, but vendors do not need every specification settled to start, because the hard parts are the same under any final rule.
The part to get right is the gap between having an SBOM and being able to use one. Make sure the inventory matches what actually ships, that its components can be identified reliably, and that your organization can respond when a disclosure changes its risk picture. Do that, and meeting the submission requirement is straightforward. Meet only the submission requirement, and you have a file that passes a check but does not help anyone when a vulnerability appears.
Frequently Asked Questions
Is South Korea requiring SBOMs? Yes. In its October 2025 Comprehensive Information Security Measures, the government announced a system requiring SBOM submissions for public-sector IT systems and products starting in 2027, along with restrictions on procuring IT products with detected vulnerabilities. Detailed implementation requirements have not yet been published.
When does Korea's SBOM mandate take effect? The public-sector submission system is set to begin in 2027. It builds on 2024 guidance and a June 2026 MSIT and NIS roadmap. Vendors should watch for later government guidance that sets the exact formats, fields, and procedures.
Who has to comply? As announced, the SBOM submission requirement covers public-sector IT systems and products. The broader security program also reaches financial, telecom, and platform systems through inspections and disclosure rules, but the published announcements do not establish that the 2027 SBOM submission obligation automatically applies to those sectors.
What is SBOM-based security management? It is the direction behind Korea's roadmap: using software component inventories for ongoing supply chain security. That means identifying components, monitoring vulnerabilities, determining product exposure, and coordinating remediation, not just generating and submitting an SBOM once.
How is Korea's approach different from the EU CRA and US requirements? They share a focus on transparency and vulnerability management but use different mechanisms. Korea has announced public-sector SBOM submissions and procurement restrictions on vulnerable products. The US has set SBOM minimum elements and federal procurement expectations. The EU CRA requires manufacturers to document components and manage vulnerabilities, with reporting obligations applying since September 2026.
What should vendors selling into Korea do now? Generate accurate SBOMs for actual product releases, including embedded and bundled components. Measure and improve SBOM quality. Connect SBOMs to vulnerability monitoring. Stand up a VEX and remediation workflow. And evaluate supplier SBOMs for coverage and accuracy. These steps prepare you for Korea and for other international requirements at the same time.
Sources
MSIT, "Government Announces Comprehensive Information Security Measures"
DigitalToday, "Science ministry and NIS unveil software supply chain security roadmap" (June 2026)
TechCrunch, "A breach every month raises doubts about South Korea's digital defenses"
Finite State, "Korea Introduces Mandatory SBOM Submissions: What It Means for Product Security"
2026 Minimum Elements for a Software Bill of Materials (CISA and international partners, via ACSC)
ENISA, Technical Advisory for Software Bill of Materials (v1.10, October 2026)
About Interlynk. Interlynk helps teams generate, manage, and operationalize SBOMs across the software supply chain. sbomqs, its open-source quality scorer, assesses SBOMs against NTIA, BSI, and other baselines. lynkctl produces build-aware SBOMs for embedded and firmware software, capturing bundled runtimes and transitive, static, and SDK components with precise identifiers. The Interlynk platform ingests SBOMs and CBOMs, evaluates them for completeness and quality, risk-assesses components against vulnerability data, manages VEX assertions, and notifies teams when exposure changes.
This article is informational and does not constitute security, legal, or compliance advice. Regulations and their implementation details evolve; confirm current requirements, dates, and scope against the primary sources and official Korean government guidance before acting.