Week 3 - Deep Dive into Footprinting and Burp Suite

As required by the course guidelines, any tools, techniques, and tutorials shared on this blog are strictly for educational purposes. I am not responsible for any misuse of the information or tools demonstrated here.

Week 3 of Ethical Hacking and Penetration Testing got significantly more technical. We moved past the high-level theory of Target Scoping and Information Gathering and started getting our hands dirty with actual footprinting tools in our Kali Linux VMs.

Here is a rundown of the practical techniques we covered.


Target Scoping Realities

Before launching into the tools, we discussed the logistics of scoping. It is not just about picking a target; it involves defining business objectives, establishing strict test boundaries, and setting up project management schedules. You need to know exactly what is allowed (e.g., black-box vs. white-box testing) and what is strictly off-limits before you start.


Intercepting Traffic with Burp Suite

One of the core practical skills this week was setting up Burp Suite. Burp Suite acts as a local proxy. By configuring Firefox to route traffic through 127.0.0.1 on port 8080, you can intercept, inspect, and modify HTTP requests before they even reach the server.

Because so much of the web is encrypted today, we also had to download the PortSwigger CA certificate from the proxy and import it into our browser's trusted authorities to properly intercept HTTPS traffic.

As a class demonstration, we looked at how this works when submitting a login request to our campus portal, binusmaya.binus.ac.id. When you intercept the POST request during a login attempt, you can see the raw parameters, including the username and password, captured in cleartext within the proxy. (Note: A huge reminder was given in class: DO NOT SCAN or launch attacks against university infrastructure!)


DNS Enumeration and Zone Transfers

We spent a lot of time in the terminal using tools like whois, host, and dig. These are standard tools for gathering IP addresses and domain information.

The ultimate goal during this phase is often to check if a target's Domain Name System (DNS) server is vulnerable to a Zone Transfer. If a server is misconfigured and allows a zone transfer, it basically hands over the organization's entire network diagram, revealing internal hostnames and IP addresses.


HTTP Under the Hood

A basic understanding of HTTP is critical for security testers. We reviewed different HTTP methods (like GET, POST, and OPTIONS). We also broke down HTTP status codes. Analyzing the specific codes returned—like 4xx for client errors and 5xx for internal server errors—can sometimes passively reveal information about the underlying server operating system.


Other Footprinting Details

To wrap up, we touched on a few other tracking and reporting methods:

Web Bugs: We looked at how 1-pixel by 1-pixel invisible image files are embedded in pages to track users, often working alongside cookies.

Reporting: All of this gathered information has to go somewhere, so we were introduced to Dradis, an open-source framework used to compile and report penetration testing findings.

Next week, we are moving into target discovery and utilizing search engines for deeper reconnaissance. For now, I have a lot of terminal commands to memorize.

Comments

Popular posts from this blog

Week 2 - Target Scoping and Information Gathering

Week 5 - Target Enumeration and Uncovering Real IPs

Week 1 - Intro to Ethical Hacking and Building the Lab