LlamaIndex用Trace测试LlamaParse安全
LlamaIndex称,Trace的智能体DAST在四天内测试了LlamaParse的解析、提取、索引、检索、部署的智能体及MCP服务器,覆盖十项OWASP LLM风险和常规Web应用风险。测试使用可用凭据,但未授予源代码或云配置访问权限;发现问题涉及业务逻辑、客户组织边界及文档影响模型的行为,公司称已修复或缓解全部平台问题。该测试为厂商自述且属于一次性测试,并未随每项新功能持续执行。
该案例展示了智能体DAST如何覆盖文档处理与连接工作流中的AI特有攻击面,但厂商自述和一次性测试的局限使其不能替代独立验证。
LlamaParse turns PDFs, scans, and other messy files into structured data that AI applications can use. Many of those files are sensitive, including financial filings, insurance claims, and contracts. Before a company sends us any of them, security teams usually review our enterprise readiness documentation: SOC 2 reports, data policies, DPAs, and third-party pen tests.
Traditional pen tests are good at web apps and APIs. They aren’t built for the parts of LlamaParse where a model reads customer documents, and we wanted those tested just as thoroughly. This post covers how we did that and what we learned.
Where a document goes
In most web apps, untrusted input comes in through a form field. In LlamaParse, it comes in as a whole file, often written by someone outside the customer’s company, and it touches almost everything. We parse it, classify it, pull out fields, and index it for search. Then it gets read again by agents that customers deploy on LlamaParse and by AI assistants connected through our MCP server. A document could try to steer any of those steps.