LIVE · cybersecurity feed
Live wire
Is AI Making Us Worse at Cybersecurity?CVE-2026-114713 · Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command InjectionCVE-2024-10441 · Synology BeeStation OS Vulnerability Linked To Ransomware CampaignsCVE-2020-1337 · Microsoft Windows TOCTOU Race Condition CVE-2020-1337 Linked to RansomwareCVE-2024-58406 · Huatian Dynamic OA8000 Path Traversal Flaw Exploited Upon DisclosureCVE-2026-124218 · Addonsorg Drag and Drop File Upload for Elementor Forms Flaw Exploited Upon DisclosureCVE-2026-114713 · UnrealIRCd Improper Neutralization Flaw Exploited Upon DisclosureCVE-2026-114713 · U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalogFBI flash alert says Artex tool automating cyberattacks at ‘machine speed’CVE-2026-84869 · SCKit abuses ScreenConnect to deploy remote access and target technician sessions
ai

PCI SSC calls for human approval of AI agent actions involving cardholder data

The PCI Security Standards Council (PCI SSC) has released new guidance, "Security Considerations for AI Systems," aimed at securing artificial intelligence deployments within payment environments and defending against AI-assisted attacks. The advisory document, developed in collaboration with industry stakeholders, covers governance, deployment, access controls, testing, and the application of…

ZeroDay News ·

Source: Help Net Security

The PCI Security Standards Council (PCI SSC) has released new guidance, "Security Considerations for AI Systems," aimed at securing artificial intelligence deployments within payment environments and defending against AI-assisted attacks. The advisory document, developed in collaboration with industry stakeholders, covers governance, deployment, access controls, testing, and the application of existing PCI standards, which take precedence over the new recommendations.

A core recommendation emphasizes a "least agency" approach, limiting AI systems to only the access and capabilities necessary for their assigned tasks. Organizations are advised to define an AI system's purpose, permissions, and data access before deployment. A designated human individual should formally accept responsibility for AI output, and specific actions requiring human approval must be clearly defined. For AI agents with access to cleartext cardholder data, explicit human approval is recommended for any actions involving that data.

The guidance also addresses the management of sensitive data and credentials. AI systems should not handle, generate, or manage unprotected high-impact secrets such as passwords or cryptographic keys. Instead, credentials should be managed via secrets-management tools and kept out of source code, prompts, AI context, outputs, and logs. When random values are needed, a trusted random-number generator should be used, with values for passwords or cryptographic keys potentially needing to remain entirely outside the AI system. The PCI SSC recommends using encrypted or tokenized payment data whenever possible, with independent data-loss prevention controls. Logs should support investigations without retaining sensitive payment information.

Organizations are urged to maintain an AI inventory and bill of materials, detailing models, versions, hosting, integrations, data-use and retention policies, and intended users. An acceptable-use policy and technical controls are also recommended to identify and restrict "shadow AI"—unapproved tools used by employees. Access restrictions should be enforced through independent controls like identity-management policies and network isolation. The guidance advises against combining sensitive data access, external communications, and unrestricted input from untrusted sources within a single AI system. If a workflow requires all three, responsibilities should be separated among agents with different permissions.

Testing safeguards before extensive functional or user-acceptance testing is crucial, including adversarial testing to check for bypasses. Continuous monitoring and revalidation throughout deployment are necessary to detect behavioral changes. Review processes should also account for potential "excessive trust" in AI output, which could lead reviewers to overlook mistakes. For monitored autonomous AI, organizations should define permitted actions, approval requirements, shutdown triggers, and procedures for reversing changes, with a human remaining ultimately responsible.

The PCI SSC warns that AI can accelerate vulnerability discovery, exploit development, and social engineering. Recommended defenses include ongoing vulnerability monitoring, prioritizing findings and patches, limiting services and permissions, isolating legacy systems, using phishing-resistant authentication, encrypting sensitive data, and containing breach impacts. AI-generated code and patches should undergo security and functional testing, with reviews checking for embedded credentials, unsuitable dependencies, newly introduced weaknesses, and whether fixes address the underlying problem.

When engaging external AI providers with access to sensitive data, organizations should assess them under applicable third-party service provider requirements. Agreements should clarify responsibility for sensitive information, explicitly prohibit using the organization's data for AI training, provide visibility into subcontractors, and set breach notification terms. Incident response plans and periodic testing should cover prompt injection, model poisoning, actions outside approved scope, and unauthorized AI tools accessing sensitive data.

PCI DSS scoping for AI systems should consider deployment, isolation, access to account data (including data used for training), and the system's ability to affect the security of cardholder-data systems. Access to encrypted or tokenized data, combined with tools that can decrypt or detokenize it, should be treated as access to readable data.

ai
ShareXLinkedInWhatsAppFacebook

More News

view all →
breach

Stolen Fireworks AI Key Led to Cursor Data Breach and Trojanized Claude Code Extension

The compromise of the official Claude Code extension hosted on the Cursor marketplace has been traced back to the theft of an access key originating from a security incident at Fireworks AI. According to a recent update from Cursor, an unauthorized actor obtained an access key that had been issued to Fireworks AI. This key, which was exposed following a breach at the third-party provider,…

breach

Cursor confirms security breach led to malicious Claude Code extension

The AI-powered code editor Cursor has confirmed a significant security breach that resulted in the distribution of malicious software through its marketplace. The incident, which occurred on October 29, involved the compromise of credentials belonging to the AI infrastructure provider Fireworks AI. These credentials allowed unauthorized actors to access internal Cursor systems, leading to the…

aicritical

Is AI Making Us Worse at Cybersecurity?

The integration of artificial intelligence into cybersecurity operations has sparked a debate regarding whether the technology is inadvertently degrading the core competencies of security professionals. While AI is widely acknowledged for its ability to accelerate data processing and increase operational efficiency, concerns are mounting that an overreliance on these tools may be eroding the…

ai

The Security Jobs Growing Around Enterprise AI Agents

The rapid integration of AI agents into enterprise workflows has shifted the focus of corporate security from simple chatbot oversight to the complex management of autonomous, high-privilege digital assistants. While AI adoption was previously confined to isolated chat windows, modern assistants now possess the capability to read shared mailboxes, access internal databases, and execute tasks…

breach

Week in review: Secret stealer hits GitHub repos, Claude Code turned into remote-controlled implant

A widespread credential-harvesting campaign has compromised tens of thousands of GitHub repositories since November 10, 2026. Security researchers identified the operation, dubbed wfx-loot, which relies on stolen GitHub credentials to inject malicious payloads into existing repositories. In at least 1,800 confirmed instances, the injected code successfully executed, exfiltrating GitHub Actions…

security

Upcoming Speaking Engagements

Security researcher Bruce Schneier has announced his upcoming public speaking schedule for the latter half of November 2026. The updates, published on November 14, 2026, outline two specific engagements taking place in the province of Ontario, Canada.