1971 Nov
The first Unix manual documents sh
The first Unix Programmer's Manual recorded sh as the command interpreter. Early shell execution already connected command files, process creation, redirection, and pipes.
Security
How the field of a Penetration Tester got here: the sourced milestones from every published course of this career, on one axis.
1971 to 2025
82 milestones across 9 courses
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
4 milestones
1971 Nov
The first Unix Programmer's Manual recorded sh as the command interpreter. Early shell execution already connected command files, process creation, redirection, and pipes.
1978 Nov
Stephen Bourne documented control flow, variables, parameter passing, return codes, redirection, pipelines, and commands read from files. Those concepts established the core shape of later Bourne-family scripting.
1983
David Korn's first ksh version added a richer command and scripting language at Bell Labs. Its 1988 language later served as source material for the POSIX shell standard.
1989 Jun
Bash appeared as a free Bourne-family shell for the GNU system. It combined scripting compatibility goals with features influenced by KornShell and the C shell.
9 milestones
1992 Sep
IEEE 1003.2 established a portable shell-language and utility baseline. Script authors could target a published contract instead of one vendor's interpreter behavior.
1995
Dan Farmer and Wietse Venema release SATAN, an early tool that scans networks for known weaknesses, making automated security testing available to a wide audience.
1997
Windows 2000 development adopted Kerberos version 5 as the default authentication protocol for domains. The design that enables later ticket abuses, including the KDC's trust in its own krbtgt key, dates from this decision.
1997 Sep 1
Nmap's publication consolidated multiple port-scanning techniques behind one tool and interface. Network discovery became a repeatable starting point for security assessment.
1998
Early public writing by researcher Jeff Forristal marks the start of SQL injection as a recognized web attack class, giving testers a label for a class of input-handling flaws.
1998 Apr 4
The first Nessus release paired a scanner engine with vulnerability checks. It strengthened the automated hypothesis stage that penetration testers still distinguish from manual validation.
1998 Dec 12
Packet-response fingerprints extended network assessment from port reachability toward host-platform inference. Testers could use one discovery tool to form more specific service and exploit hypotheses.
1999
Microsoft security engineers coin the term cross-site scripting for the client-side attack class where a site renders untrusted input, giving the emerging web security field a shared term.
1999 Jun
RFC 2616 standardized HTTP/1.1. Its method, header, and response model became a common transport surface for web APIs and their security controls.
24 milestones
2000 Dec 7
Nmap 2.54BETA16 expanded the same network-discovery workflow beyond Unix-like tester hosts. Cross-platform availability made the tool easier to place inside varied assessment environments.
2001
OWASP releases WebGoat, a deliberately vulnerable web application, so testers and developers can practice finding and exploiting weaknesses without authorization concerns.
2001 Aug
Researchers implement the FMS attack against WEP with administrator permission. The result exposes a failure in WEP key handling.
2001 Sep 9
Mark Curphey starts the Open Web Application Security Project (OWASP), giving web application security a permanent community home for standards, tools, and training.
2003
OWASP publishes the first OWASP Top Ten, a consensus list of the most critical web application security risks. It becomes the shared vocabulary for describing and prioritizing web risk.
2003
OWASP published the first Top 10 list, establishing a shared awareness document for web application security risks.
2003 Jul 21
Protocol-aware probes connected open ports to likely applications and versions. The change strengthened enumeration while preserving the need to validate fingerprints before claiming exploitability.
2003 Oct 6
Metasploit packaged reusable exploit modules in a shared framework. Testers gained a common platform for moving from a suspected weakness to controlled exploit validation.
2004
OWASP updated the original list, beginning a recurring cycle of revisiting the web application risks practitioners use for awareness.
2004
The amendment extends 802.11 MAC security. It provides a standards foundation for robust security networks.
2004
OWASP publishes the Web Application Penetration Checklist and then Testing Guide v1.0 in December, the first version of the structured methodology that becomes the Web Security Testing Guide.
2004 Aug 14
OWASP WSTG version 1.1 organized web application checks into a public reference. Application testing gained a target-specific structure beyond general network assessment.
2004 Aug 30
The live distribution bundled assessment tools for work on a restricted, air-gapped engagement. It began the project lineage that later produced BackTrack and Kali Linux.
2006
The sqlmap project is registered on SourceForge and its early versions test MySQL injection. It grows into the standard automated tool for detecting and exploiting SQL injection.
2006 May
The WHAX and Auditor projects merged into a shared live testing environment. A portable tool platform reduced setup work across constrained engagements.
2006 May 26
WHAX and Auditor efforts converged into a shared live environment for security assessment. A maintained toolkit distribution reduced setup work between engagements.
2006 Jun
Ubuntu's specification moved the system sh link from Bash to dash while retaining Bash as the user shell. The change made undeclared Bash syntax in system scripts an operational portability defect.
2007
The 2007 update continued the list as a maintained reference rather than a one-time catalog of vulnerabilities.
2007 Jan
Apple introduced iPhone as a software-rich handheld platform. Mobile assessment increasingly had to consider device-side applications, platform controls, and remote services together.
2007 Feb 10
Testing Guide v2.0 broadens the web testing methodology across more application security categories, cementing the guide as the reference for structured web penetration testing.
2008 Jul
Apple opened the App Store in July 2008. Third-party distributed apps became a mainstream security assessment target.
2008 Sep
Android 1.0 released publicly in September 2008. Testing practice expanded across a second major mobile platform with its own application and permission model.
2008 Sep
SP 800-115 includes passive and active wireless scanning within a planned assessment. Wireless testing is tied to scope and evidence handling.
2008 Sep
The guide formalized planning, discovery, attack, reporting, rules of engagement, and operational risk for technical security assessments. It placed penetration testing inside a broader assessment program rather than treating exploitation as the whole activity.
27 milestones
2010
The 2010 edition refreshed the risk categories for the changing web application landscape.
2010 Apr
RFC 5849 published OAuth 1.0. It documented a signed-request approach to delegated access before OAuth 2.0 replaced it.
2010 Sep 6
ZAP 1.0.0 is released as an open-source intercepting proxy and scanner. It becomes an OWASP project and the most-used free tool for manual web application testing.
2011 Sep
OWASP AppSec USA material documented the Mobile Security Project and Mobile Top 10 risks. It gave practitioners a shared vocabulary for recurring mobile weaknesses.
2011 Dec
Research identifies a weakness in PIN enrollment. Wireless assessment must examine enrollment separately from WPA passphrase strength.
2012
The ShellCheck project began cataloging defects in quoting, tests, commands, and portability. Script review gained an automated layer that reasons from the declared shell language.
2012 Feb
SP 800-153 addresses security across WLAN design, deployment, maintenance and monitoring. AP and client controls belong to the same lifecycle.
2012 Oct
RFC 6749 standardized OAuth 2.0 authorization grants and access tokens. API security practice gained a common framework for delegated authorization.
2013
The 2013 edition revised the list and broadened some category scopes, affecting how teams mapped findings to risk categories.
2013 Mar 13
The Debian-based distribution replaced BackTrack with a rebuilt development and packaging model. Penetration testers gained a maintained platform for assembling the discovery, validation, evidence, and reporting toolchain.
2014
Tim Medin demonstrated requesting service tickets for SPN accounts and cracking them offline, converting an ordinary ticket request into a password recovery attack. The technique remains one of the most common path steps because it needs no privilege at all.
2014 Sep
The Shellshock disclosures showed that crafted environment values could trigger unintended command execution in vulnerable Bash versions. Fixes changed how exported functions were represented and imported.
2014 Sep 17
The fourth major guide release refreshed the public framework for web application testing. Versioned scenarios gave reports a stable way to name application coverage.
2014 Sep 17
The renamed Web Security Testing Guide v4.0 organizes tests into categories with stable WSTG identifiers, so testers can cite a specific check across tools and reports.
2014 Nov
Microsoft's security bulletin documented a Kerberos KDC signature validation flaw allowing forged tickets claiming privileged group membership. The patch closed the flaw for updated systems, but unpatched estates still carry the edge.
2015 May
RFC 7519 defined JSON Web Token claims and compact serialization. Token validation became an explicit API implementation concern.
2015 Sep
RFC 7636 specified proof key for code exchange. Public clients gained a standardized mitigation for authorization-code interception.
2016
BloodHound introduced attack path analysis as shortest-path queries over collected Active Directory relationship data. The demonstration showed hidden paths to Domain Admins that no checklist inspection surfaced, and the tool quickly became standard for both attackers and defenders.
2016
OWASP recorded a final 2016 Mobile Top 10 list. Mobile assessment could compare recurring risk categories across apps while retaining app-specific evidence.
2017
Key reinstallation research exposes nonce-reuse risks in WPA2 exchanges. Password replacement alone does not repair the affected mechanism.
2017
The 2017 edition documented categories including injection, broken authentication, and sensitive data exposure.
2017 Mar
The RFC specifies encryption without peer authentication. Passive confidentiality and network identity become explicit separate properties.
2018
Coercion primitives in remote procedure interfaces, studied through 2018 and after, showed that ordinary protocol methods could force machines to authenticate to attacker-chosen hosts. These primitives became the standard way to feed relay and unconstrained delegation capture chains.
2018 Jun
Wi-Fi Alliance introduces SAE-based personal authentication and required PMF for WPA3 connections. Transitional operation retains WPA2 compatibility.
2019
Research examines SAE and EAP-pwd downgrade and side-channel weaknesses. Implementation updates and transition choices remain part of assessment.
2019
OWASP released its first API-specific Top 10. It established a shared vocabulary for broken object authorization and resource limits.
2019 Jan
Elad Shamir's research showed that S4U2Proxy accepts non-forwardable tickets under resource-based constrained delegation, reducing host takeover to one writable attribute plus any SPN-bearing account. Combined with relayed machine authentications into LDAP, this became the default modern takeover chain.
18 milestones
2020 Aug
The Netlogon remote protocol's use of AES-CFB8 with a zero initialization vector allowed an attacker to reset a domain controller's machine account password. Where reachable, the flaw compressed domain takeover to minutes and forced urgent patching campaigns.
2020 Dec
A Kerberos S4U flaw allowed the forwardable flag to be forged in constrained delegation requests, bypassing delegation restrictions. Microsoft's December 2020 patches closed it, adding another historic edge that patch state decides.
2020 Dec 3
Version 4.2 added testing scenarios and revised chapters and layout. The guide continued separating target-specific web tests from a generic penetration-testing checklist.
2020 Dec 3
WSTG v4.2 refreshes existing test scenarios and adds new ones while keeping the stable identifier format, remaining the current reference version for web application testing.
2021
OWASP introduced new categories and naming changes that emphasized root causes over symptoms, using a formalized data-collection process.
2021 May
RFC 8725 documented JSON Web Token best current practices. It emphasized explicit algorithm, issuer, audience, and token-kind checks.
2021 May 11
Research finds fragmentation and aggregation design flaws plus implementation defects. Assessment needs patch evidence across Wi-Fi security modes.
2021 Jul
OWASP released MSTG v1.2 with updated test material, tools, and platform guidance. The guide continued to connect verification work with changing Android and iOS practice.
2021 Sep 24
The 2021 Top Ten puts Broken Access Control at the top position, reflecting how frequently missing authorization checks lead to data exposure, and adds categories for insecure design and integrity failures.
2022
Adversary reporting through 2022, including SVR and ransomware crew tradecraft, recorded BloodHound collection, Kerberoasting, DCSync, and golden ticket use as routine steps. The techniques stopped being specialist knowledge and became the expected path model defenders must assume.
2023
MASVS 2.0 simplified and clarified the standard while relying more on related industry standards. Testing details remained in MASTG during the transition.
2023
The 2023 edition includes business-flow abuse, server-side request forgery, improper inventory management, and unsafe API consumption.
2023 Feb
AA23-059A documented a three-month assessment that went from spearphishing through unconstrained delegation, DCSync of krbtgt, and golden tickets to deep persistence, undetected. The advisory's findings list read as a validation of the graph model, since no single step was exotic and the chain went uncaught.
2023 Aug
OWASP recorded the initial release of the current Mobile Top 10 in August 2023. The list reflects a refreshed taxonomy for communicating mobile application risks.
2024 Jan
MASVS 2.1 added the MASVS-PRIVACY category. Privacy became an explicit control area in the standard used to organize mobile assessment objectives.
2024 Jun
IEEE and The Open Group published a new base specification including the shell and utilities volume. The portable contract remained an active standard rather than a frozen description of one historic shell.
2025
The 2025 edition updated the ten-category map, including software supply chain failures and mishandling of exceptional conditions.
2025 Jun
NIST SP 800-228 organized controls across pre-runtime and runtime lifecycle stages for cloud-native systems.