Security Testing
Security testing examines systems and software for weaknesses that could let an attacker bypass intended protections. It combines automated checks and human investigation, then turns reproducible findings into repair work and retesting.
itOffensive security and application security | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Security testing
Security testing is the controlled examination of a system to find and validate weaknesses in its protections. It asks whether security requirements hold when software receives malformed input, credentials have different privileges, components are misconfigured, or an authorized tester behaves like an attacker.
The subject is broader than penetration testing. A vulnerability assessment searches for known or suspected weaknesses and estimates their exposure. A penetration test attempts selected attack paths to show what an attacker could achieve. Static analysis examines source or compiled code without running the target. Dynamic analysis interacts with a running application. Configuration review, dependency analysis, fuzzing, and manual business-logic tests cover other parts of the attack surface.
The testing system
A useful security test has five connected parts:
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://csrc.nist.gov/pubs/sp/800/115/final
Supports
- Planning, conducting, analyzing, and reporting technical security tests
- Rules of engagement, assessment logistics, and data handling
- Review, identification and analysis, and target-vulnerability validation techniques
- Benefits and limitations of vulnerability scanning and penetration testing
- Mitigation and post-testing activities
- Quiz answers about authorization, assessment type, access, validation, and limits
- https://csrc.nist.gov/pubs/sp/800/42/final
Supports
- October 2003 publication date
- Consistent network security testing programs, techniques, and tools
- Supersession by NIST SP 800-115 in September 2008
- https://owasp.org/www-project-web-security-testing-guide/
Supports
- WSTG purpose and versioned scenario identifiers
- Availability of version 4.2 as a versioned release
- Security testing as detailed application assessment guidance
- https://owasp.org/www-project-web-security-testing-guide/v42/
Supports
- Web test coverage across information gathering, configuration, identity, authorization, sessions, input validation, business logic, client-side behavior, and APIs
- Manual and tool-assisted web testing scenarios
- Quiz answers about authorization requirements and retesting relevant variants
- https://owasp.org/www-project-web-security-testing-guide/v42/0-Foreword/README
Supports
- Security testing cannot exhaust every way an application may fail
- Tools and testing complement broader secure development work
- Quiz answer about the limit of a clean result
- https://owasp.org/www-project-web-security-testing-guide/v41/2-Introduction/
Supports
- Testing framework rather than an issue checklist
- Integration of web application testing into the software development life cycle
- 2014 Testing Guide version 4 milestone meaning
- https://owasp.org/www-project-web-security-testing-guide/v41/6-Appendix/E-History
Supports
- Testing Guide project origin in 2003
- Release dates for Testing Guide versions 1, 2, 3, and 4
- https://owasp.org/www-project-application-security-verification-standard/
Supports
- ASVS as a basis for testing application technical security controls
- Verification requirements as a measurable test basis
- Quiz answers about role requirements and control-level retesting
- https://csrc.nist.gov/pubs/sp/800/218/final
Supports
- Security verification and vulnerability response within software development
- Reference-path rationale for integrating testing with releases
- https://www.first.org/cvss/v4-0/specification-document
Supports
- CVSS vulnerability characteristic groups and scoring model
- Severity as structured vulnerability information rather than complete business priority
- https://attack.mitre.org/resources/getting-started/
Supports
- ATT&CK as a knowledge base of adversary tactics and techniques
- Use of ATT&CK to inform hypotheses and coverage without proving control effectiveness
- https://owasp.org/about/
Supports
- OWASP launch on December 1, 2001
- Open software-security projects, documentation, and standards
- https://owasp.org/www-project-developer-guide/
Supports
- Developer Guide 1.0 publication in 2002
- Original penetration-testing material later covered by WSTG
- https://portswigger.net/about
Supports
- Burp Suite 1.0 launch in June 2003
- Initial Proxy, Sock, Spider, and Repeater tools
- https://owasp.org/2020/12/17/owasp-zap-210-release.html
Supports
- ZAP tenth birthday in 2020 and 2010 origin
- ZAP as an OWASP web application scanner project
- https://owasp.org/www-event-2020-NewZealandDay/assets/presentations/Manico--Keynote-Abridged_History_of_AppSec--20200221.pdf
Supports
- 2010 OWASP ZAP release milestone
- Security-testing history context
- https://github.com/sindresorhus/awesome
Supports
- Discovery route from the requested root index to security and testing lists
- https://github.com/enaqx/awesome-pentest
Supports
- Discovery of Nuclei, Dradis, sqlmap, Kali Linux, and SecLists as relevant ecosystem resources
- Awesome Links curation decision
- https://docs.projectdiscovery.io/opensource/nuclei/overview
Supports
- Nuclei as a template-driven scanner across applications, infrastructure, cloud, and networks
- Awesome Links rationale about repeatable protocol-aware checks
- https://dradis.com/support/guides/projects.html
Supports
- Projects, methodologies, finding review, and report generation
- Awesome Links rationale about engagement evidence and reporting
- https://github.com/sqlmapproject/sqlmap/wiki/Introduction
Supports
- Automated SQL injection detection and validation
- Awesome Links rationale about focused automation
- https://github.com/ffuf/ffuf
Supports
- Web fuzzing for content and parameter discovery
- Awesome Links rationale about attack-surface mapping
- https://www.kali.org/docs/
Supports
- Operation of a penetration-testing distribution and its tool ecosystem
- Awesome Links rationale about a controlled testing workstation
- https://www.kali.org/tools/seclists/
Supports
- SecLists collections for usernames, passwords, URLs, fuzzing payloads, and other test inputs
- Awesome Links rationale about purpose-built input lists
- https://portswigger.net/burp/documentation/desktop/tools
Supports
- Burp tools for intercepting, replaying, and scanning web traffic
- Burp Suite landscape placement
- https://www.zaproxy.org/docs/automate/automation-framework/
Supports
- YAML automation plans, authentication, passive scanning, and active scanning
- OWASP ZAP landscape placement
- https://www.invicti.com/product/
Supports
- Automated web and API security testing and remediation workflow
- Invicti landscape placement
- https://www.tenable.com/products/nessus
Supports
- Nessus vulnerability assessment of hosts, services, and configurations
- Tenable Nessus landscape placement
- https://www.qualys.com/apps/vulnerability-management-detection-response
Supports
- Asset discovery, vulnerability assessment, prioritization, and remediation workflow
- Qualys VMDR landscape placement
- https://docs.rapid7.com/insightvm/
Supports
- InsightVM console, distributed scan engines, sites, findings, and reports
- Rapid7 InsightVM landscape placement
- https://docs.rapid7.com/insightvm/working-with-vulnerabilities/
Supports
- Scan result review and varying certainty of vulnerability evidence
- Metasploit integration for controlled validation
- Quiz answer about validating version-based signals
- https://greenbone.github.io/docs/latest/
Supports
- OpenVAS scanner and self-managed Greenbone vulnerability-testing stack
- Greenbone landscape placement
- https://semgrep.dev/products/semgrep-code/
Supports
- Rule-based static analysis in development workflows
- Semgrep landscape placement
- https://snyk.io/product/
Supports
- Testing of code, dependencies, containers, and infrastructure definitions
- Snyk landscape placement
- https://checkmarx.com/product/checkmarx-one/
Supports
- Centralized application security testing across code, dependencies, infrastructure, and APIs
- Checkmarx One landscape placement
- https://docs.metasploit.com/
Supports
- Exploit modules and controlled vulnerability validation
- Metasploit Framework landscape placement
- https://www.cobalt.io/platform
Supports
- Managed penetration testing coordination and finding workflow
- Cobalt landscape placement
