Insurance Top 100 / #4ARD = Agentic Resource Discovery · A2A = Agent2Agent · MCP = Model Context Protocol
Insurance agents · commercial · Salesforce Financial Services
Agentforce Insurance
Agentic workflows across insurance servicing and operations. Publisher: Salesforce. Also ranked in Finance & Banking (#6), Cybersecurity (#50), Supply Chain, Manufacturing & Logistics (#53).
Trust profileas of 2026-10-26
Publisherconfirmed · Vendor-domain page, marketplace listing or metadata at publisher domain — product page served from the vendor's own domainconfirmed
Compliance1 record about this agent · 1 registry-matched · +6 vendor-level (inherited)T1
Security3 CVEs linked in the registry · newest 2025-11-04linked
ProtocolsModel Context Protocol (MCP) probed, not foundAgent2Agent (A2A) probed, not foundAgentic Resource Discovery (ARD) probed, not found0 / 3
Traces1 public trace · best: vendor report · data left the environment in at least oneT3
Issues found0 regulator actions · 0 incidents · 0 withdrawn certificates · CVEs: see Securitylinks only
Evidence available — not a safety certification. Suitability depends on your task, deployment and permissions. Rows marked vendor-level describe Salesforce, not this agent specifically.
Traces — under attack, in defence, in incidents
1 public · what a trace is⚠
attacked by a researcher
T3 vendor report · platform-level · unreviewed
Instructions placed in a Web-to-Lead form field are later processed by an Agentforce agent, which queries lead records and sends them to an expired, re-registered Salesforce-allowlisted domain
Observed: Lead data exfiltrated; Salesforce enforced Trusted URL allowlists for Agentforce and Einstein AI and re-secured the expired domain · egress: yes · human approval: no · refused: no
Vendor response: Salesforce patch (Trusted URLs enforcement), September 2025
Noma Security; reported by The Hacker News
2025-09-25
2025-09-25
● third-party or vendor report · ◎ this registry's own probe transcript · ⚠ data left the environment. A trace describes one version on one date; it is evidence of behaviour, never a certification. Rows marked unreviewed have not yet been checked against their source by the maintainer.
CVEs — on the official record
3 linked · the registryCVE-2025-64320
2025-11-04
Improper Neutralization of Input Used for LLM Prompting vulnerability in Salesforce Agentforce Vibes Extension allows Code Injection.This issue affects Agentforce Vibes Extension:…Prompt injection · Code execution · fix known · unreviewed
Medium 6.5CVE-2025-64321
2025-11-04
Improper Neutralization of Input Used for LLM Prompting vulnerability in Salesforce Agentforce Vibes Extension allows Manipulating Writeable Configuration Files.This issue affects…Prompt injection · Code execution · fix known · unreviewed
Medium 5.3CVE-2025-64322
2025-11-04
Incorrect Permission Assignment for Critical Resource vulnerability in Salesforce Agentforce Vibes Extension allows Manipulating Writeable Configuration Files.This issue affects A…— · fix known · unreviewed
Medium 5.3All 3 in the registry → Severity is the official record's; nothing here enters the score. Links are by listed product, so a CVE that names a different component of the same platform may be missing.
Compliance evidence
Jurisdiction: US + EU · 11 frameworks shown✔
FedRAMP · FedRAMP Moderate
T1 Registry-matched
FedRAMP Authorized
Scope: product · covers this resource: partial · FedRAMP Marketplace · 2026-10-26 · match 91%
re-check 2026-11-02
–
SOC 2
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
ISO 27001
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
PCI DSS
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
HIPAA
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
"Unknown" means nothing was found in the sources checked — registries, marketplaces and the vendor's own pages. It is not a finding of non-compliance; ask the vendor.
About the vendor — inherited, not agent-specific
6 records matched at organisation level✔
CSA STAR · STAR for AI
T1 Registry-matched · vendor-level
found in CSA STAR Registry on 2026-10-26
Scope: entity · CSA STAR Registry · 2026-10-26
re-check 2026-11-02
✔
CSA STAR · STAR Level 1
T1 Registry-matched · vendor-level
found in CSA STAR Registry on 2026-10-26
Scope: entity · CSA STAR Registry · 2026-10-26
re-check 2026-11-02
✔
ISO 42001 · ISO 42001
T1 Registry-matched · vendor-level
Found in CSA STAR Registry on 2026-10-26
Scope: entity · CSA STAR Registry · 2026-10-26
re-check 2026-11-02
○
EU AI Act · Art. 50 statement
T4 Vendor-claimed · vendor-level
Art. 50 statement
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
GDPR · DPA available
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
GDPR · DPF active
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
A vendor-level registry entry proves the organisation was assessed; whether this agent is inside that scope is a question for the vendor. These rows do not count toward the agent's evidence tier.
✔ found · ○ claimed · – not found · ⚠ expired, stale or revoked. Every row links to its source.Dispute or correct this dossier
GDPR, assembled from checks
GDPR● 0 found in registries or documents○ 2 vendor-claimed⚠ 0 issues linkedas of 2026-10-26
○ ClaimedDPA available: Vendor-claimed (vendor page, 2026-10-26). A DPA is a contract you still have to sign and review.
○ ClaimedDPF active: Vendor-claimed (vendor page, 2026-10-26). Proves a transfer mechanism for EU-to-US transfers only.
– Not foundNo Article 42 GDPR seal. "GDPR certified" is never shown without one.
☐ You checkYour lawful basis, DPIA, and whether this agent is inside the certificate scope.
News and chatter
last 90 days · linked with confidence ≥ 0.85Nothing linked from Hacker News, GDELT, GitHub releases or the vendor's feed in the last 90 days.
Headline, link and a summary attributed to the outlet. News never changes trust or domain scores.
Insurance score
72regulated profile · sar-score-2.0 · #4 of 100 in the curated list
Adoption / usage25 / 30
Trust & security19 / 25
Project / product health20 / 20
Ecosystem / interoperability14 / 15
Domain expertise / fit72 / 100
Governance / compliance evidence17 / 100
Docs / transparency9 / 10
Raw component / maximum, then weighted by the regulated profile (adoption 15, trust 25, project 10, ecosystem 10, domain 20, governance 15, docs 5). Trust and governance are computed from the evidence on this page (vendor-level rows at half credit); the other components come from the curated workbook, whose order is the rank. Unknown components count as 0 and are never imputed.
Before you deploy
Deployment questions answered from the vendor's documentation, each with its source.
✔Masks or minimises personal data before it reaches the model? Yes — Einstein Trust Layer: "Sensitive data is detected and masked before sending the prompt to the LLM"; admins choose what is masked source
?Data residency or regional hosting documented? Not documented — Not covered on the pages checked source
✔Customer data excluded from model training (documented)? Yes — "Your data isn't retained by third-party LLMs" and is not used for their training source
◐Human review before a decision or record change is executed? Configurable — Per action: "enable the Require user confirmation setting" so the agent asks before a record change source
✔Audit log of agent actions documented? Yes — "Prompts, responses, and trust signals are logged and stored in Data 360" source
Evidence supporting this use (11)
CSA STAR STAR for AI — registry-matched, vendor-level source
CSA STAR STAR Level 1 — registry-matched, vendor-level source
FedRAMP Moderate — registry-matched source
ISO 42001 — registry-matched, vendor-level source
EU AI Act Art. 50 statement — vendor-claimed, vendor-level source
GDPR DPA available — vendor-claimed, vendor-level source
GDPR DPF active — vendor-claimed, vendor-level source
Masks or minimises personal data before it reaches the model: yes — Einstein Trust Layer: "Sensitive data is detected and masked before sending the prompt to the LLM"; admins choose what is masked source
Customer data excluded from model training (documented): yes — "Your data isn't retained by third-party LLMs" and is not used for their training source
Human review before a decision or record change is executed: configurable — Per action: "enable the Require user confirmation setting" so the agent asks before a record change source
Audit log of agent actions documented: yes — "Prompts, responses, and trust signals are logged and stored in Data 360" source
Unknowns to check (7)
Data residency or regional hosting documented: not documented — Not covered on the pages checked. Ask the vendor. source
Your lawful basis and DPIA for PHI and personal data the agent will touch
Current FedRAMP status with the agency, if government use is intended
Whether the CSA STAR entry covers this product; Level 1 is a self-assessment, Level 2 a third-party attestation
The transfer mechanism you will rely on; DPF covers EU-to-US transfers only
Ask the vendor for SOC 2, ISO 27001, PCI DSS, HIPAA evidence; none was found in the sources checked
Whether the agent exposes MCP or A2A endpoints; none were observed
Suggested restrictions for a pilot (4)
Confirm the processing region in writing before personal data of EU or UK residents is in scope.
Ask for the SOC 2 report under NDA before the pilot touches customer data; none was found in the sources checked.
No PHI in the pilot until a HIPAA BAA is in hand; no HIPAA evidence was found in the sources checked.
A public trace shows data leaving the environment under adversarial input. Confirm the vendor's fix is in the version you deploy, and keep an egress allowlist around the agent during the pilot.
See the worked comparison: Claims and document-intake agents that touch personal data →
Rules: config/deploy_rules.json. Advice for a bounded pilot, not a verdict.
Provenance
seed workbookscores, rank, category
CSA STAR Registrycompliance evidence
FedRAMP Marketplacecompliance evidence
vendor pageclaims
NVDsecurity (CVE keyword search)
Hacker News, GDELT, vendor feedsnews and chatter
First seen2026-10-26
Record
res_f1912c71acc80c75