The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Threat actors are using the ARTEX framework against Salesforce orgs; here is how to defend (opens in a new tab)

You will learn how an AI-driven attack against Salesforce environments behaves, what Salesforce Threat Intelligence has observed, and which controls to put in place now.

  1. Use stolen application credentials
  2. Relay traffic through Apex and Named Credentials
  3. Inspect existing Apex and integration settings
  4. Deploy custom Apex and REST endpoints
  5. Enumerate users, profiles and Permission Sets
  6. Retry code-execution and integration paths
How the ARTEX-assisted campaign moved through a Salesforce org, from access to persistence

Salesforce Threat Intelligence reports that several threat actors are using ARTEX, an open-source, multi-agent offensive framework originally built for autonomous penetration testing. A malicious operator supplies a target and an objective, and AI agents coordinate the intrusion, combining known attack techniques with continuous planning, parallel execution and on-the-fly code generation. The framework’s GitHub repository was taken down, but community forks still circulate, and the authors treat ARTEX as an accessible capability rather than a tool tied to one actor. Other vendors report its use by a state-aligned actor against Microsoft 365 tenants and by financially motivated groups against financial organizations.

Salesforce observed a campaign that used stolen application credentials and trusted integration sessions against customer environments. The company states that the activity did not stem from a flaw in the Salesforce platform and that affected customers were notified directly. The observed behavior included using Salesforce as a relay through Apex and abused Named Credentials, inspecting existing Apex and integration settings before deploying custom Apex, REST endpoints and Visualforce components, and testing the compromised account’s effective permissions by enumerating users, profiles and Permission Sets. The attackers kept retrying code-execution and integration paths, including anonymous Apex, and audit logs showed rapid, dynamic automation that Salesforce reads as an agentic-like operator.

The recommended defenses are phishing-resistant MFA for all users, with Salesforce already enforcing it for admins and MFA for all users, User Email Domain Restrictions, short-lived context-bound OAuth tokens, and step-up authentication for sensitive actions such as bulk export and permission changes. Also recommended are IP allowlisting for users and Connected Apps, behavioral detection of full attack sequences, Event Monitoring streamed to a SIEM, regular scanning of repositories for exposed secrets, and a response plan able to disable an integration, revoke tokens and reset credentials within hours.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

Salesforce confirms MFA enforcement timelines and extension options for administrators (opens in a new tab)

Readers will learn the confirmed deadlines for mandatory multi-factor authentication and phishing-resistant requirements, along with how Salesforce plans to handle extension requests for non-compliant accounts.

Salesforce has clarified its ongoing multi-factor authentication rollout after conflicting messages caused confusion among customers. The company reaffirmed that mandatory multi-factor authentication remains required for all users by June 2026, with production enforcement beginning on July 20. Administrators and users with elevated permissions must use phishing-resistant methods.

Recent reports suggested enforcement might be delayed indefinitely or pushed past late October, but Salesforce explicitly stated there are no open-ended postponements. The platform is currently collaborating directly with a small group of customers who previously received extensions and require additional time to complete their security configurations.

A tool expected by mid-October will allow organizations to request ninety-day extensions for non-compliant users. Salesforce notes that over ninety percent of customers have already adopted the required controls and will contact any remaining accounts directly to ensure compliance within the next six to eight months.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?