Day 1 of 860 minCipher Cadet

Day 1: AI Security Testing with Burp Suite: Orientation and Your First Burp Capture

Taught by Mr Elite Updated

By the end of today you can

  • Explain the eight-day course direction and the practical skills each day will build.
  • Understand why AI applications are also web applications with HTTP APIs, sessions and backend services.
  • Install Burp Suite Community Edition using the official PortSwigger distribution.
  • Configure a dedicated browser profile to send traffic through Burp's local proxy.
  • Understand the purpose of Burp's CA certificate and how HTTPS interception works in an authorised test setup.

Warm-up

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

Is an AI-powered chatbot separate from normal web security because it uses a language model?

No. It still relies on web technologies such as HTTP, APIs, sessions, authentication and server-side application logic. AI adds components and risks, but the web application layer remains important.

What should you see after configuring a browser to use Burp's proxy and visiting a page?

The browser request should appear in Burp's Proxy HTTP history, provided interception and proxy settings are configured correctly.

Welcome to AI Security Testing with Burp Suite. Over the next eight days, we will use Burp as a practical inspection point for understanding how AI-powered web applications communicate. We will start with the basics—capturing requests and reading HTTP—then build toward inspecting API behaviour, authentication, prompt submission, retrieval interactions, tool calls and security controls.

Why use Burp for AI security? Because an AI application is still a web application. The browser sends HTTP requests. The server authenticates users, validates inputs, calls APIs and returns responses. Somewhere behind that interface, the application may call a model endpoint, retrieve documents, store conversation history or invoke tools. Burp helps you observe the web-facing part of that flow so you can understand what the application sends and receives.

Today is about setup, not exploitation. Your goal is simple: run Burp Community Edition, configure a dedicated browser profile to use its proxy, visit a harmless page or an authorised test application, and see one request appear in HTTP history. Once you can do that reliably, you have the foundation for the rest of the course.

The eight-day learning path — what we will build

This course is a practical introduction. Each day builds on the previous one, so do not skip the setup fundamentals. If you cannot capture and read a basic request, later API testing will feel confusing.

The planned eight-day progression is:

  • Day 1Orientation and Your First Burp Capture: install Burp, configure the browser proxy, install the CA certificate in a dedicated profile and capture a request.
  • Day 2Reading HTTP Requests and Responses: understand methods, paths, headers, cookies, status codes and response bodies.
  • Day 3Mapping an AI Application's API Surface: identify the browser-facing endpoints used by chat, file upload, history and settings features.
  • Day 4Authentication and Session Handling: inspect login flows, session cookies, token handling and access-control boundaries in an authorised lab.
  • Day 5Testing AI Input and Output Paths: understand how prompts and responses are represented in requests and responses, using harmless test content.
  • Day 6Inspecting RAG and File-Upload Flows: follow document upload, processing and retrieval-related web requests in a controlled application.
  • Day 7Reviewing Tool and Agent API Calls: inspect how an application represents tool requests, approvals and action results.
  • Day 8Build a Mini Assessment: combine scope, traffic observations, prioritised checks and a concise report.

The course is about understanding and testing the application layer. Burp does not automatically reveal every internal model call. Some AI traffic is generated server-to-server and never passes through your browser. You will learn to distinguish what is visible at the client boundary from what requires application logs, architecture information or owner-provided test instrumentation.

For every practical exercise, record:

  • Target and environment
  • Permission or lab scope
  • Request and response details relevant to the task
  • What you expected to happen
  • What actually happened
  • A short explanation of what the evidence does and does not prove
HTTP history
Burp's record of requests and responses that pass through its proxy.
Scope
The specific hosts, applications and actions you are authorised to test.
Client-side traffic
Requests sent by the browser or other client to a server.
Server-to-server traffic
Requests made by backend services to other services, which may not be visible in the browser proxy.

Quick check

What is the main reason the course begins with a basic Burp capture?

Why AI applications are web applications with APIs

An AI chat interface may look like a simple text box, but a typical request travels through several layers. The browser sends a request to the application backend. The backend checks the session, validates the input, applies rate limits and may call a model provider or internal inference service. The response then returns to the browser, often as JSON or a streamed response.

A simplified flow looks like this:

text
Browser
   |
   | HTTPS request: message, session and options
   v
Web application / API
   |
   +---- Authentication and authorisation
   |
   +---- Input validation and rate limiting
   |
   +---- Conversation storage / retrieval
   |
   +---- Model service or internal AI gateway
   |
   v
HTTP response or streamed output
   |
   v
Browser interface

Burp sits between your browser and the web application when the browser is configured to use Burp's proxy. It can show the request method, URL, headers, cookies, body, response status, response headers and response body. That makes it useful for learning how the application is structured.

Common web features in AI applications include:

  • Chat submission and response streaming
  • Conversation history and message retrieval
  • File upload and document processing
  • User profile and account settings
  • Authentication, logout and session refresh
  • Feedback, rating and report endpoints
  • Tool approval and action confirmation
  • Search, retrieval and knowledge-base configuration

Do not assume every feature has a separate endpoint, or that every endpoint is visible from the browser. Modern applications may use fetch, XMLHttpRequest, WebSockets or server-sent events. Some actions are handled entirely by the backend. Your job is to observe what is present, not guess endpoints or treat an unseen request as confirmed.

When you inspect a request, start with the basics:

  • MethodGET, POST, PUT, PATCH or DELETE.
  • Paththe resource or API route being requested.
  • Headerscontent type, origin, user agent, cookies and authorisation metadata.
  • BodyJSON, form data, multipart upload or another payload format.
  • Responsestatus code, headers and returned content.
API
An interface that lets software components exchange requests and responses.
HTTP method
The action type used by a request, such as GET or POST.
Header
Metadata sent with an HTTP request or response.
Session cookie
A browser-held value used by an application to associate requests with a logged-in session.
JSON
A common structured data format used in web APIs.

Quick check

Which statement about Burp's browser proxy view is correct?

Install Burp Community Edition and prepare a dedicated browser profile

Burp Suite Community Edition is sufficient for learning proxy basics and manually inspecting HTTP traffic. Download it from PortSwigger's official website. Avoid third-party installers and repackaged downloads.

Burp's interface changes over time, so button names and navigation can vary slightly between releases. The important items to find are the proxy listener address and port, the browser launch option (if available) and the HTTP history view.

Use a separate browser profile for testing. This prevents the Burp CA certificate and proxy settings from changing how your everyday browser handles websites. Burp may offer a built-in browser that is already configured to use its proxy. If you use that option, it is usually the simplest route for a first capture.

If you configure an external browser, set its HTTP and HTTPS proxy to the Burp listener address shown in Burp. A common default is 127.0.0.1 on port 8080, but verify the actual listener configuration in your own installation rather than assuming the default.

text
Example local proxy settings
Proxy host: 127.0.0.1
Proxy port: 8080

Use the values shown in your Burp installation.
Do not configure a public or shared browser profile for this exercise.
Burp Suite Community Edition
The free edition of Burp Suite used for learning and manual web traffic inspection.
Proxy listener
The local address and port on which Burp accepts proxied browser connections.
Dedicated browser profile
A separate browser environment used only for authorised testing.
Loopback address
127.0.0.1, which refers to the local computer.

Configure HTTPS interception and capture your first request

For plain HTTP, a proxy can read the request and response directly. HTTPS adds TLS encryption between the browser and the destination server. To inspect HTTPS in an authorised test setup, Burp acts as a TLS-intercepting proxy: the browser establishes a TLS connection to Burp, and Burp establishes a separate TLS connection to the destination. The browser must trust Burp's local CA certificate for this controlled interception to work without a certificate warning.

Use this only in your dedicated test browser profile. Burp's CA certificate is powerful: a browser that trusts it may accept certificates generated by Burp for sites you visit through the proxy. Do not install it system-wide or on a device you do not control. Remove the certificate from the test profile when you no longer need it.

A typical setup sequence is:

  • Start Burp and confirm its proxy listener is running.
  • Open the browser that will be used for testing.
  • Visit Burp's local certificate page using the browser routed through the proxy, following the instructions shown by your Burp version.
  • Download the CA certificate from Burp.
  • Import it into the dedicated browser profile's certificate authority store, following the browser's current documentation.
  • Restart the browser if required.
  • Visit a harmless HTTPS page or an authorised training application.
  • Open Burp Proxy HTTP history and confirm that the request and response appear.

The exact certificate import screens differ across browsers and operating systems. Read the current browser documentation and PortSwigger guidance for your version. Do not disable certificate validation globally as a workaround. If a certificate warning remains, check that you imported the correct Burp CA certificate into the correct test profile and that the browser is using the intended proxy.

To make your first capture:

If a page loads but nothing appears in HTTP history, check whether the browser is actually using Burp, whether the listener is active, whether the request was generated by that browser, and whether the history view has filters enabled. If HTTP appears but HTTPS fails, check the CA certificate and browser trust settings.

Quick check

Why does Burp need its CA certificate trusted by the test browser to inspect HTTPS?

If it did not work

- Downloading Burp from unofficial mirrors or third-party installer sites.

- Assuming the proxy listener always uses the default host and port without checking Burp's settings.

- Configuring the proxy in the wrong browser profile.

- Forgetting that only traffic routed through the proxy appears in HTTP history.

- Expecting browser-to-server proxy history to show every backend-to-backend AI service call.

- Installing Burp's CA certificate system-wide when a dedicated test profile is sufficient.

Recap

  • AI applications are web applications that use HTTP, APIs, authentication and backend services alongside AI components.
  • Burp helps inspect traffic that is routed through its proxy; it does not automatically expose every internal server-to-server call.
  • Community Edition is enough for the first manual capture and basic HTTP inspection.
  • A dedicated browser profile keeps proxy and certificate changes isolated.
  • HTTPS interception requires the test browser to trust Burp's CA certificate for that controlled setup.
  • Install the CA only in a browser profile and device you control and are authorised to use.
  • Your first milestone is one harmless request visible in Burp HTTP history.

Cheat sheet

Burp Community Edition
Free edition for manual web traffic inspection and learning
Proxy listener
Burp's local host and port accepting browser traffic
Common local listener
127.0.0.1:8080, but verify your actual configuration
HTTP history
Proxy view listing captured requests and responses
HTTPS interception
Burp terminates and re-establishes TLS connections in the configured test flow
Burp CA certificate
Certificate authority trusted by the dedicated test browser for HTTPS interception
Dedicated profile
Isolated browser profile used for authorised testing
First capture
Visit a harmless authorised page and locate its request in HTTP history
Evidence hygiene
Redact cookies, bearer tokens, API keys and personal data

Before the next day

Mission: Capture Your First Authorised HTTP Request

Install Burp Suite Community Edition, configure a dedicated browser profile to use Burp's proxy, and capture one harmless HTTP or HTTPS request in the HTTP history. The objective is to prove that your proxy path works—not to test the target for vulnerabilities.

About 30 min

You are done when: One redacted screenshot or written capture record showing a request in Burp HTTP history, plus the Burp listener address and browser profile used. Do not include raw session credentials or secrets.

Want more? Capture one harmless request to a local test page and one to an authorised HTTPS training application. Compare the request method, headers and response status. Explain why the HTTPS request required the test browser to trust Burp's CA certificate.

Quiz

4 questions. Your score is saved with your progress.

1. Why is Burp useful when assessing an AI-powered web application?

2. What is the safest place to install Burp's CA certificate for this beginner exercise?

3. What should you check if the browser loads a page but no request appears in Burp HTTP history?

4. Does seeing one request in HTTP history prove that the AI application has a security vulnerability?

Finish the day

Mark the day complete to save your progress.

Go to Day 2

Next: Next, we will learn to read the traffic you have captured. You will identify HTTP methods, paths, headers, cookies, status codes and response bodies. We will practise recognising JSON requests and understanding how a browser submits information to an application API. Keep today's setup available, but remember how to disable the proxy and remove the test CA certificate when the course is complete. A reliable, isolated test environment is part of good security practice.

Tell someone you are doing this:WhatsAppXLinkedIn

Your notes

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