Skip to content
Tutorials Center
My learning

Topics

Lesson 34 of 38 ยท Testing and Tooling

A Tour of Common Security Tools

Meet the tools used in web security testing: intercepting proxies, scanners, static analyzers and image scanners, with read-only examples and safe lab practice.

Security work uses a small, well-known toolbox. You do not need to master all of it, but knowing what each tool is for helps you read reports, set up automation and talk to testers. This lesson is a guided tour. Commands are shown read-only with illustrative output; this site cannot run the tools, and you should run them only against systems you own or are authorized to test (see Authorized Testing and Scoping).

Scanners send many requests and can break fragile systems or trigger alarms. Point them at your own lab or a staging copy, with permission, never at third-party sites.

Intercepting proxies: OWASP ZAP and Burp Suite

An intercepting proxy sits between your browser and the application. You see, pause, edit and replay every request. That makes hidden parameters, cookies and API calls visible, which is the foundation of manual web testing.

  • OWASP ZAP is free and open source. It has a spider (crawler), an active and passive scanner, scripting, and a headless mode for CI.
  • Burp Suite (PortSwigger) has a free Community edition and a paid Professional edition. It is popular for manual testing, with Repeater (replay and edit requests) and Intruder (automated variations).

Typical lab workflow: configure the browser to use the proxy, browse your test app normally so the proxy records the site map, review the passive findings (missing headers, cookie flags), then run an active scan against the in-scope target.

A CI-friendly baseline scan using the ZAP container, pointed at a staging URL you own:

Terminal
# Read-only example. Replace the URL with YOUR staging site.
docker run --rm -t ghcr.io/zaproxy/zaproxy:stable \
  zap-baseline.py -t https://staging.example.test -r report.html

Illustrative result lines (not from a real scan):

TEXT
WARN-NEW: Content Security Policy (CSP) Header Not Set [10038] x 4
WARN-NEW: Missing Anti-clickjacking Header [10020] x 4
PASS: Cookie No HttpOnly Flag [10010]
FAIL-NEW: 0	WARN-NEW: 2	INFO: 0	IGNORE: 0	PASS: 54

Network discovery: Nmap

Nmap finds hosts and open ports and identifies services. For a defender it answers "what is exposed?" in your own network. Always scan only what you own or have permission to scan.

Terminal
# Read-only example against a host in your own lab (documentation address)
nmap -sV -p 22,80,443 192.0.2.10
TEXT
PORT    STATE SERVICE VERSION
22/tcp  open  ssh     OpenSSH 8.9
80/tcp  open  http    nginx 1.24
443/tcp open  ssl/http nginx 1.24

Unexpected open ports (a database listening on all interfaces, an old admin service) are classic misconfiguration findings. Version information feeds component vulnerability checks.

Static analysis and secrets: Semgrep, linters, gitleaks

  • Semgrep matches code patterns using rules that read like the code itself. It is fast, supports many languages and has public rule sets for the OWASP categories.
  • Language-specific analyzers (for PHP, Java, Python, JavaScript and others) catch typical flaws and type mistakes.
  • Secret scanners such as gitleaks and trufflehog search code and history for committed keys and tokens.
Terminal
# Read-only examples
semgrep --config auto .
gitleaks detect --source . --redact

A leaked secret in history is still leaked after you delete the line; rotate it.

Dependencies and containers: Trivy, Grype, OSV, audit commands

Composition analysis tools scan lock files, container images and infrastructure files. They produce the kind of report you built in Dependency Scanning and SBOMs.

Terminal
# Read-only examples
trivy image myapp:latest
composer audit
npm audit --omit=dev
TEXT
Total: 3 (HIGH: 1, MEDIUM: 2)
LIBRARY   VULNERABILITY   SEVERITY  INSTALLED  FIXED
fastparse DEMO-2024-0001  HIGH      2.3.0      2.4.1

(The package and ID above are fictional.)

Everything else you will meet

Tool type Examples Use
Vulnerability scanner Nessus, OpenVAS Host and service weaknesses
Fuzzer ffuf, wfuzz, AFL++ Try many inputs against your own endpoints or parsers
TLS checker testssl.sh, SSL Labs Certificate and protocol configuration
Header checker securityheaders.com style tools Missing browser defenses
Packet analyzer Wireshark, tcpdump Look at network traffic you own
Cloud posture Prowler, ScoutSuite Misconfigured cloud accounts

Pick the tool by question

What is exposed? Nmap, cloud posture tools.
What does the app do? ZAP or Burp proxy.
Is the code risky? Semgrep, linters.
Are parts outdated? Trivy, audit commands.

Tools answer questions; people interpret.

1 / 2

Reading tool output with skill

Tools produce raw findings; your job is to triage. The stand-in below ingests a fictional scanner report, drops duplicates and groups findings by OWASP category and severity.

Python Triage a scanner report (fictional data)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Note that "idor-suspected" says suspected: automated tools guess; a human must confirm access control issues.

Good habits

  • Keep tools updated; rules and signatures change.
  • Authenticate scanners with test accounts so they can reach logged-in pages.
  • Tune the rate to protect the target.
  • Store raw output for evidence but share a cleaned report.
  • Re-test after fixes and keep the checks in CI to prevent regressions.
  • Learn the concepts (HTTP, TLS, sessions, SQL) so you can judge tool results instead of trusting them blindly.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does an intercepting proxy such as ZAP or Burp let you do?

    A proxy makes the traffic visible and editable, which is the basis of manual web testing.
  2. 2. You committed an API key by mistake and removed it in the next commit. What must you still do?

    Version history keeps the old content, so the secret must be revoked and replaced.
  3. 3. Where is it appropriate to run an active scanner?

    Active scanning can disrupt services and is only acceptable with authorization.
  4. 4. Why does a report line like 'idor-suspected' need human follow-up?

    Tools can flag patterns, but whether someone should see an object is a business decision.

Summary

  • Proxies (ZAP, Burp) expose app traffic; Nmap maps exposure; Semgrep and secret scanners review code; Trivy and audit commands check components.
  • Run tools only where authorized, tuned to avoid damage.
  • Triage results by category and severity, deduplicate, and confirm logic issues manually.
  • Rotate leaked secrets and keep checks in CI.

Next: Project: Dependency Audit Tool