Day 2 of 860 minCipher CadetHands-on lab

Day 2: AI Security Testing with Burp Suite: Proxy, Intercept and Repeater Basics

Taught by Mr Elite Updated

By the end of today you can

  • Explain how an HTTP proxy sits between a browser and a web application.
  • Distinguish Proxy Intercept from HTTP history and understand when each is useful.
  • Turn Intercept on and off and safely forward or drop a request in a controlled test.
  • Send a captured request to Repeater.
  • Resend a request from Repeater and compare the response with the original.

Warm-up

Answer from memory first, then tap to check. Recalling yesterday is what makes it stick.

What does Burp's proxy do when your browser is configured to use it?

It receives browser requests, can inspect or modify them within the authorised test, forwards them to the destination and passes responses back to the browser.

What is the difference between Intercept and HTTP history?

Intercept lets you pause and handle traffic while it is passing through Burp. HTTP history records requests and responses that have passed through the proxy.

Yesterday, you installed Burp Suite, configured a dedicated browser profile and captured your first request. Today we will use that same setup to understand three core parts of Burp: Proxy, Intercept and Repeater.

Think of a proxy as a controlled checkpoint between your browser and a website. Your browser sends a request to Burp, Burp can record it, and then the request is forwarded to the destination. The response comes back through Burp before reaching the browser. This position lets you inspect what is being sent and what comes back.

There are two views that beginners often confuse. Intercept is for handling a request or response as it passes through the proxy. HTTP history is the record of traffic that has already passed through. Repeater takes a selected request and lets you send it again manually, so you can study the response without repeatedly clicking around in the browser.

How a proxy works — the request and response journey

A web proxy is an intermediary. Instead of connecting directly to the destination, your browser connects to Burp's local proxy listener. Burp then makes the onward connection to the website or application. The response travels back through Burp to the browser.

text
Browser
   |
   | 1. HTTP request
   v
Burp Proxy
   |
   | 2. Forwarded request
   v
Web application
   |
   | 3. HTTP response
   v
Burp Proxy
   |
   | 4. Response returned
   v
Browser

This is useful because Burp can observe the request and response at the application layer. You can inspect the method, URL, headers, cookies, body, status code and returned content. With HTTPS, the dedicated test browser must trust Burp's CA certificate for the controlled interception setup described on Day 1.

A proxy does not automatically make a request safe or authorised. It simply gives you a point where you can observe traffic. The permission to test comes from the owner of the application, not from the fact that Burp can reach it.

In an AI application, the browser might send a chat message to a conversation API. The request may include a message body, conversation identifier and session cookie. The backend may then call an internal model service. That internal model call may not be visible in Burp if it happens server-to-server. Burp shows the traffic that actually passes through the configured browser proxy.

Proxy
An intermediary that receives a client's request and forwards it to a destination.
Request
The message a client sends to a server, including method, path, headers and optional body.
Response
The server's reply, including status, headers and optional body.
Forward
Allow a paused request or response to continue through the proxy.
Drop
Stop a paused request from being sent onward.

Quick check

Which statement best describes Burp Proxy?

Intercept versus HTTP history — pause traffic or review the record

Proxy Intercept and HTTP history are related, but they solve different problems.

Intercept:

  • Handles a request or response while it is passing through Burp.
  • Can pause the flow so you can inspect it before it continues.
  • Lets you choose to forward or drop the paused item.
  • Is useful when you need to observe a request at the moment it is generated.
  • Can be switched off so traffic flows without manual pauses.

HTTP history:

  • Records requests and responses that pass through the proxy.
  • Lets you review traffic after it has moved on.
  • Helps you find a request again and inspect its details.
  • Is useful for mapping application endpoints and comparing traffic.
  • Does not require you to pause every request.

A common beginner experience is turning Intercept on and then wondering why the browser appears to hang. That is expected: Burp is holding the request until you decide what to do. Click Forward to let it continue. If you do not want it sent, use Drop. When you are finished observing live traffic, turn Intercept off.

Use Intercept sparingly. Leaving it on while a page loads can pause many requests for images, scripts, fonts and API calls. You may need to forward several items before the page completes. For normal browsing and collecting traffic, HTTP history is often more convenient.

Intercept on
Burp pauses matching traffic so you can inspect and decide what happens next.
Intercept off
Burp forwards traffic without waiting for a manual decision.
HTTP history
A reviewable record of proxied requests and responses.
Forward
Continue the paused request or response.
Drop
Stop the paused item from continuing to its destination or client.

Quick check

You want to inspect a request after it has already completed. Which view should you use?

Send a request to Repeater and read the response

Repeater is used to resend an individual request manually. It is useful when you want to repeat a request and study the response without reproducing the same browser clicks each time.

A simple workflow is:

  • Find a request in HTTP history.
  • Select it and send it to Repeater using the context menu or shortcut shown by your Burp version.
  • Open the Repeater tab.
  • Review the request before sending it.
  • Click Send.
  • Read the response and compare it with the original history entry.

In Repeater, the request editor lets you inspect the request line, headers and body. The response panel shows what the server returned. Pay attention to:

  • Status codefor example, 200, 302, 400 or 401.
  • Response headerscontent type, cache directives and other metadata.
  • Response bodyHTML, JSON or another representation.
  • Content length and timinguseful context, but not proof of a security issue.
  • Differenceswhether the response changes between the original request and the repeated request.

For this beginner lesson, resend a safe read-only request, such as a GET request to a harmless page. Avoid resending state-changing requests such as POST, PUT, PATCH or DELETE unless the lab explicitly says they are safe and provides a disposable test record. Even repeating a request can create duplicate actions, send notifications or modify data.

Example of a simple request:

http
GET /help HTTP/1.1
Host: training.example
Accept: text/html
User-Agent: ExampleBrowser/1.0

A corresponding response might look like:

http
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: no-store

<html>
  <body>
    <h1>Training Help</h1>
  </body>
</html>

The example host is illustrative. Use the actual local or authorised training target supplied for your course. Do not send requests to a domain merely because it appears in a sample.

When you compare responses, first check whether the request is truly identical. Cookies, timestamps, anti-CSRF tokens, session state and server-generated identifiers can change. A different response does not automatically mean a vulnerability. Record the exact request conditions and describe what changed.

Repeater
Burp tool for manually sending an individual request again and inspecting its response.
Read-only request
A request intended to retrieve information without changing server-side state.
Status code
Numeric response indicator describing the result of an HTTP request.
Response body
The content returned by the server, such as HTML or JSON.
CSRF token
A value used by some applications to help protect state-changing requests against cross-site request forgery.

Quick check

What should you do before sending a request from Repeater?

A repeatable beginner workflow for AI application traffic

Once you understand Proxy, Intercept and Repeater, use a consistent workflow. This is the foundation for later AI API testing.

Start with a normal browser action in an authorised application. For example, open a help page or submit a harmless message in a training chatbot that is specifically provided for testing. Observe the browser request in HTTP history. Identify the endpoint and the content type. If the application uses JSON, note the shape of the request body without copying sensitive values.

Next, send a safe request to Repeater. For a read-only endpoint, resend it without changing anything. Compare the response. Your first objective is not to bypass authentication or alter another user's data. It is to understand how the application behaves when the same request is sent again.

For an AI chat endpoint, you might see a request with a JSON body containing a message and conversation identifier. Treat these fields as examples only; actual applications use different schemas. Do not guess hidden endpoints or try to access conversations that do not belong to your test account.

A useful observation table is:

text
Field | What to record
Target | Local or authorised application
Method | GET, POST, etc.
Path | Endpoint path, with sensitive values redacted
Content type | For example application/json
Status | Response status code
Body shape | Field names and data types, not secrets
Repeater result | Same, changed, rejected or not tested
Notes | What the observation proves and what it does not prove

When testing a chat submission, use a harmless message such as “Reply with the word hello.” If the lab provides a specific prompt-injection exercise, follow its scope and instructions. Do not send prompts designed to obtain hidden credentials, private user data or system secrets. Today's learning goal is proxy operation and request replay, not a successful exploit.

Your turn

AI Prompt Injection

Use the authorised training application associated with this lab to observe a harmless chat request in Burp, pause it with Intercept, forward it and resend the captured request in Repeater. The lab name refers to the course's prompt-injection training track; today's task is limited to learning the proxy workflow and using a benign test message. Do not target public AI services or attempt to extract hidden prompts, credentials or private data.

Open the lab in a new tab

What to try

What to notice

  • Did Intercept pause the request before it reached the application?
  • Did Forward allow the browser action to complete?
  • Did the same request appear in HTTP history?
  • Could you identify the request method, path, headers and body format?
  • Did the Repeater response match the original response, or did session state cause a difference?

If it did not work

- Confusing Intercept with HTTP history.

- Leaving Intercept on and assuming the browser or application has frozen.

- Forgetting to forward a paused request.

- Dropping a request when the intention was to let it continue.

- Assuming HTTP history will stop recording when Intercept is off.

- Sending a request to Repeater without checking the host and method.

Recap

  • Burp Proxy acts as an intermediary for browser traffic routed through its listener.
  • Intercept pauses a request or response while it is passing through the proxy.
  • Forward continues a paused item; Drop stops it.
  • HTTP history records traffic that has passed through Burp and is useful for later review.
  • Repeater lets you resend an individual request and inspect the response.
  • Always inspect the target, method, path and body before replaying a request.
  • Prefer harmless read-only requests for beginner Repeater practice.

Cheat sheet

Proxy
Intermediary between the configured browser and destination
Intercept on
Pause matching traffic for inspection
Intercept off
Let traffic pass without manual pausing
Forward
Continue the paused request or response
Drop
Stop the paused item from continuing
HTTP history
Review requests and responses that have passed through Burp
Repeater
Manually resend one request and inspect its response
Safe beginner replay
A harmless read-only request to an authorised target
Before Send
Check host, method, path, parameters, body and possible side effects
Evidence
Record status and relevant response details; redact cookies and tokens

Before the next day

Mission: Pause, Forward and Replay a Safe Request

Using the authorised training application or a harmless read-only page, demonstrate the complete Burp workflow: pause a request with Intercept, forward it, locate it in HTTP history, send it to Repeater and compare the response. Do not replay state-changing requests unless the lab explicitly authorises it.

About 30 min

You are done when: A short workflow record or redacted screenshot set showing the paused request, the HTTP history entry and the Repeater response, plus a comparison note. Do not include raw session credentials.

Want more? Capture two harmless read-only requests from the same authorised application and compare their methods, paths, response codes and content types. Explain why one might be better suited to Repeater practice than the other.

Quiz

4 questions. Your score is saved with your progress.

1. What is the main function of Proxy Intercept?

2. What is the main difference between HTTP history and Intercept?

3. What is Burp Repeater used for?

4. Which request is the best choice for a beginner's first Repeater exercise?

Finish the day

Mark the day complete to save your progress.

Go to Day 3

Next: Next, we will focus on reading HTTP requests and responses in more detail. You will learn how to interpret request lines, headers, cookies, JSON bodies, status codes and response content. Those skills will help you recognise the structure of AI application APIs before you begin mapping endpoints and testing their security controls. Keep your Day 2 capture and Repeater comparison. It will serve as your baseline when we inspect more complex AI application requests later in the course.

Tell someone you are doing this:WhatsAppXLinkedIn

Your notes

Private to this device. Write what you want to remember from today.