Burp AT in Burp Suite Professional
Burp AT sends the information the AI needs to reason about your task:
- Your prompts and any goals you set with
/goal. - Any resources you send to Burp AT, such as a message from the HTTP history, a node from your site map, or an issue found by the scanner.
- Files you attach.
- The agent's own messages.
- Each tool call the agent makes, and the arguments it passes to that tool.
- The result each tool returns. For tools that send HTTP requests, this includes the full request and response.
- Task metadata, such as token counts and the time each request was started.
Burp AT does not upload your Burp project. Its tools run locally in Burp, and Burp returns only the results of the tool calls the agent makes.
PortSwigger stores the conversation as your task runs, and includes it in requests to the AI provider. This enables the agent to keep track of its work. Attachment contents are stored separately and are only sent when Burp AT needs to access the file. For more information on data storage, see What data does PortSwigger store?
Burp AT in Burp Suite enterprise platform
Burp AT sends your objectives, chat messages, and the site's background context to PortSwigger's AI service. The agent also receives the results of the testing tools it calls. These results can include HTTP request and response data from your target.
For example, the request-sending tool returns response headers and body content. It can shorten large responses, and the agent can request more content when needed.
AI-enhanced scanning and AI-recorded login sequences in Burp Suite DAST
- AI-enhanced scanning: the full HTTP request and response pair in which the issue was found, including headers; the issue name, target URL, and insertion point; and the origin scan ID and site ID.
- Recorded logins: the page text, HTML attributes of interactive elements, and a screen capture of the page.