<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Payment Security on After the Code</title><link>https://windshock.github.io/en/tags/payment-security/</link><description>Recent content in Payment Security on After the Code</description><generator>Hugo -- 0.145.0</generator><language>en-US</language><lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/en/tags/payment-security/index.xml" rel="self" type="application/rss+xml"/><item><title>You Cannot Assess the Security of External SDKs by Checking Cryptographic Algorithms Alone</title><link>https://windshock.github.io/en/post/2026-08-24-external-sdk-security-assessment/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/en/post/2026-08-24-external-sdk-security-assessment/</guid><description>Algorithm names like AES-256 or TLS reveal nothing about how keys are generated, who controls the endpoint, or whether a response binds to the real transaction. A broader, evidence-based assessment model for external SDKs and native binaries.</description></item></channel></rss>