Tag: cyber security

  • From Game Platforms Using CPU’s fTPM to Trace Cheating Players: Network Privacy and Network Security Cannot Coexist

    From Game Platforms Using CPU’s fTPM to Trace Cheating Players: Network Privacy and Network Security Cannot Coexist

    The author: Certified Information Systems Auditor, System Analyst (China Software Exam), Master of Software Engineering

    I recently came across a news article about a player who purchased a used CPU and found himself banned from a gaming platform. For every time he launched a game, he got kicked out. After contacting the platform’s customer support, he learned the CPU had been blacklisted because its previous owner was a cheater.

    In my view, this matter goes far beyond anti-cheat measures. It represents a form of physical-device-based identity tracking that directly undermines network privacy.

    1. The Present and The Past

    Here is the link to the news article. Interested readers can look into it themselves for more details:

    https://www.heise.de/en/news/Used-processor-leads-to-game-ban-11471562.html

    As the title suggests, what I’m most interested in is how the gaming platform leverages the CPU for identity tracking. Before diving in, it’s worth revisiting a piece of history. This is the Processor Serial Number (PSN) feature that Intel once embedded in the Pentium III CPU [1]. The news article also references this historical episode.

    At the time, Intel’s original intent was to enhance network security in e-commerce and other domains by providing a unique serial number in each CPU, thereby supporting an identity verification mechanism that tightly binds transaction parties to their transactional behavior. However, once this feature was released, it sparked enormous controversy: transactions became more secure, but privacy went to zero. Because this unique, unchangeable hardware ID was arguably the best method for tracking online users [2].

    In the end, this controversy led Intel to announce the removal of the PSN feature from its CPUs.

    Considering how sophisticated targeted mobile ad delivery has become today, if the PSN feature existed in modern mobile CPUs, ad brokers would be laughing all the way to the bank.

    So my first reaction to this news was: could the CPU mentioned in the article also have an undocumented PSN-like feature?

    1. How TPM Creates Conflict Between Privacy and Security

    Looking more closely at the news report, the author hypothesized—based on some statements released by the gaming platform—that the platform leveraged the TPM (Trusted Platform Module) functionality built into the CPU. Different CPU vendors name this technology differently; in the case covered by the news (AMD CPUs), it’s called fTPM (firmware-TPM), while on Intel CPUs it’s named PTT.

    I found similar explanations from other sources. For instance, ROG (Republic of Gamers), well-known among gaming enthusiasts, explicitly states that to combat cheating, players must enable Secure Boot and TPM 2.0 (including fTPM) in their computers [3].

    Therefore, I agree with the news author’s hypothesis: it is highly likely that this gaming platform software installed a kernel-mode driver on players’ computers, thereby leveraging the CPU’s TPM functionality to write a unique ID to fTPM and subsequently reading that ID to track and identify players.

    Technically speaking, this isn’t particularly complex.

    But when it comes to TPM, I have quite a bit to say.

    It should first be noted that TPM is indeed a foundational component of modern network security. Its core positioning is as a “trusted hardware root,” with functions including secure storage of encryption keys, measurement and verification of the boot chain integrity at system startup, binding user credentials for operating system login, and providing remote attestation and device identity verification.

    For example, Windows BitLocker disk encryption, Windows Hello and PIN login credentials, and even the currently popular PassKey login technology all to some extent rely on and utilize TPM.

    But TPM’s ability to deliver these security functions hinges on the unique identifiers stored within it, the most critical being the Endorsement Key (EK):

    The EK is a pair of asymmetric keys burned into the TPM at the factory. The private key cannot be exported, while the public key and its certificate are readable. The EK is globally unique, immutable by the user, and non-migratable.

    This means that as long as a TPM exists, the device’s identity identifier is already firmly established.

    And for TPM functionality embedded in a CPU… this is essentially another PSN.

    When anti-cheat drivers (running at kernel level), enterprise management agents, firmware components, or even malware have the ability to access the TPM interface, they can read this identity identifier and achieve persistent device tracking. Even if a user wipes all user data and reinstalls the operating system, the device can still be identified.

    Moreover, this is not some undocumented feature. TPM access mechanisms already have standardized interfaces and API wrappers; any kernel-level driver has the capability to access them. Therefore, the gaming platform’s use of TPM for user tracking doesn’t exploit any vulnerability or backdoor.

    So this news once again highlights: any product based on the design philosophy of “determining identity through hardware” will inevitably give rise to the conflict between network privacy and network security.

    Furthermore, this problem is fundamentally an inherent contradiction in system-level security identity mechanisms: network security emphasizes identity confirmation, while network privacy requires identity concealment.

    The former requires that devices, users, and communication channels can all be reliably identified and verified—otherwise encryption, authentication, and access control are impossible; the latter seeks to minimize persistent identifiers that could be correlated, avoiding the long-term assembly of behavior trails, device fingerprints, and usage patterns into profiles. These two share the same underlying identity mechanism at the technical level, yet pull in opposite directions in terms of values—the more security relies on stable hardware anchors, the more easily privacy is betrayed by those anchors.

    This is the essence of the TPM dilemma: it is both a shield against attacks and a window exposing identity—a classic case of being unable to have your cake and eat it too.

    And it must be mentioned that TPM itself is also prone to bugs. I have previously written about TPM vulnerabilities on my blog:

    “As with any software, the TPM 2.0 module library has been found to have two vulnerabilities, rated 7.8 and 5.5.”
    https://www.wavecn.com/content.php?id=357 (Only in Simplified Chinese)

    And just recently in August 2026, AMD confirmed two additional fTPM vulnerabilities numbered CVE-2026-6726 and CVE-2026-6727, rated 8.5 and 8.3 respectively—quite high [4]. While exploiting these two vulnerabilities requires local privileged user access and isn’t particularly easy, users should still promptly update their BIOS to mitigate these vulnerabilities.

    1. Something Should Be Done

    From the current network security landscape, enabling TPM does more good than harm. Although the contradiction is inherent, readers can still take some steps—for example, clearing TPM records after purchasing used computer devices. While this doesn’t guarantee complete protection against encountering situations like the buyer in the news report, from a perspective of balancing security and privacy, it’s something that should not be overlooked.

    Scenario 1: Clearing TPM in a Windows Environment

    1. First, check whether the device is currently using BitLocker. If the system drive has BitLocker encryption enabled, clearing TPM will inevitably trigger recovery mode, requiring a recovery key to unlock the disk—effectively rendering the TPM clearing meaningless.
    2. For computers with BitLocker already enabled, disable BitLocker first. The method is to right-click on the encrypted drive letter, select “Manage BitLocker,” and then in the appearing “BitLocker Drive Encryption” interface, select “Turn Off BitLocker” for all drives. The disabling process takes some time.
    3. Back up and record Windows login credentials, especially distinguishing between PIN login and password login. A PIN is not a password; after clearing TPM, PIN login may become invalid. Biometric methods such as fingerprint login will essentially no longer work.
    4. Press Win+R, type tpm.msc to open the TPM Management Console, click “Clear TPM” in the right-hand operations pane, and follow the prompts to restart.
    5. Restart and confirm the clearing. During restart, if the computer displays a prompt similar to “Press Y to reset fTPM / Press N to keep previous fTPM record,” select Y to confirm.
    6. After restarting and logging into Windows with a password, re-enable BitLocker and reconfigure login PIN, etc.

    Scenario 2: Clearing TPM in a BIOS Environment

    If the used device is in a bare-metal state or the system cannot boot into Windows, you can clear TPM directly in the BIOS/UEFI.

    1. At computer startup, press the specific key to enter BIOS/UEFI. Which key to press depends on the device’s manual—today it’s not just the Del key; F2, F10, or even ESC keys are possible.
    2. Locate the TPM-related options, which may be buried somewhat deeply and may have different naming conventions. Most commonly, they are located under menus named Security, Advanced, or Trusted Computing. Option names may include TPM 2.0 Security, AMD fTPM, AMD fTPM Configuration, Intel PTT, Intel Platform Trust Technology, Security Device Support, etc.
    3. Execute the TPM clear operation. After finding and entering the TPM management function, look for options such as Clear TPM, Reset TPM, or Clear Security Device on the operation interface, select and confirm Yes.
      Note: We are clearing the old state, not disabling TPM functionality, so TPM should be kept in the Enabled state.
    4. Save configuration and restart. Then, when reinstalling the operating system, configure BitLocker, PIN, and other features as needed.

    This process can help you clear the previous owner’s user state and data remnants. However, for devices that have already been blacklisted by gaming platforms via TPM identity, clearing TPM may not necessarily resolve the issue, because what was recorded might be based on the EK, which cannot be cleared.

    [1] Intel Processor Serial Number Q&A for OEMs

    https://www.theregister.com/off-prem/2000/05/04/intel-processor-serial-number-qa-for-oems/488918

    [2] Intel Case – Processor Serial Number (PSN)

    https://courses.ischool.berkeley.edu/i224/s99/GroupJ/presentation.pdf

    [3] Fix Game Launch Errors Update TPM2.0 in BIOS Utility

    https://rog-forum.asus.com/t5/technologies-explained/fix-game-launch-errors-update-tpm2-0-in-bios-utility/ba-p/1141117

    [4] AMD ID: AMD-SB-7064, Trusted Platform Module (TPM) Reference Code Errata

    https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7064.html

    ~ End ~

  • A Glimpse into the 2025 Hong Kong Cybersecurity Summit

    A Glimpse into the 2025 Hong Kong Cybersecurity Summit

    This year’s Hong Kong Cybersecurity Summit was postponed to November due to a typhoon. Coincidentally, Sender Su, Founder of Langji Tech, had just wrapped up a major phase of work and was able to attend this industry gathering.

    The summit’s theme—“Future-Proofing Digital Infrastructure: Harnessing AI for Enhanced Security and Resilience”—reflected the growing centrality of artificial intelligence in cybersecurity. While last year’s event featured distinguished academicians as keynote speakers, this year’s program placed even greater emphasis on practical AI applications. With AI now deeply embedded in both offensive and defensive cyber operations, discussions naturally revolved around its evolving role and implications.

    Speakers explored how AI is being deployed in cyber offense and defense, as well as the security measures needed to protect AI systems themselves—particularly large language models (LLMs). Data security surrounding LLMs emerged as a recurring focal point, aligning closely with Langji Tech’s forward-looking strategy. In fact, our team began strengthening cybersecurity frameworks for enterprise LLM adoption well before these concerns gained mainstream attention.

    Beyond AI, the summit also addressed significant shifts across the broader security landscape—from infrastructure design to regulatory compliance.

    Globally, for instance, SSL/TLS certificate lifespans are being progressively shortened. According to the CA/Browser Forum’s approved roadmap, starting March 15, 2029, all newly issued SSL/TLS certificates will have a maximum validity period of 47 days. While this enhances overall security, it introduces new operational risks—most notably, a higher likelihood of accidental certificate expiration due to more frequent renewal cycles. Meanwhile, the integration of post-quantum cryptographic algorithms into digital certificates is also gaining momentum, with gradual adoption expected in the coming years.

    On the local front, Hong Kong’s first Cybersecurity Law—the “Security of Critical Infrastructure (Computer Systems) Ordinance”—will take effect on January 1, 2026. This legislation will impose clear compliance obligations on responsible personnel within critical sectors. Compounding the pressure, threat actors are increasingly leveraging AI to conduct sophisticated intrusion, data theft, and ransomware campaigns. As in last year’s summit, many attendees were seen snapping photos of presentation slides during threat landscape briefings—a telling sign of the mounting anxiety in the room.

    Full text of the ordinance (in English):
    https://www.legco.gov.hk/yr2025/english/ord/2025ord004-e.pdf

    Among exhibitors, one mainland-based headline sponsor stood out for its strong localization efforts—particularly in building a capable local team well-integrated into the Hong Kong market.

    As a final note—and a uniquely Hong Kong touch—the summit doubled as a civic engagement platform ahead of the upcoming Legislative Council elections. Campaign flyers were distributed throughout the venue, and nearly every government-affiliated speaker concluded their talk with an earnest call for attendees to vote. CrossWise InfoTech joins in this spirit of civic participation and encourages everyone to cast your ballot on December 7!

    References:
    CA/Browser Forum 官網:
    https://cabforum.org/

    Ballot SC081v3:Introduce Schedule of Reducing Validity and Data Reuse Periods
    https://cabforum.org/2025/04/11/ballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods/