Security testing guides — vulnerability scanning, penetration testing basics, and secure SDLC practices.
API Testing
RESTler is a stateful REST API fuzzer from Microsoft Research. Unlike simple fuzzers that hit each endpoint independently, RESTler infers the relationships between API calls — it knows that you must create a user before you can update it, and that updating requires the ID returned by creation. This stateful awareness
API Testing
API fuzzing finds the bugs that escape manual testing and code review: server crashes from unexpected inputs, schema violations from edge cases, and authorization gaps revealed by unusual request sequences. But fuzzing without a clear strategy wastes time and generates noise. This guide covers the practices that make API fuzzing
Security Testing
DevSecOps integrates security testing into every stage of the CI/CD pipeline instead of running it as a separate gate at the end. The principle is "shift left"—move security checks earlier in the development process where they're cheaper to fix. A complete DevSecOps pipeline runs
Security Testing
Checkov is an open-source static analysis tool for Infrastructure as Code (IaC). It scans Terraform, Kubernetes, CloudFormation, Helm, Dockerfiles, and more for security misconfigurations and compliance violations. With 1000+ built-in checks and the ability to write custom checks in Python or YAML, Checkov catches misconfigurations before they'
Security Testing
Trivy is an open-source vulnerability scanner that covers container images (OS packages and application dependencies), Kubernetes manifests, Terraform, Dockerfiles, and secrets. It's fast, requires no setup beyond installation, and produces structured JSON or table output. Use Trivy in CI to block builds with critical vulnerabilities before they
Security Testing
Semgrep is a fast, language-agnostic static analysis tool that finds security vulnerabilities by pattern matching against source code. It ships with thousands of community rules for OWASP Top 10 vulnerabilities, secret detection, and language-specific security patterns. You can also write custom rules in YAML to catch patterns specific
Fuzz Testing
Rust's memory safety guarantees eliminate an entire class of bugs that make fuzzing critical in C/C++ — but Rust code can still have logic errors, integer overflows, panics, and unexpected behavior. cargo-fuzz brings libFuzzer to Rust with a clean command-line interface, and the arbitrary crate enables
Security Testing
SAST (Static Application Security Testing) analyzes source code without running it. DAST (Dynamic Application Security Testing) tests the running application by sending malicious inputs. SAST finds vulnerabilities early in development; DAST finds vulnerabilities that only appear at runtime. Use both: SAST in CI on every pull request, DAST against a
Security Testing
Burp Suite is the industry-standard web application security testing platform. The Community Edition is free and covers proxy interception, manual testing, and the repeater for request manipulation. This guide covers setup, proxying browser traffic, intercepting and modifying requests, using Repeater and Intruder for manual testing, and testing for common
Fuzz Testing
AFL++ (American Fuzzy Lop Plus Plus) is the most widely used coverage-guided fuzzer in the world. It has discovered thousands of vulnerabilities in production software — from image parsers to network protocols to cryptographic libraries. This tutorial walks you through setting up AFL++, instrumenting a target, building an effective corpus,
Testing
Testing authenticated APIs is unavoidable in any real project. Most production endpoints require authentication — Basic Auth, Bearer tokens, OAuth2, or API keys. REST Assured provides built-in support for common authentication schemes and the flexibility to handle anything custom. This guide covers the patterns you'll actually use. Basic
Security Testing
Security testing bolted on at the end of the development cycle catches vulnerabilities too late — when fixing them means rework, delayed releases, and expensive patches. The solution is shifting security into the CI/CD pipeline, where it runs automatically on every change and catches issues when they're cheapest