You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

February 8, 2013

U.S. Cracks Down on IT Theft by Overseas Manufacturers

Bangkok Post, Corporate Counsellor Column

Marking an unprecedented milestone in the fight against unfair competition, a state attorney-general in the United States has taken legal action against a Thai manufacturer that produced and exported products while using stolen IT to unfairly lower its operating costs and undercut competition.

In October 2012, the Massachusetts Attorney General exercised her authority to enforce the state’s unfair competition law by requiring a Thai seafood processor to use licensed IT in its business operations. She announced a landmark settlement with the company.

However, this first-of-its-kind enforcement should serve as no surprise, and is really just a culmination of the continued momentum of U.S. legislative efforts over the past year to preserve domestic jobs and software innovation by ensuring a level global playing field. Recognizing that fair competition fosters respect for the rule of law and intellectual property rights, innovation, and job growth, certain members of the U.S. government have led efforts to restore competitiveness in business by cracking down on IT theft by companies in emerging markets, particularly in the manufacturing sector.

In communications between state attorneys general and the Federal Trade Commission (FTC), officials agreed that stolen IT was destabilizing the pricing market, distorting competition, and posing a serious disadvantage to American firms paying for legal IT. Given that global software theft amounts to US$63.4 billion, as estimated by the Business Software Alliance, it was clear that legal recourse needed to be revised and enforced.

Therefore, in 2011, the states of Washington and Louisiana passed unfair competition laws, which require manufacturers whose products are sold in their states to ensure that they use legal IT (both hardware and software) in their business operations, or risk liability and lost sales opportunities. Manufacturers using stolen IT may be subject to liability if their products are sold, in these states, in competition with products that were made without the use of stolen IT—regardless of where the manufacturing took place or the IT theft occurred.

Subsequently, in November 2011, attorneys-general from 36 U.S. states and three U.S. territories signed a letter to the FTC and head of the Unfair Competition Bureau, announcing their commitment to use their powers to increase enforcement against manufacturers that use stolen IT and asking the FTC to help address the issue.

In April 2012, 16 members of the U.S. Senate Small Business Committee issued a letter to the FTC, urging it to promote manufacturing competitiveness around the world and work with state attorneys-general to fight the problem of IT theft.

In May 2012, the state of Missouri passed a resolution calling on the FTC and state attorney general to address unfair competition, and in June the state of New York adopted a similar measure. In August, 19 members of the U.S. House Small Business Committee followed suit with their own letter to the FTC, asking it to work with the states and federal agencies to “identify the best solutions to fight illegal IT theft.”

In January 2013, the state attorney-general of California filed new lawsuits against two manufacturers, based in China and India, for violating the state’s Unfair Competition Law and for gaining an advantage over American companies by using illegal software in the production of items imported and sold in California. The lawsuits allege that foreign manufacturers who have not paid software licensing fees or other IT costs have a significant advantage over American manufacturers who are already complying with unfair competition and anti-piracy laws.

The lawsuits also state that these companies obtain an unfair advantage because they can use the money saved from using illegal software to hire more employees and grow their business.

Clearly, this series of events demonstrates growing momentum toward even wider coverage and enforcement of unfair competition laws. For manufacturers with global supply chains and a share of exports going into the U.S., the argument could not be stronger that using legal IT is the safest way to protect their businesses and assets, and to build a competitive advantage.

While some manufacturers outside the U.S. may perceive these latest developments as an additional cost of doing business, forward-thinking companies will see the opportunities this trend creates. Thai manufacturers that can adhere to the regulations, create a trustworthy reputation in the U.S. market, and show a strong commitment to supply-chain management and innovation will place themselves in an enviable position compared to noncompliant competitors elsewhere, such as the recently accused companies in China and India.

By ensuring the legality of their software and hardware, Thai manufacturers can help to grow Thailand’s national competitiveness, spur job creation, and protect innovation, while giving themselves an edge in the U.S. market.

RELATED INSIGHTS​ 

August 10, 2026
Thailand’s Office of the Personal Data Protection Committee (PDPC) recently released draft guidance on records of processing activities (ROPA) for personal data controllers and processors under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The draft guidance, which was presented to the public on July 7, 2026, addresses both controller records of collection, use, and disclosure of personal data and processor records of processing activities carried out on behalf of controllers. If implemented, the guidance will significantly expand organizational expectations for ROPA preparation, maintenance, and use across all sectors. Key Takeaways The draft guidance contains several important implications for organizations subject to the PDPA: ROPA reframed as a core accountability tool. The guidance elevates ROPA from an administrative record to a central accountability mechanism, connecting controller duties with recordkeeping obligations. ROPA as a source for privacy notices and governance documents. ROPA should serve as the primary source for privacy notices and align with consent management, retention schedules, DPIAs, incident response plans, and vendor contracts. Expanded scope across all activities. ROPA must cover all processing activities across the organization—including security, finance, HR, and external contractors—with correct controller or processor classification for each. Ongoing maintenance and auditability. ROPA must be updated for any change to systems, purposes, or processors, reviewed at least annually, and maintained with version control and a designated owner. Enhanced vendor, processor, and cross-border transfer requirements. Organizations must document all processors, external recipients, and cross-border transfers, specifying purposes, access scope, and destination countries. Linkage with risk assessment, DPIAs, and LIAs. ROPA should assign risk levels to each activity and identify when data protection impact assessments (DPIAs) or legitimate interests assessments (LIAs) are required, functioning as a risk-management tool. ROPA and data breach readiness. Incomplete ROPA can delay breach response and notification. Organizations should map data flows, vendors,
August 4, 2026
Thailand’s Personal Data Protection Act B.E. 2562 (2019) (PDPA) could soon see some important changes, as a draft bill to amend the PDPA has been introduced in the House of Representatives. The draft amendment is currently in the public consultation phase, with comments accepted from July 16 to August 15, 2026. If enacted in its current form, the amendment would make three key changes: expanding the government exemption to cover anticorruption operations, introducing a statutory definition of “government agency,” and restructuring the lawful bases for personal data processing to align with international standards. Background The PDPA has encountered several enforcement challenges since its implementation, including three core problems identified by the bill’s sponsors: (1) the current exemptions for government agencies do not cover anticorruption and misconduct-prevention operations; (2) the PDPA lacks a clear statutory definition of “government agency,” causing legal uncertainty as to which entities are covered; and (3) the existing framework for lawful bases of data processing does not align with international standards—particularly the multiple-lawful-bases system in the EU’s General Data Protection Regulation (GDPR)—making compliance inflexible for both government and private sector entities. Expanded Government Exemption The current PDPA exempts government agencies performing duties related to national security (including fiscal security), public safety, anti-money laundering, forensic science, and cybersecurity. The proposed amendment adds “prevention and suppression of corruption and misconduct” to this list of exempted functions. This would allow anticorruption bodies—most notably the National Anti-Corruption Commission (NACC), which is identified as a directly affected party—to collect, use, and disclose personal data without being subject to PDPA requirements when carrying out their duties. New Statutory Definition of “Government Agency” Notably, while the current PDPA use the term “government agency” in several provisions, the term is not comprehensively defined, creating potential uncertainty as to its scope. The draft bill therefore
August 3, 2026
On July 23, 2026, the Bank of Thailand (BOT) released for public comment its draft Notification on Digital Channel Security, which would significantly expand the scope and stringency of Thailand’s existing mobile banking security framework. If finalized in its current form, the draft notification would extend mandatory security requirements to credit card providers and credit providers, cover internet banking in addition to mobile applications, phase out SMS one-time passwords (OTPs) for transaction authentication, and introduce biometric verification requirements for high-value transactions. The public comment period is open through August 24, 2026. Background The BOT’s existing Mobile Banking Security Notification, issued in 2024, sets minimum security standards for financial institutions, specialized financial institutions (SFIs), and e-money providers, significantly reducing “money-draining app” fraud. However, fraudsters have since shifted to nonbank providers and internet banking channels, prompting the BOT to propose broader security requirements. Expanded Scope of Regulated Entities and Channels The existing Mobile Banking Security Notification covers only financial institutions, SFIs, and e-money providers offering mobile banking services. The draft expands coverage in two key areas: entities and channels. On the entity side, it adds credit card providers and credit providers that offer fund transfers to third parties at other financial service providers or that provide cash withdrawal services to individual retail customers. On the channel side, it broadens coverage to include internet banking in addition to mobile banking. Strengthened Customer Authentication The draft introduces enhanced authentication requirements in three areas: Service enrollment and device changes. Providers must implement rigorous identity verification, notify customers of enrollment results through out-of-band communication channels, and adopt risk-mitigation measures such as cooling-off periods and temporary transaction limits. Transaction-level authentication. Providers must use two-factor authentication for fund transfers, cardless ATM withdrawals, and transaction limit increases. Secure authentication factors. Key requirements include the following: “What-you-know” factors must
July 28, 2026
Data protection officers (DPOs) have become a fixture of Thailand’s privacy compliance landscape since the Personal Data Protection Act B.E. 2562 (2019) (PDPA) took full effect and the Office of the Personal Data Protection Committee (PDPC) began requiring certain organizations to appoint them. On July 7, 2026, the Office of the PDPC presented draft guidance on DPOs as part of a public consultation on a series of draft personal data protection manuals and recommendations. The draft offers the clearest indication yet of how the regulator expects the DPO role to work in practice, addressing recurring implementation issues under the PDPA—including when an organization must appoint a DPO, how the DPO should operate independently, how to manage conflicts of interest, and how data subjects and regulators should be able to contact the DPO. Because it remains in draft, organizations have an opportunity to weigh the practical implications now before the guidance is finalized. When a DPO Must Be Appointed The draft guidance clarifies the triggers for mandatory DPO appointment, including: Regular and systematic monitoring of personal data or systems on a large scale, such as tracking, analyzing, or predicting behavior, attitudes, or individual characteristics. Core activities involving large-scale processing of sensitive personal data, such as health data, biometric data, or criminal records. Certain foreign-organization representative arrangements. Public-sector coverage under relevant notifications identifying government entities that must appoint a DPO. Processing involving 100,000 or more data subjects may be considered large-scale. The guidance also contemplates voluntary DPO appointment for organizations that wish to raise their privacy governance standards, and such organizations should still comply with the standards applicable to DPOs under the law. Independence and Reporting Lines The draft guidance identifies lack of DPO independence as a core risk because an ineffective or constrained DPO may be unable to raise deficiencies