惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
aimingoo的专栏
aimingoo的专栏
月光博客
月光博客
博客园 - Franky
Martin Fowler
Martin Fowler
U
Unit 42
阮一峰的网络日志
阮一峰的网络日志
Recent Announcements
Recent Announcements
The Cloudflare Blog
博客园 - 聂微东
酷 壳 – CoolShell
酷 壳 – CoolShell
宝玉的分享
宝玉的分享
J
Java Code Geeks
B
Blog RSS Feed
博客园 - 三生石上(FineUI控件)
MongoDB | Blog
MongoDB | Blog
腾讯CDC
博客园_首页
博客园 - 司徒正美
D
DataBreaches.Net
I
InfoQ
GbyAI
GbyAI
IT之家
IT之家
罗磊的独立博客

PCI Perspectives

Just Published: Security Considerations for AI Systems Just Published: PCI Key Management and Operations (KMO)™ Standard v1.0 The AI Exchange: Innovators in Payment Security Featuring Integrity360 Coffee with the Council Podcast: Celebrating 20 Years of Securing Payment Data The Quantum Leap: Preparing for Post Quantum Cryptography Featuring Futurex 2026 Asia-Pacific Community Meeting Agenda Highlights The AI Exchange: Innovators in Payment Security Featuring GM Sectec Coffee with the Council Podcast: Meet This Year’s Europe Community Meeting Keynote Speaker, Ken Hughes Join Us at the Payment Industry Events of the Year Coffee with the Council Podcast: Meet This Year’s Asia-Pacific Community Meeting Keynote Speaker, CJ Meadows 2026 Europe Community Meeting Agenda Highlights Mapping PCI DSS v4.0.1 to the NIST Cybersecurity Framework 2.0 2026 North America Community Meeting Agenda Highlights Meet the Council’s New Head of Business Operations and Risk Management The AI Exchange: Innovators in Payment Security Featuring PCA Cyber Security Enhance Your Community Meeting Experience with Interactive Workshops The AI Exchange: Innovators in Payment Security Featuring PROSA Bring PCI SSC Training to Your Organization with the New Training Venue Host Program The AI Exchange: Innovators in Payment Security Featuring Utimaco Coffee with the Council Podcast: Meet This Year’s North America Community Meeting Keynote Speaker, Sharon Gai Welcome Our Newest Associate Participating Organizations The AI Exchange: Innovators in Payment Security Featuring SecurityMetrics PCI SSC Publishes New Guidance on Compensating Controls and the Customized Approach Spotlight On: Dreamplug Technologies Private Limited (CRED), a New Principal Participating Organization Request for Comments: PCI Data Security Standard (PCI DSS) v4.0.1 The AI Exchange: Innovators in Payment Security Featuring In-Solutions Global Ltd Coffee with the Council Podcast: Nominate Now for the Global Executive Assessor Roundtable (GEAR) PCI SSC Publishes PCI PTS HSM v5.0 Request for Comments: PCI Secure Software Lifecycle Standard v2.0 Spotlight On: Worldline, a New Principal Participating Organization
The AI Exchange: Innovators in Payment Security Featuring...
Alicia Malone · 2026-07-27 · via PCI Perspectives

Welcome to the PCI Security Standards Council’s blog series, The AI Exchange: Innovators in Payment Security. This special, ongoing feature of our PCI Perspectives blog offers a resource for payment security industry stakeholders to exchange information about how they are adopting and implementing artificial intelligence (AI) into their organizations.  

In this edition of The AI Exchange, atsec Principal Consultant, QSA, Yan Liu, offers insight into how his company is using AI, and how this rapidly growing technology is shaping the future of payment security. 

How has your AI strategy evolved over the past 12–18 months? 

Within atsec, we have established guidelines for the secure and responsible use of Artificial Intelligence (AI) services within the organization. Given our responsibility to handle sensitive information from both customers and internal sources, alongside the high standards required by stakeholders, it is essential that AI tools are utilized in a manner that minimizes security risks.

Our principles include: 

  • Internal AI Services: Internal AI tools hosted on the company infrastructure are preferred due to better control over data security. However, it is critical to ensure that proper data segregation between different projects, and that principles of least privilege remain effective. 

    Our focus with AI/Automation tools is on commercial management, project management, general testing methodology, and the reporting tools (e.g. PCI DSS ROC). 

  • External AI Services: The use of external AI services, especially those managed by untrusted third parties, must be approached with caution. atsec employees must only use well-established services from known organizations to ensure security, reliability, and compliance with regulations. No confidential or internal information can be shared with these services.  
  • Built-in AI Services: A recent development is that products and software tend to include various AI functionality by default. It may be ambiguous whether such functions are internal (e.g., on device) or external, and it is also difficult to control the information processed. Therefore, such functions are considered to be similar to telemetry and must be disabled. 

What is one AI initiative that has already delivered a measurable impact, and what made it successful? 

In different atsec global offices, we are developing in-house AI solutions on systems that are physically located in our offices, ensuring that all data remains on premises. atsec team has successfully implemented this using open-source models, for example: Llama, working with OpenSSL library code.

Through our current usage, we have improved efficiency and quality in aspects including test preparation, project management, and reporting. For vulnerability discovery, AI provides valuable references and facilitates the development of auxiliary scripts.

Regarding the cryptography testing area, we are currently in the process of incorporating specific retrieval-augmented generation (RAG) and fine-tuning the model with standard requirements (e.g., FIPS 140) to improve accuracy. 

How are you approaching AI governance, particularly around data privacy and security? 

atsec's general principles for information security are also applicable for AI. As such, AI services, especially those hosted externally, must never process any non-public data or information, classified as either atsec internal or atsec confidential. This also extends to customer data and all personally identifiable information. Any data used with AI services must always be anonymized and/or masked to reduce risk and note that even public information may pose a risk.

AI tools are subject to the same rules and requirements of other tools and software as delineated in this policy regarding the employ of internal and confidential information. It has become common that many software applications and tools provide AI features, such as AI Assistant in Adobe Acrobat, CoPilot features in Microsoft 365, AI in Webex, AI in Feishu, and others.

As a rule of thumb, the models and databases related to these AI tools are maintained by the providers and vendors, are property of them, and are not maintained locally in employee devices. In addition, usually the usage agreement for those tools gives the providers the right to use and store the information given to the tools, which will then be used to further train their models. Thus, when prompts contain some internal or confidential information, that information will be transferred to the provider of the tool, violating atsec NDAs with customers.

As such, using AI tools with atsec internal and confidential information is forbidden unless the specific AI tool is explicitly allowed for use for specific projects/situations. atsec has established the internal policy “Use of AI within atsec” since 2023, and the policy is well-maintained internally. All colleagues need to be aware of and follow the requirements. 

What challenges have become more apparent as AI capabilities have matured? 

Quality and Accuracy of AI-Generated Output.

AI may be leveraged to improve efficiency and streamline repetitive or time-consuming tasks. However, it is not intended to replace human critical thinking, decision-making, or judgment. All AI-generated content must be carefully reviewed and validated by employees to ensure accuracy and alignment with company standards. The author is always responsible for all content produced with any AI service.

AI tools are tools. They shall not be used for authorship or produce work on behalf of the human. We do NOT allow the public AI tools to process any customer confidential data, even with commercial licenses that atsec has purchased from trusted AI suppliers.

While AI may be employed to generate output, it is critical to maintain the high standards expected by the organization and its stakeholders. To ensure this, all AI-generated content, whether it involves code, documentation, reports, or any other deliverable, is expected to undergo verification and quality assurance by the responsible employee. Therefore, atsec colleagues are required to: 

  • Manually review AI-generated output: Before any AI-generated material is used, the employee must review it in detail to verify its accuracy, completeness, and relevance to the task at hand. This includes correcting any errors, omissions, or inconsistencies that may arise from AI output. Note also the potential for security issues, where executing unknown code from an AI is no better than code copied from untrusted sources online.
  • Follow internal quality assurance (QA) processes: AI-generated output must not bypass the organization’s established QA protocols. In addition to personal verification, the output should undergo the regular QA checks applied to non-AI-generated work to ensure it meets internal standards.
  • Accuracy in sensitive areas: Particular attention should be given when AI tools are used to handle or generate content that in some regard affects project deliverables. Employees must ensure that AI output does not compromise the accuracy or confidentiality of such data. Without full insight, the risk of false positives and false negatives increases.
  • Documentation and accountability: Employees should document where AI has been used for important work, and the steps taken to verify and validate AI-generated content. This ensures full accountability for any output integrated into projects or delivered to clients. 

What advice would you provide for an organization moving from early AI adoption to broader implementation? 

The most suitable use of AI is customer and product agnostic tasks handling non-sensitive information. It is acceptable to use the service to generate a description or a script and then have the tool to change/improve it. Rather, a more restrictive approach should be selected where the service is used to improve isolated parts of the work.

Note that even publicly available information should be used only with caution. Consider operations of security! All input provided to an AI service relating to any project must be considered not only by itself, but in the context of other related input. For example: if an AI service is used to assist with installing and configuring a specific product, and that same service is then used to develop scripts to execute a specific attack. Regardless of whether all information was public, the potential result is data leakage.

Examples of appropriate usage: 

  • Test Tool Creation: AI may assist in the development of internal testing tools or scripts. This includes generating code snippets and automating testing processes.
  • Technical Research: AI can be used to gather or summarize technical information, research new developments, or explore potential solutions to technical problems.
  • Production of Guidelines or Policies: AI tools may be employed to draft technical or procedural guidelines.
  • Production of Training Materials: AI may assist in creating training materials, including generating initial drafts for presentations, instructional documents, or video scripts.
  • Assistance with Phrasing and Language: AI tools can help with minor phrasing tasks but should only be used cautiously in official communication.
  • Scripting: While AI should not be used to handle any large amount of information (e.g., data analysis), it may very well be used to help create scripts that may perform such tasks. An AI tool may efficiently suggest bash or regex code to help solve such tasks.
  • Non-sensitive Prototyping: For exploratory or proof-of-concept projects where no sensitive data is involved, AI tools can be used to speed up the prototyping process, particularly in areas such as design or early-stage development. 

What AI trend are you most excited about? 

The trend I look forward to most is accessible, human-centric AI. First, AI is moving from large cloud models to lightweight local applications, which better protects user privacy and security.

Second, AI is deeply integrated into our industry, from payment functions to cybersecurity implementation and test/verification. Most importantly, it focuses on human-AI collaboration — AI takes over repetitive tasks, while people focus on creativity, thinking, and decision-making. 

View More Content on Artificial Intelligence

Learn More About atsec